datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery
RFC 4872

Note: This ballot was opened for revision 04 and is now closed.

Summary: Needs a YES. Needs 9 more YES or NO OBJECTION positions to pass.

[Brian Carpenter]

Comment (2006-10-20)

From Gen-ART review by Pasi Eronen:

There is one minor nit (but IANA/RFC editor will take care of it):
sections 9.3 and 9.4 suggest the same value (198) forthe
SECONDARY_EXPLICIT_ROUTE and SECONDARY_RECORD_ROUTE objects.

[Russ Housley]

Comment (2006-10-24)

  s/IPSEC/IPsec/

  When recommending the use of IPsec, please point to section 12
  of [RFC3473].

[Ted Hardie]

Comment (2006-10-23)

Nit:

Extended Tunnel ID

        A 32-bit (or 16-byte) identifier used in the SESSION that
        remains constant over the life of the tunnel. Normally set to
        all zeros. Ingress nodes that wish to narrow the scope of a
        SESSION to the ingress-egress pair MAY place their IPv4 (or
        IPv6) address here as a globally unique identifier.

I think it would be better to say 32-bit or 128-bit identifer; this is
more consistent, avoids the "byte is not always octet" gotcha, and seems
closer to the typical usage for v6 address discussions.