Skip to main content

Label Distribution Protocol (LDP) Internet Assigned Numbers Authority (IANA) Considerations Update
draft-ietf-mpls-ldp-iana-01

Revision differences

Document history

Date Rev. By Action
2024-01-16
01 Adrian Farrel This document fell at the last hurdle when the AD sent questions before issuing an IETF last call.
The document appears to have been abandoned.
2024-01-16
01 Adrian Farrel Tag Other - see Comment Log set.
2024-01-16
01 Adrian Farrel IETF WG state changed to Dead WG Document from WG Document
2015-10-14
01 (System) Notify list changed from mpls-chairs@ietf.org, draft-ietf-mpls-ldp-iana@ietf.org to (None)
2011-11-14
01 (System) Ballot writeup text was added
2011-11-14
01 (System) Last call text was added
2011-11-14
01 (System) Ballot approval text was added
2011-11-14
01 (System) Document has expired
2011-11-14
01 (System) State changed to Dead from AD is watching.
2011-10-27
01 Adrian Farrel State changed to AD is watching from AD Evaluation::External Party.
2011-09-27
01 Adrian Farrel State changed to AD Evaluation::External Party from AD Evaluation.
Questions sent to document shepherd
2011-09-27
01 Adrian Farrel State changed to AD Evaluation from Publication Requested.
2011-09-27
01 Adrian Farrel Ballot writeup text changed
2011-09-26
01 Amy Vezza
PROTO writeup for draft-ietf-mpls-ldp-iana-01

  (1.a) Who is the Document Shepherd for this document? Has the
        Document Shepherd personally reviewed this …
PROTO writeup for draft-ietf-mpls-ldp-iana-01

  (1.a) Who is the Document Shepherd for this document? Has the
        Document Shepherd personally reviewed this version of the
        document and, in particular, does he or she believe this
        version is ready for forwarding to the IESG for publication?

Ross Callon is the Document Shepherd for draft-ietf-mpls-ldp-iana. He has read the document and believes that it is ready for publication.

  (1.b) Has the document had adequate review both from key WG members
        and from key non-WG members? Does the Document Shepherd have
        any concerns about the depth or breadth of the reviews that
        have been performed? 

Adequate review. No concerns.

  (1.c) Does the Document Shepherd have concerns that the document
        needs more review from a particular or broader perspective,
        e.g., security, operational complexity, someone familiar with
        AAA, internationalization or XML?

No concerns.

  (1.d) Does the Document Shepherd have any specific concerns or
        issues with this document that the Responsible Area Director
        and/or the IESG should be aware of?

No concerns.

  (1.e) How solid is the WG consensus behind this document?

Good consensus. No objections.

  (1.f) Has anyone threatened an appeal or otherwise indicated extreme
        discontent?

No discontent expressed.

  (1.g) Has the Document Shepherd personally verified that the
        document satisfies all ID nits?

Yes. Passes nits with no issues found.

  (1.h) Has the document split its references into normative and
        informative?

Both references are normative, which is appropriate. Both are to existing RFCs (one standards track, on a BCP).

  (1.i) Has the Document Shepherd verified that the document IANA
        consideration section exists and is consistent with the body
        of the document?

The IANA section exists, and is the body of the document.

  (1.j) Has the Document Shepherd verified that sections of the
        document that are written in a formal language, such as XML
        code, BNF rules, MIB definitions, etc., validate correctly in
        an automated checker?

Not applicable.

  (1.k) The IESG approval announcement includes a Document
        Announcement Write-Up. Please provide such a Document
        Announcement Write-Up? Recent examples can be found in the
        "Action" announcements for approved documents. The approval
        announcement contains the following sections:

    Technical Summary

This document augments the Internet Assigned Numbers Authority (IANA) considerations for the Label Distribution Protocol (LDP), for protocol fields that are Reserved in the LDP Specification but for which there are no IANA allocation policies.

    Working Group Summary

Progression of this document through the WG was smooth with no concerns or objections.

    Document Quality
       
This document establishes IANA rules for LDP protocol fields. LDP is widely deployed, including deployment in many multi-vendor networks.
2011-09-26
01 Amy Vezza Draft added in state Publication Requested
2011-09-26
01 Amy Vezza [Note]: 'Ross Callon (rcallon@juniper.net) is the Document Shepherd.' added
2011-05-13
01 (System) New version available: draft-ietf-mpls-ldp-iana-01.txt
2011-05-10
00 (System) New version available: draft-ietf-mpls-ldp-iana-00.txt