IESG agenda: 2019-09-05
1. Administrivia
1.1 Roll call
1.2 Bash the agenda
1.3 Approval of the minutes of past telechats
1.4 List of remaining action items from last telechat
OUTSTANDING TASKS
Last updated: August 22, 2019
o Ignas Bagdonas to propose an additional question on YANG Model
format validation for each of the styles of document write-ups.
- Added 2019-04-18 (8 telechats ago)
o Roman Danyliw to draft text to be posted on ietf.org about reporting
protocol vulnerabilities via an email alias and possible procedures
on how to assign triage resources.
- Added 2019-04-24 (8 telechats ago)
o Martin Vigoureux to work with the IESG to create a list of possible
IESG Tutorials and will prioritize them for scheduling on a series
of Informal Telechats.
- Added 2019-04-24 (8 telechats ago)
o Eric Vyncke to write up draft text for the NomCom to help them
understand the rules for the NomCom.
- Added 2019-04-25 (8 telechats ago)
o Roman Danyliw to shepherd the www.ietf.org analytics discussion
with the community.
- Added 2019-04-25 (8 telechats ago)
o Alexey Melnikov to find designated experts for RFC-ietf-core-object-
security [IANA #1141664].
- Added 2019-05-01 (8 telechats ago)
o Alexey Melnikov to find designated experts for RFC 8554 [IANA
#1142796].
- Added 2019-05-16 (7 telechats ago)
o Alexey Melnikov to find designated experts for RFC 8610 [IANA
#1145107].
- Added 2019-06-14 (4 telechats ago)
o Ignas Bagdonas to find designated experts for RFC 7317 [IANA
#1146017].
- Added 2019-06-26 (4 telechats ago)
o Adam Roach to collate the list of specific "hot topic" items from
each Area that will be provided to document authors and post it on
the wiki.
- Added 2019-06-27 (4 telechats ago)
o Barry Leiba to come up with a proposal for moving Last Call
discussions to a separate mailing list.
- Added 2019-08-08 (2 telechat ago)
o Suresh Krishnan to ask Heather F and Sandy G to introduce the
Updates Tags Document (draft-kuehlewind-update-tag) to the RFC-
Interest email list for discussion, and inform the community via the
IETF discussion list with a pointer to RFC-Interest.
- Added 2019-08-15 (1 telechats ago)
o Adam Roach to send a message to the tools team cc Roman as
liaison about removing the required date associated with milestones
on WG Charters.
- Added 2019-08-15 (1 telechats ago)
2. Protocol actions
Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?"
2.1 WG submissions
2.1.1 New items
- IETF stream
- draft-ietf-iasa2-rfc7776bis
- Best Current Practice
- Update to the IETF Anti-Harassment Procedures for the Replacement of the IAOC with the IETF Administration LLC
- Token
- Alissa Cooper (GEN area)
- IANA review
- IANA OK - No Actions Needed
- Consensus
- Yes
- Reviews
- IETF stream
- draft-ietf-core-senml-etch (Has RFC Editor Note)
- Proposed Standard
- FETCH & PATCH with Sensor Measurement Lists (SenML)
- Token
- Alexey Melnikov (ART area)
- IANA review
- IANA - Review Needed
- Consensus
- Yes
- Reviews
- Last call expires
- 2019-09-02
- IETF stream
- draft-ietf-netmod-artwork-folding
- Best Current Practice
- Handling Long Lines in Inclusions in Internet-Drafts and RFCs
- Token
- Ignas Bagdonas (OPS area)
- IANA review
- IANA OK - No Actions Needed
- Consensus
- Yes
- Reviews
2.1.2 Returning items
(None)
2.2 Individual submissions
2.2.1 New items
(None)
2.2.2 Returning items
(None)
2.3 Status changes
2.3.1 New items
(None)
2.3.2 Returning items
(None)
3. Document actions
3.1 WG submissions
Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?"
3.1.1 New items
- IETF stream
- draft-ietf-iasa2-rfc5377bis
- Informational
- Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents
- Token
- Alissa Cooper (GEN area)
- IANA review
- Version Changed - Review Needed
- Consensus
- Unknown
- Reviews
3.1.2 Returning items
(None)
3.2 Individual submissions via AD
Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?"
3.2.1 New items
(None)
3.2.2 Returning items
(None)
3.3 Status changes
Reviews should focus on these questions: "Are the proposed changes to document status appropriate? Have all requirements for such a change been met? If not, what changes to the proposal would make it appropriate?"
3.3.1 New items
(None)
3.3.2 Returning items
(None)
3.4 IRTF and Independent Submission stream documents
The IESG will use RFC 5742 responses:
- The IESG has concluded that there is no conflict between this document and IETF work;
- The IESG has concluded that this work is related to IETF work done in WG <X>, but this relationship does not prevent publishing;
- The IESG has concluded that publication could potentially disrupt the IETF work done in WG <X> and recommends not publishing the document at this time;
- The IESG has concluded that this document violates IETF procedures for <Y> and should therefore not be published without IETF review and IESG approval; or
- The IESG has concluded that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval.
The document shepherd must propose one of these responses in the conflict-review document, and the document shepherd may supply text for an IESG Note in that document. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd and agreement that the IESG should request inclusion of the IESG Note.
Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document.
3.4.1 New items
- Conflict review
-
conflict-review-ise-iana-policy
IETF conflict review for draft-ise-iana-policy - ISE Informational
-
draft-ise-iana-policy
How Requests for IANA Action Will be Handled on the Independent Stream - Token
- Alissa Cooper
3.4.2 Returning items
(None)
4. Working Group actions
4.1 WG creation
4.1.1 Proposed for IETF review
(None)
4.1.2 Proposed for approval
(None)
4.2 WG rechartering
4.2.1 Under evaluation for IETF review
- WG name
- Audio/Video Transport Core Maintenance (avtcore)
- Charter
- charter-ietf-avtcore-(02-00)
- Area
- ART (Barry Leiba)
4.2.2 Proposed for approval
- WG name
- Autonomic Networking Integrated Model and Approach (anima)
- Charter
- charter-ietf-anima-(01-08)
- Area
- OPS (Ignas Bagdonas)