[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: I-D ACTION:draft-berger-gmpls-egress-control-00.txt

Alan,
Thanks for the comments. I'll incorporate in the next rev of the draft.

Lou

At 09:46 PM 12/1/2003, Kullberg Alan-G19424 wrote:

Hi Lou,

I have a few typo fixes below as well as this comment.
In section 2.1 ERO Procedures, it says "the label is copied
into a new Label_Set object."

I understand the intent of this statement, but this may mislead
people into thinking that the signaling of the LSP continues
beyond the current (egress) node.

Perhaps that sentence and the one following it could be reworded
as follows:
   If the U-bit of the
   subobject being examined is clear (0), then the value of the label is
   used for downstream traffic associated with the LSP.  This label value
   MUST be used for transmitting traffic associated
   with the LSP on the indicated outgoing/downstream interface.


I've reworded as follows:
  If the U-bit of the subobject being examined is clear (0), then the
  value of the label is copied into a new Label_Set object.  Note, this
  Label_Set object is for internal use only.  This Label_Set object
  indicates the label value that MUST be used for transmitting traffic
  associated with the LSP on the indicated outgoing/downstream interface.

And to make the next paragraph consistent, I would add the word
MUST as follows:
   Specifically, the label value MUST be used for

Not using MUST here was intentional as the use is by the connected node, so there is no way for the processing node to enforce this.

Now for typos:

In the Abstract change "know and" to "known as":
   Such control is also known as "Egress Control".

thanks.

In 2. Egress Control Procedures, change "that section" to "those sections":
   The procedures described in those sections...

thanks.

In 2.1. ERO Procedures, change "unicast" to "unidirectional":
   If the associated LSP is unidirectional...


Thanks again,
Lou


Regards,
Alan

> -----Original Message-----
> From: owner-ccamp@ops.ietf.org
> [<mailto:owner-ccamp@ops.ietf.org>mailto:owner-ccamp@ops.ietf.org] On Behalf Of Lou Berger
> Sent: Monday, December 01, 2003 1:50 PM
> To: ccamp@ops.ietf.org
> Subject: Fwd: I-D ACTION:draft-berger-gmpls-egress-control-00.txt
>
>
> FYI -
> Please send comments to me (and/or the list).
>
> Thanks,
> Lou
>
> >To: IETF-Announce: ;
> >From: Internet-Drafts@ietf.org
> >Reply-To: Internet-Drafts@ietf.org
> >Subject: I-D ACTION:draft-berger-gmpls-egress-control-00.txt
> >Date: Mon, 24 Nov 2003 15:32:17 -0500
> >Sender: owner-ietf-announce@ietf.org
> >
> >A New Internet-Draft is available from the on-line Internet-Drafts
> >directories.
> >
> >
> > Title : GMPLS Signaling Procedure For
> Egress Control
> > Author(s) : L. Berger
> > Filename : draft-berger-gmpls-egress-control-00.txt
> > Pages : 4
> > Date : 2003-11-24
> >
> >This note clarifies the procedures for the control of a
> label used on
> >an egress output/downstream interface. Such control is also
> know and
> >'Egress Control'. Support for Egress Control is implicit in
> >Generalized Multi-Protocol Label Switching (GMPLS) Signaling
> [RFC3471]
> >and [RFC3473]. This note does not modify GMPLS signaling mechanisms
> >and procedures and should be viewed as an informative
> clarification of
> >[RFC3473].
> >
> >A URL for this Internet-Draft is:
> ><http://www.ietf.org/internet-drafts/draft-berger-gmpls-egress>http://w ww.ietf.org/internet-drafts/draft-berger-gmpls-egress
> -control-0
> >0.txt
> >
> >To remove yourself from the IETF Announcement list, send a
> message to
> >ietf-announce-request with the word unsubscribe in the body of the
> >message.
> >
> >Internet-Drafts are also available by anonymous FTP. Login with the
> >username "anonymous" and a password of your e-mail address. After
> >logging in, type "cd internet-drafts" and then
> > "get draft-berger-gmpls-egress-control-00.txt".
> >
> >A list of Internet-Drafts directories can be found in
> ><http://www.ietf.org/shadow.html>http://www.ietf.org/shadow.html or
> ><ftp://ftp.ietf.org/ietf/1shadow-sites.txt>ftp://ftp.ietf.org/ietf/1sha dow-sites.txt
> >
> >
> >Internet-Drafts can also be obtained by e-mail.
> >
> >Send a message to:
> > mailserv@ietf.org.
> >In the body type:
> > "FILE
> >/internet-drafts/draft-berger-gmpls-egress-control-00.txt".
> >
> >NOTE: The mail server at ietf.org can return the document in
> > MIME-encoded form by using the "mpack" utility. To use this
> > feature, insert the command "ENCODING mime" before
> the "FILE"
> > command. To decode the response(s), you will need
> "munpack" or
> > a MIME-compliant mail reader. Different
> MIME-compliant mail readers
> > exhibit different behavior, especially when dealing with
> > "multipart" MIME messages (i.e. documents which
> have been split
> > up into multiple messages), so check your local
> documentation on
> > how to manipulate these messages.
> >
> >
> >Below is the data which will enable a MIME compliant mail reader
> >implementation to automatically retrieve the ASCII version of the
> >Internet-Draft.
> >Content-Type: text/plain
> >Content-ID: <2003-11-24152450.I-D@ietf.org>
> >
> >ENCODING mime
> >FILE /internet-drafts/draft-berger-gmpls-egress-control-00.txt
> >
> ><ftp://ftp.ietf.org/internet-drafts/draft-berger-gmpls-egress
-control-0
>0.txt>