IETF Administrative Support Activity 2.0: Consolidated Updates to IETF Administrative Terminology
draft-ietf-iasa2-consolidated-upd-07

[Ballot comment]
It's not entirely clear to  me what criteria were used to split normative/informative
references; e.g., normally when we Update a document that will end up being a
normative reference, but 3929 is listed here as informative.

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

The IANA Functions Operator has reviewed draft-ietf-iasa2-consolidated-upd-07, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
Senior IANA Services Specialist

1. Summary

draft-ietf-iasa2-consolidated-upd makes a number of minor terminology changes to a large number of existing process RFCs in order to reflect the changes to the administration of the IETF documented in the IASA 2.0 WG. For the most part, these are changes that reflect the new distinction between the Executive Director of the LLC role and the Managing Director of the Secretariat. These language updates ensure the consistency of existing IETF process documents with the updated structure of IASA 2.0.

draft-ietf-iasa2-consolidated-upd will, if approved update RFCs 2028, 2418, 3005, 3710, 3929, 4633, and 6702. In order to update those documents, the IASA2.0 WG has asked for publication of this document as a BCP.

2. Review and Consensus

This document was thoroughly reviewed by the IASA2.0 WG. It was the result of a suggestion that attempted to prevent the working group from burdening the RFC series (and the IESG) with a number of very small updates to several documents. There was considerable discussion about which documents warranted an independent RFC and which could be bundled into this consolidated update. No worrisome issues arose in WGLC, and a post-WGLC version was issued to address minor comments. The chairs believe this document has strong support from the WG.

3. Intellectual Property

This document is not a protocol specification and it contains no technical solutions that might require a disclosure.

4. Other Points

IDnits complains that the Abstract does not enumerate the several RFCs that this document updates or obsoletes. Some of those documents are informational, but are listed in the "Normative References" section as those documents are changed (or destroyed) by this specification. This throws a number of downref flags in IDnits, but is unlikely to cause any actual confusion.

The following Last Call announcement was sent out (ends 2019-04-01):

From: The IESG
To: IETF-Announce
CC: jon.peterson@neustar.biz, iasa20@ietf.org, alissa@cooperw.in, Jon Peterson , iasa2-chairs@ietf.org, draft-ietf-iasa2-consolidated-upd@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Consolidated IASA 2.0 Updates of IETF Administrative Terminology) to Best Current Practice


The IESG has received a request from the IETF Administrative Support Activity
2 WG (iasa2) to consider the following document: - 'Consolidated IASA 2.0
Updates of IETF Administrative Terminology'
  as Best Current Practice

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-04-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


  In 2018, the IETF began the transition to a new administrative
  structure and updated its IETF Administrative Support Activity (IASA)
  to a new "IASA 2.0" structure.  In addition to more substantive
  changes that are described in other documents, the transition to the
  2018 IETF Administrative Support structure changes several position
  titles and organizational relationships that are referenced
  elsewhere.  Rather than reissue those referencing documents
  individually, this specification provides updates to them and
  deprecates some now-obsolete documents to ensure that there is no
  confusion due to these changes.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-iasa2-consolidated-upd/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-iasa2-consolidated-upd/ballot/


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


The document contains these normative downward references.
See RFC 3967 for additional information:
    rfc3710: An IESG charter (Informational - IETF stream)
    rfc6702: Promoting Compliance with Intellectual Property Rights (IPR) Disclosure Rules (Informational - IETF stream)
    draft-ietf-iasa2-trust-rationale: Discussion of the IASA 2.0 Changes as They Relate to the IETF Trust (None - IETF stream)
    draft-ietf-iasa2-rfc7437bis: IAB, IESG, IETF Trust and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees (None - IETF stream)

1. Summary

draft-ietf-iasa2-consolidated-upd makes a number of minor terminology changes to a large number of existing process RFCs in order to reflect the changes to the administration of the IETF documented in the IASA 2.0 WG. For the most part, these are changes that reflect the new distinction between the Executive Director of the LLC role and the Managing Director of the Secretariat. These language updates ensure the consistency of existing IETF process documents with the updated structure of IASA 2.0.

draft-ietf-iasa2-consolidated-upd will, if approved, obsolete RFCs 3716, 3929, and 4633, and update RFCs 2028, 2418, 3005, 3710, and 6702. In order to update those documents, the IASA2.0 WG has asked for publication of this document as a BCP.

