Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)
draft-ietf-mpls-rsvp-unnum-08

2002-11-14 - rfc ed note from alex & the ID is approved

In section 5 replace

  An unnumbered link has to be a point-to-point link. An LSR at each
  end of an unnumbered link assigns an identifier to that link. This
  identifier is a non-zero 32-bit number that is unique within the
  scope of the LSR that assigns it. The IS-IS and/or OSPF and RSVP
  modules on an LSR must agree on the identifiers.

with

  An unnumbered link has to be a point-to-point link. An LSR at
  each end of an unnumbered link assigns an identifier to that
  link. This identifier is a non-zero 32-bit number that is unique
  within the scope of the LSR that assigns it. If one is using
  OSPF or ISIS as the IGP in support of traffic engineering, then
  the IS-IS and/or OSPF and RSVP modules on an LSR must agree on
  the identifiers.

In section 5 replace

  In the context of this document the term "Router ID" refers to the
  "Router Address" as defined in [OSPF-TE], or "Traffic Engineering
  Router ID" as defined in [ISIS-TE].

with

  In the context of this document the term "Router ID" means a
  stable IP address of an LSR that is always reachable if there
  is any connectivity to the LSR. This is typically implemented
  as a "loopback address"; the key attribute is that the address
  does not become unusable if an interface on the LSR is down.
  In some case this value will need to be configured. If one is
  using OSPF or ISIS as the IGP in support of traffic engineering,
  then it is RECOMMENDED to set the Router ID to the "Router
  Address" as defined in [OSPF-TE], or "Traffic Engineering Router
  ID" as defined in [ISIS-TE].

2002-11-02 - sent draft rfc ed note to iesg

RFC Editor:
        Please move teh following two references to the normative
section:
        [OSPF-TE] and [ISIS-TE]

2002-10-31 - IESG discussion
OKed but references do need to be normative - Alex
says that this should not delay things all that much
the change will be done with an RFC Editor note (no new
version needed)

2002-10-25 - note from loa to ADs & Alex
Alex,

Scott informed us that you've suggested that the isis-te and the
ospf-te references in the rsvp-unnum should be made normative.

We've two issues on this:

1. cr-ldp-unnum and rsvp-unnum should be treated the same way
2. we are concerned that making those references normative will delay
    delay the publication of the draft unnecessarily.
    are the argument for normative references really strong, they were
    included just refer to the router address and router id. it does not
    seem ther right thing to do to create a situation where it becomes
    hard to move documents because of this kind of reference.

Do we have a time schedule for isis-te and ospf-te? Could the references
stay non-normative? Any other way to solve this?

/Loa

2002-08-22 - on IESG agenda
comments back to mpls WG chairs
1/ in sec 10 - the text "The responsible Internet authority (presently called the IANA)" should be replaced with "The IANA" (we do not need the semi-political statement)

2/ the IPR text from RFC 2026 sec 10.4(A) and 10.4(B) should be added to the ID

3/ The document uses the notion of "Router ID" that is not
defined. One could read it as OSPF Router ID or TE Router ID, for example, that have completely different name spaces.

State Changes to Ready for Telechat                                from Last Call Issued                                  by sob

State Changes to Last Call Issued                                  from Last Call Requested                              by jhargest

State Changes to Last Call Requested                              from New Version Needed (WG/Author)                    by sob

2002-06-02 - note to chairs - sob
> acronyms must be expanded in title and abstract
> MUST etc used but not defined (eg. add reference to RFC 2119)
> s/idenfitier/identifier - sec 4, 4th pp
> s/cooresponding/corresponding/ - sec 7 near end

State Changes to New Version Needed (WG/Author)                    from Pre AD Evaluation                                by sob

State Changes to Pre AD Evaluation                                from In WG                                            by sob