Guidelines and Registration Procedures for Interface Types and Tunnel Types
draft-thaler-iftype-reg-07

[Ballot comment]
Section 6.1

  5.  If instead the Designated Expert does not approve registration
      (e.g., for any of the reasons in [RFC8126] section 3), a
      registrant can resubmit a corrected request if desired, or the
      IESG can override the Designated Expert and approve it per the
      process in Section 5.3 of [RFC8126].

These section references look like they're for RFC 5226's sections and
should be updated for RFC 8126's different layout.  (So, 5, and 3.3,
respectively, it seems, in an amusing numerological twist.)

Section 9.2

[I thought IANA did not guarantee stability of the anchor portion of
links, and preferred that we not include them in references.  Maybe this
case is special?]

[Ballot comment]
First, a small note on the shepherd write-up: it should be "individual submission" and not "independent submission".

And one quick question:
Should section 4 use some normative SHOULDs?

(While at the same time I have to say that I fine the use of MUSTs in section 6 rather unusual.)

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

The IANA Functions Operator has completed its review of draft-thaler-iftype-reg-05.

IANA will work with the authors required in the IANA Considerations section to ensure that the IANA Actions are correctly executed.

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 meant only to confirm the list of actions that will be performed.

Thank you,

Sabrina Tanamal
Senior IANA Services Specialist

The following Last Call announcement was sent out (ends 2019-11-07):

From: The IESG
To: IETF-Announce
CC: draft-thaler-iftype-reg@ietf.org, suresh@kaloom.com, ianfarrer@gmx.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Guidelines and Registration Procedures for Interface Types and Tunnel Types) to Proposed Standard


The IESG has received a request from an individual submitter to consider the
following document: - 'Guidelines and Registration Procedures for Interface
Types and Tunnel
  Types'
  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 2019-11-07. 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


  The registration and use of interface types ("ifType" values)
  predated the use of IANA Considerations sections and YANG modules,
  and so confusion has arisen about the interface type allocation
  process.  Tunnel types were then added later, with the same
  requirements and allocation policy as interface types.  This document
  updates RFC 2863, and provides updated guidelines for the definition
  of new interface types and tunnel types, for consideration by those
  who are defining, registering, or evaluating those definitions.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-thaler-iftype-reg/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-thaler-iftype-reg/ballot/


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

(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?

Intended status: Standards Track (Indicated on the title page)
This document describes updated processes and templates for registering new ifType or tunnelType values with IANA, updating RFC2863 (also Standards Track).

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

This document identifies a number of problems with the existing ifType and tunnelType IANA registries which have arisen as their use has grown beyond the original scope for use with MIB modules (as defined in RFC2863). The document extends the applicability of RFC2863 to include YANG modules. It also contains procedures and templates for the registration of new ifType or tunnelType entries.

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?

No. This document was submitted through the Independent Submissions stream as an AD sponsored submission. It has been reviewed and discussed across several WGs (int-area, dhcwg, softwires, OPSAWG and v6ops).


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?

N/A

Personnel:

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

Ian Farrer is the Document Shepherd
Suresh Krishnan is the Responsible AD

(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.

The document has been reviewed by the Document Shepherd for content, completeness and language. The document is well written and 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.

(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.

N/A.

(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?

As the document is an independent submission, there is no directly responsible w/g. However, the draft, and questions that have arisen during the authoring process have been cross posted to int-area, dhcwg, softwires, OPSAWG and v6ops generating discussion and review comments which have been addressed. The draft was also presented in Int-area at IETF104 and IETF105.

(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.

I-D Nits shows the following relation to the RFC2863 update in the header:

    (Using the creation date from RFC2863, updated by this document, for
    RFC5378 checks: 2000-03-14)

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
    have content which was first submitted before 10 November 2008.  If you
    have contacted all the original authors and they are all willing to grant
    the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
    this comment.  If not, you may need to add the pre-RFC5378 disclaimer.
    (See the Legal Provisions document at
    https://trustee.ietf.org/license-info for more information.)

From discussion with the authors and AD, the consensus was that the pre-RFC5378 disclaimer does not need to be included as this document does not include any text from RFC2863.

(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.

This document updates RFC2863, specifically sections 3.1.1 & 3.1.2. RFC2863 was concerned only with interface MIB modules and this document extends the applicability of RFC2863 to include YANG modules. The update is indicated in the title page header.

(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 8126).

As the whole of the document is concerned solely with IANA processes, there are no additional IANA considerations in this section.

(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.

No new registries are created by this document.

(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.

None (no formal language is included in the document).