[CCAMP] Fw: I-D Action:draft-kern-ccamp-rsvpte-hop-attributes-00.txt

["Adrian Farrel" <[e-mail]>]

Hi,

Did you notice that RFC 5420 allows the recording of per attributes in the 
RRO using the RRO Attributes Subobject as defined in section 7.2?

I would suggest you should not define a duplicate of this function, and if 
you need similar function in the ERO you should use the same subobject type 
and number.

The RRO Attributes Subobject collects only flags (not TLVs). This was a 
deliberate decision based on scalability and there being no defined 
requirements for collecting TLVs.

Similarly, we did not define an ERO Attributes Subobject, because there was 
no defined requirement to have an LSP behave differently on different hops.

I think that it might be useful if you could set out your requirements 
before extending the protocol in this way.

Cheers,
Adrian

----- Original Message ----- 
From: <[e-mail]>
To: <[e-mail]>
Sent: Monday, October 19, 2009 4:45 PM
Subject: I-D Action:draft-kern-ccamp-rsvpte-hop-attributes-00.txt


>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>
> Title           : Encoding of Attributes of LSP intermediate hops using 
> RSVP-TE
> Author(s)       : A. Kern, A. Takacs
> Filename        : draft-kern-ccamp-rsvpte-hop-attributes-00.txt
> Pages           : 10
> Date            : 2009-10-19
>
> RFC5420 specifies a general framework to support signaling and
> reporting of generic attributes relevant for a signaled LSP.  This
> document extends the concept and defines a new Explicit Route
> subobject for RSVP-TE to allow the specification and reporting of
> attributes relevant to a particular hop of the signaled LSP.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-kern-ccamp-rsvpte-hop-attributes-00.txt