The MPLS WG Archive

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

Joel,

Excellent. Thank you.

In line.

Adrian

> IANA Considerations:
>      The document identifies two new spaces for the IANA to manage.  It
> lists the properties of relevance to values in these spaces.  However, it
> does not indicate what procedure is to be followed for assigning values in
> these registries.  Are they to be assigned only by IETF Standards Track
> RFCs?  Are they assigned simply on a first-come, first-served basis with
> sufficient documentation?

Good catch. I never did get IANA sections right. We'll think about this and update the
draft.

> Minor comments:
>
> The document talks about several degrees or kinds of mandatory / optional
> information, ranging from information that must be examined at every node
> to information that only needs to be examined at the end-points.  The
> specific example is given of information that needs to be examined at
> ABR/ASBRs, but should be deployable without upgrading all routers in the
> path.  It is not clear that this stated goal is met by the solution
> provided.  Some text on how the various cases listed are met by the
> documented method would be helpful.

Sure. We can do that.

> 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