2. Review and Consensus

This document was thoroughly reviewed by the IASA2.0 WG. It was the result of a suggestion that attempted to prevent the working group from burdening the RFC series (and the IESG) with a number of very small updates to several documents. There was considerable discussion about which documents warranted an independent RFC and which could be bundled into this consolidated update. No worrisome issues arose in WGLC, and a post-WGLC version was issued to address minor comments. The chairs believe this document has strong support from the WG.

3. Intellectual Property

This document is not a protocol specification and it contains no technical solutions that might require a disclosure.

4. Other Points

IDnits complains that the Abstract does not enumerate the several RFCs that this document updates or obsoletes. Some of those documents are informational, but are listed in the "Normative References" section as those documents are changed (or destroyed) by this specification. This throws a number of downref flags in IDnits, but is unlikely to cause any actual confusion.

1. Summary

draft-ietf-iasa2-consolidated-upd makes a number of minor terminology changes to a large number of existing process RFCs in order to reflect the changes to the administration of the IETF documented in the IASA 2.0 WG. For the most part, these are changes that reflect the new distinction between the Executive Director of the LLC role and the Managing Director of the Secretariat. These language updates ensure the consistency of existing IETF process documents with the updated structure of IASA 2.0.

draft-ietf-iasa2-consolidated-upd will, if approved, obsolete RFCs 3716, 3929, and 4633, and update RFCs 2028, 2418, 3005, 3710, and 6702. In order to update those documents, the IASA2.0 WG has asked for publication of this document as a BCP.

2. Review and Consensus

This document was thoroughly reviewed by the IASA2.0 WG. It was the result of a suggestion that attempted to prevent the working group from burdening the RFC series (and the IESG) with a number of very small updates to several documents. There was considerable discussion about which documents warranted an independent RFC and which could be bundled into this consolidated update. No worrisome issues arose in WGLC, and a post-WGLC version was issued to address minor comments. The chairs believe this document has strong support from the WG.

3. Intellectual Property

This document is not a protocol specification and it contains no technical solutions that might require a disclosure.

4. Other Points

IDnits complains that the Abstract does not enumerate the several RFCs that this document updates or obsoletes. Some of those documents are informational, but are listed in the "Normative References" section as those documents are changed (or destroyed) by this specification. This throws a number of downref flags in IDnits, but is unlikely to cause any actual confusion.

1. Summary

draft-ietf-iasa2-consolidated-upd makes a number of minor terminology changes to a large number of existing process RFCs in order to reflect the changes to the administration of the IETF documented in the IASA 2.0 WG. For the most part, these are changes that reflect the new distinction between the Executive Director of the LLC role and the Managing Director of the Secretariat. These language updates ensure the consistency of existing IETF process documents with the updated structure of IASA 2.0.

draft-ietf-iasa2-consolidated-upd will, if approved, obsolete RFCs 3716, 3929, and 4633, and update RFCs 2028, 2418, 3005, 3710, and 6702. In order to update those documents, the IASA2.0 WG has asked for publication of this document as a BCP.

2. Review and Consensus

This document was thoroughly reviewed by the IASA2.0 WG. It was the result of a suggestion that attempted to prevent the working group from burdening the RFC series (and the IESG) with a number of very small updates to several documents. There was considerable discussion about which documents warranted an independent RFC and which could be bundled into this consolidated update. No worrisome issues arose in WGLC, and a post-WGLC version was issued to address minor comments. The chairs believe this document has strong support from the WG.

3. Intellectual Property

This document is not a protocol specification and it contains no technical solutions that might require a disclosure.

4. Other Points

IDnits complains that the Abstract does not enumerate the several RFCs that this document updates or obsoletes. Some of those documents are informational, but are listed in the "Normative References" section as those documents by this specification. This throws a number of downref flags in IDnits, but is unlikely to cause any actual confusion.

There was one minor change suggested - which was to update the title to something like "Consolidated Updates of IETF Administrative Terminology". This is a minor change and the doc can be updated as Jon works on shepherding this and the other IASA2 documents.

As per prior notation, WGLC complete with 2 minor tweaks needed to the document. Once those changes are made we will package this with other drafts for IESG/IAB/IETFLC/RFCE.