Re: I-D ACTION:draft-katz-yeung-ospf-traffic-10.txt

[Rohit Dube <[e-mail]>]

Folks,

This draft will be IETF Last-Called shortly (with CC to
OSPF WG) and then submitted for IESG review.

The IANA section has changed significantly from the previous
version as the IESG objected to the Private Use and (my impression)
to a lesser degree with the FCFS range. This has now been fixed
(see diff excerpt below).

If you have comments, now would be the time to make them.

Best,
--rohit.

On Thu, 19 Jun 2003 09:40:54 -0400 Rohit Dube writes:
=>Folks,
=>
=>Attached below is the output of
=>`diff -u draft-katz-yeung-ospf-traffic-09.txt draft-katz-yeung-ospf-traffic-1
>0.txt`
=>(Apologies in advance for the rather larger attachment created by the
=>output of diff.)
=>
=>Please review. Specifically, note the changes in the IANA considerations
=>section.
=>
=>Thanks,
=>--rohit.
=>
=>
=>--- draft-katz-yeung-ospf-traffic-09.txt        Fri Nov 22 11:13:40 2002
=>+++ draft-katz-yeung-ospf-traffic-10.txt        Thu Jun 19 09:31:47 2003
[snip]
=>-8. IANA Considerations
=>
=>-   The top level Types in a TE LSA as well as Types for sub-TLVs in a TE
=>-   Link TLV are to be registered with IANA.
=>
=>-   Following the guidelines set in [10], top level Types in TE LSAs from
=>-   3 through 32767 are to be assigned by Expert Review (the said Expert
=>-   to be decided by the IESG).  Types from 32768 through 65535 are
=>-   reserved for Private Use.  In all cases, assigned values Types MUST
=>-   be registered with IANA.
=>-
=>-   Also, sub-Types of a TE Link TLV from 10 to 32767 are to be assigned
=>-   by Expert Review; values from 32768 through 32772 are reserved for
=>-   Private Use; and values from 32773 through 65535 are to be assigned
=>+
=>+
=>+
=>+
=>+
=>+
=>+
=>
=>
=>
=> Katz, Yeung, Kompella        Standards Track                   [Page 12]
=>
=>-Internet Draft           TE Extensions to OSPFv2            October 2002
=>+Internet Draft           TE Extensions to OSPFv2               June 2003
=>+
=>
=>+IANA Considerations
=>
=>-   First Come First Served.  In all cases, assigned values are to be
=>-   registered with IANA.
=>+   The top level Types in a TE LSA as well as Types for sub-TLVs for
=>+   each top level Type are to be registered with IANA, except as noted.
=>
=>+   Here are the guidelines (using terms defined in [10]) for the
=>+   assignment of top level Types in TE LSAs:
=>+    o Types in the range 3-32767 are to be assigned via Standards
=>+      Action.
=>+    o Types in the range 32768-32777 are for experimental use; these
=>+      will not be registered with IANA, and MUST NOT be mentioned by
=>+      RFCs.
=>+    o Types in the range 32778-65535 are not to be assigned at this
=>+      time.  Before any assignments can be made in this range, there
=>+      MUST be a Standards Track RFC that specifies IANA Considerations
=>+      that covers the range being assigned.
=>+
=>+   The guidelines for the assignment of types for sub-TLVs in a TE LSA
=>+   are as follows:
=>+    o Types in the range 10-32767 are to be assigned via Standards
=>+      Action.
=>+    o Types in the range 32768-32777 are for experimental use; these
=>+      will not be registered with IANA, and MUST NOT be mentioned by
=>+      RFCs.
=>+    o Types in the range 32778-65535 are not to be assigned at this
=>+      time.  Before any assignments can be made in this range, there
=>+      MUST be a Standards Track RFC that specifies IANA Considerations
=>+      that covers the range being assigned.
[snip]