The MPLS WG Archive

["Adrian Farrel" <adrian@olddog.co.uk>]

OK, we can do that (although in fairness, anyone not familiar with the RRO should really
not be playing with LSP Attributes!).

A
----- Original Message ----- 
From: "Joel M. Halpern" <joel@stevecrocker.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>; <gen-art@alvestrand.no>
Cc: "Dimitri Papadimitriou" <Dimitri.Papadimitriou@alcatel.be>; <jpv@cisco.com>; "Arthi
Ayyangar" <arthi@juniper.net>; <mpls@lists.ietf.org>; "Alex Zinin" <zinin@psg.com>;
"George Swallow" <swallow@cisco.com>; "Loa Andersson" <loa@pi.se>
Sent: Tuesday, December 07, 2004 10:55 PM
Subject: Re: Last Call Assignment: draft-ietf-mpls-rsvpte-attributes-04.txt


> The description you provide makes sense.
> I am afraid that a reader who is not sufficiently involved in RRO work may
> well not understand what is meant.  If you could elaborate the second
> sentence (the one with "the RRO immediately before") just a bit, it would
> probably help.
>
> Yours,
> Joel
>
> At 04:48 PM 12/7/2004, Adrian Farrel wrote:
> > > In section 7.3.1, there are two lines which confused me:
> > >     The Attributes subobject is pushed onto the RECORD_ROUTE object
> > >     immediately prior to pushing the node's IP address or link
> > >     ...
> > >     This means that an Attributes subobject is bound to the LSR
> > >     identified by the subobject found in the RRO immediately before the
> > >     Attributes subobject.
> > > The first sentence seems to say that when I parse the message I will find
> > > the Attributes subobject followed by the ID of the node which put it there.
> > > The later sentence seems to say that the Attributes subobject is bound to
> > > the ID which precedes it, rather than the ID which follows it?
> >
> >No, RRO is described as a stack. So, that which you push first, you pop last.
> >
> >You receive an RRO and you add your sub-objects to the front. You add the
> >Attributes
> >sub-object first, then you add your node/link.
>
>
>


_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls