IS-IS Prefix Attributes for Extended IPv4 and IPv6 Reachability
draft-ietf-isis-prefix-attributes-04

(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

IANA has completed its review of draft-ietf-isis-prefix-attributes-03.txt. If any part of this review is inaccurate, please let us know.

IANA has a question about one of the actions requested in the IANA Considerations Section of the current document.

IANA understands that, upon approval of this document, there are two actions which IANA must complete.

First, in the Sub-TLVs for TLVs 135, 235, 236, and 237 subregistry of the IS-IS TLV Codepoints registry located at:

http://www.iana.org/assignments/isis-tlv-codepoints/

The following temporary registrations for values 4, 11, an 12 are to be made permanent and the reference is to be changed to [ RFC-to-be ].

Second, a new registry is to be created.

IANA Question --> What is the new registry to be called?

The new registry is to be located in the existing IS-IS TLV Codepoints registry located at:

http://www.iana.org/assignments/isis-tlv-codepoints/

The registration policy for the new registry is Expert Review as defined in RFC 5226.

There are initial registrations in the new registry as follows:

Bit # Name Reference
----- ------------------------ -------------
0 External Prefix Flag [ RFC-to-be ]
1 Re-advertisement Flag [ RFC-to-be ]
2 Node Flag [ RFC-to-be ]


IANA understands that the two actions above are the only ones required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed. 


Thank you,

Sabrina Tanamal
IANA Specialist
ICANN

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: draft-ietf-isis-prefix-attributes@ietf.org, isis-wg@ietf.org, chopps@chopps.org, akatlas@gmail.com, "Christian Hopps" , isis-chairs@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (IS-IS Prefix Attributes for Extended IP and IPv6 Reachability) to Proposed Standard


The IESG has received a request from the IS-IS for IP Internets WG (isis)
to consider the following document:
- 'IS-IS Prefix Attributes for Extended IP and IPv6 Reachability'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-01-01. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document introduces new sub-TLVs to support advertisement of
  prefix attribute flags and the source router ID of the router which
  originated a prefix advertisement.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-isis-prefix-attributes/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-isis-prefix-attributes/ballot/


No IPR declarations have been submitted directly on this I-D.

Technical issues were addressed - but there are still 7 authors/editors.
Some need to be move to contributors or have a good justification for
each and why more than 5 authors/editors - as per RFC Editor guidelines
- is appropriate.

AD Review comments:

1)  This draft has 7 authors.  The limit is 5; you can pick an editor if you can't trim
down to 5.  I can, of course, listen to a clear write-up of contributions made by each
author of this 7 page draft, if you feel that an exception is truly warranted.  Until this
issue is addressed, I will not progress this draft.

2) The Security Considerations section is completely empty.  You know that this
needs to be filled in - if only as a reference to the existing ISIS security and a bit
on why sending additional information isn't a concern. 

3)  As a minor kvetch (meaning that you don't have to agree), I'd prefer to see
a bit of motivation or how this is expected to be used.  There's a very small amount
of motivation from SR - but that doesn't really explain the need to send the originating
Router ID. 

4) Clarifying question:  When a prefix has the external prefix flag set and the Router ID is sent, is that the Router ID of the router that is doing the redistribution or of the original advertising router (if it were available)?

PROTO Questionaire and Write-up for: draft-ietf-isis-prefix-attributes-01

Shepherding WG-Chair: Chris Hopps (chopps@chopps.org)

    (1) What type of RFC is being requested (BCP, Proposed Standard,
    Internet Standard, Informational, Experimental, or Historic)? Why is
    this the proper type of RFC? Is this type of RFC indicated in the title
    page header?

Proposed Standard

    (2) 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:

    Relevant content can frequently be found in the abstract and/or
    introduction of the document. If not, this may be an indication that
    there are deficiencies in the abstract or introduction.

This document introduces new sub-TLVs to support advertisement of
prefix attribute flags and the source router ID of the router which
originated a prefix advertisement.

    Working Group Summary:

    Was there anything in WG process that is worth noting? For example, was
    there controversy about particular points or were there decisions where
    the consensus was particularly rough?

