Subject: Re: [CCAMP] FW: I-D Action: draft-margaria-ccamp-lsp-attribute-ero-00.txt

From: Jie Dong <[email-masked]>
Date: Wed, 30 May 2012 03:05:00 +0000

Hi Cyril, 

Here are some comments on this draft.

3rd paragraph of Sec 2.3 says that the new subobject with the R bit set or cleared MUST be examined following the rules in RFC 5420.

Since the LSP attributes in this subobject is explicitly sent to a specific node addressed by the preceding ERO subobject, IMO the processing rules may be slightly different from RFC 5420. For example, if the R bit is cleared, and if the target node of the attribute does not recognize the attribute TLV, the TLV will not be passed on unaltered to the downstream. Some clarifications in this part may be helpful.

BTW, could you provide some use case in which this subobject is sent to a particular node with R bit cleared?

Sec 2.3, 3rd paragraph, 
s/ERO LSP attribute subject/ERO LSP attribute subobject

Best regards,
Jie

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]] On Behalf
> Of Margaria, Cyril (NSN - DE/Munich)
> Sent: Wednesday, April 18, 2012 11:57 PM
> To: CCAMP
> Subject: [CCAMP] FW: I-D Action:
> draft-margaria-ccamp-lsp-attribute-ero-00.txt
> 
> Hi all,
> 
> Following Lou directions we wrote a draft addressing a generic LSP
> attribute subobject in the ERO.
> 
> Comments are welcome.
> 
> Best regards
> Cyril
> 
> > -----Original Message-----
> > From: [email-masked] [mailto:i-d-announce-
> > [email-masked]] On Behalf Of ext [email-masked]
> > Sent: Wednesday, April 18, 2012 5:50 PM
> > To: [email-masked]
> > Subject: I-D Action: draft-margaria-ccamp-lsp-attribute-ero-00.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> >
> > 	Title           : LSP Attribute in ERO
> > 	Author(s)       : Cyril Margaria
> >                           Dirk Schroetter
> >                           Giovanni Martinelli
> > 	Filename        : draft-margaria-ccamp-lsp-attribute-ero-00.txt
> > 	Pages           : 11
> > 	Date            : 2012-04-18
> >
> >    LSP attributes can be specified or recorded for whole path, but
> they
> >    cannot be specified as part of an Explicit Route Object (ERO).
> This
> >    document extend the semantic for RSVP ERO object with a new
> > subobject
> >    to carry LSP attributes.
> >
> >
> > A URL for this Internet-Draft is:
> >
> http://www.ietf.org/internet-drafts/draft-margaria-ccamp-lsp-attribute-
> > ero-00.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > This Internet-Draft can be retrieved at:
> > ftp://ftp.ietf.org/internet-drafts/draft-margaria-ccamp-lsp-attribute-
> > ero-00.txt
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > [email-masked]
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _______________________________________________
> CCAMP mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/ccamp