[mpls] Re: Last Call Assignment: draft-ietf-mpls-rsvpte-attributes-04.txt

"Joel M. Halpern" <joel@stevecrocker.com> Tue, 07 December 2004 23:34 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14641; Tue, 7 Dec 2004 18:34:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbowj-0004N9-G1; Tue, 07 Dec 2004 18:41:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CboZW-0003Ri-NN; Tue, 07 Dec 2004 18:16:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CboIl-00087m-N9 for mpls@megatron.ietf.org; Tue, 07 Dec 2004 17:59:23 -0500
Received: from EXECDSL.COM (ns.execdsl.net [208.184.15.238]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10292 for <mpls@lists.ietf.org>; Tue, 7 Dec 2004 17:59:20 -0500 (EST)
Received: from [64.254.114.114] (HELO JLaptop.stevecrocker.com) by EXECDSL.COM (CommuniGate Pro SMTP 3.3) with ESMTP id 8163028; Tue, 07 Dec 2004 17:59:22 -0500
Message-Id: <6.1.2.0.0.20041207175414.04045830@localhost>
X-Sender: joel@stevecrocker.com@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Tue, 07 Dec 2004 17:55:59 -0500
To: Adrian Farrel <adrian@olddog.co.uk>, gen-art@alvestrand.no
From: "Joel M. Halpern" <joel@stevecrocker.com>
In-Reply-To: <04c401c4dca6$934dd550$fd919ed9@Puppy>
References: <5E17B42A-485B-11D9-8830-000393CC2112@psg.com> <6.1.2.0.0.20041207111453.03e2ed38@localhost> <04c401c4dca6$934dd550$fd919ed9@Puppy>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: mpls@ietf.org, jpv@cisco.com
Subject: [mpls] Re: Last Call Assignment: draft-ietf-mpls-rsvpte-attributes-04.txt
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

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