There was no controversy in the WG over this draft.

    Document Quality:

    Are there existing implementations of the protocol? Have a significant
    number of vendors indicated their plan to implement the specification?
    Are there any reviewers that merit special mention as having done a
    thorough review, e.g., one that resulted in important changes or a
    conclusion that the document had no substantive issues? If there was a
    MIB Doctor, Media Type or other expert review, what was its course
    (briefly)? In the case of a Media Type review, on what date was the
    request posted?

There is good interest in the industry to implementing this standard.

    Personnel:

    Who is the Document Shepherd? Who is the Responsible Area Director?

Shepherd: Christian Hopps.
AD: Alia Atlas.

    (3) Briefly describe the review of this document that was performed by
    the Document Shepherd. If this version of the document is not ready for
    publication, please explain why the document is being forwarded to the
    IESG.

I have reviewed this document and believe it is ready for publication.

    (4) Does the document Shepherd have any concerns about the depth or
    breadth of the reviews that have been performed?

No

    (5) Do portions of the document need review from a particular or from
    broader perspective, e.g., security, operational complexity, AAA, DNS,
    DHCP, XML, or internationalization? If so, describe the review that took
    place.

No special review is needed.

    (6) Describe any specific concerns or issues that the Document Shepherd
    has with this document that the Responsible Area Director and/or the
    IESG should be aware of? For example, perhaps he or she is uncomfortable
    with certain parts of the document, or has concerns whether there really
    is a need for it. In any event, if the WG has discussed those issues and
    has indicated that it still wishes to advance the document, detail those
    concerns here.

No specific concerns.

    (7) Has each author confirmed that any and all appropriate IPR
    disclosures required for full conformance with the provisions of BCP 78
    and BCP 79 have already been filed. If not, explain why?

Yes.

    (8) Has an IPR disclosure been filed that references this document? If
    so, summarize any WG discussion and conclusion regarding the IPR
    disclosures.

No.

    (9) How solid is the WG consensus behind this document? Does it
    represent the strong concurrence of a few individuals, with others being
    silent, or does the WG as a whole understand and agree with it?

Strong consensus in the WG.

    (10) Has anyone threatened an appeal or otherwise indicated extreme
    discontent? If so, please summarise the areas of conflict in separate
    email messages to the Responsible Area Director. (It should be in a
    separate email because this questionnaire is publicly available.)

No

    (11) Identify any ID nits the Document Shepherd has found in this
    document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
    Checklist). Boilerplate checks are not enough; this check needs to be
    thorough.

Reference needs increment/updating.

    (12) Describe how the document meets any required formal review
    criteria, such as the MIB Doctor, media type, and URI type reviews.

N/A.

    (13) Have all references within this document been identified as either
    normative or informative?

Yes.

    (14) Are there normative references to documents that are not ready for
    advancement or are otherwise in an unclear state? If such normative
    references exist, what is the plan for their completion?

No.

    (15) Are there downward normative references references (see RFC 3967)?
    If so, list these downward references to support the Area Director in
    the Last Call procedure.

No.

    (16) Will publication of this document change the status of any existing
    RFCs? Are those RFCs listed on the title page header, listed in the
    abstract, and discussed in the introduction? If the RFCs are not listed
    in the Abstract and Introduction, explain why, and point to the part of
    the document where the relationship of this document to the other RFCs
    is discussed. If this information is not in the document, explain why
    the WG considers it unnecessary.

No.

    (17) Describe the Document Shepherd's review of the IANA considerations
    section, especially with regard to its consistency with the body of the
    document. Confirm that all protocol extensions that the document makes
    are associated with the appropriate reservations in IANA
    registries. Confirm that any referenced IANA registries have been
    clearly identified. Confirm that newly created IANA registries include a
    detailed specification of the initial contents for the registry, that
    allocations procedures for future registrations are defined, and a
    reasonable name for the new registry has been suggested (see RFC 5226).

IANA section has been reviewed and is sufficient. Entries to existing
registries, as well as a new registry for prefix attribute flags
are clearly articulated.

    (18) List any new IANA registries that require Expert Review for future
    allocations. Provide any public guidance that the IESG would find useful
    in selecting the IANA Experts for these new registries.

A new registry for the definition of prefix attribute flags is being
created. Existing IS-IS expert review is considered sufficient.

    (19) Describe reviews and automated checks performed by the Document
    Shepherd to validate sections of the document written in a formal
    language, such as XML code, BNF rules, MIB definitions, etc.

N/A.