draft-ietf-l2tpext-circuit-status-extensions-02.txt

Ignacio Goyret <[email protected]> Fri, 13 Mar 2009 10:16:51 -0700
Newsgroups gmane.ietf.l2tpext
Message-ID <[email protected]>
Hi,
A few comments on the circuit-extensions draft:

1) Since this draft adds some new bits, including an
   "Standby" bit that affects the data plane, would it
   make sense to add a bit to request a remote loop?
   (ie, ask the remote LCCE to send all packets received
   over the L2TP tunnel back to the sender LCCE)

   Mmm, come to think of it, this may be the wrong AVP
   for that kind of function.

2) Besides updating RFC3931, this draft is also implicitly
   updating 4591, as well as 4349, 4454 and 4719.

   The new bits and the effect on the N-bit are applicable
   to all protocols, right?

   If so, RFC4591 should probably be moved to the normative
   section of the references, and the others should be added.

That's all I have.


I'd like to start a WGLC on this document but,
with IETF74 so close, we should wait until after
the meeting.

In the meantime, please, take the time to read this
document: it is an easy read.

Cheers,
-Ignacio