IESG agenda: 2016-03-17
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: March 4, 2016
o Alia Atlas to draft an FAQ on interactions in the IETF.
- Added 2015-12-17 (6 telechats ago)
o Jari Arkko to talk to the current moderators of ietf@ietf list on
where to draw the line between guidance and moderation.
- Added 2015-12-17 (6 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-tictoc-ptp-mib
- Proposed Standard
- Precision Time Protocol Version 2 (PTPv2) Management Information Base
- Token
- Brian Haberman (INT area)
- IANA review
- IANA OK - Actions Needed
- Consensus
- No
- Last call expires
- 2016-03-08
- IETF stream
- draft-ietf-tsvwg-circuit-breaker
- Best Current Practice
- Network Transport Circuit Breakers
- Token
- Spencer Dawkins (TSV area)
- IANA review
- IANA OK - No Actions Needed
- Consensus
- Yes
- IETF stream
- draft-ietf-opsawg-hmac-sha-2-usm-snmp-new
- Proposed Standard
- HMAC-SHA-2 Authentication Protocols in USM for SNMPv3
- Token
- Joel Jaeggli (OPS area)
- IANA review
- Version Changed - Review Needed
- Consensus
- Yes
- IETF stream
- draft-ietf-mmusic-proto-iana-registration
- Proposed Standard
- IANA registrations of SDP 'proto' attribute for transporting RTP Media over TCP under various RTP profiles.
- Token
- Ben Campbell (ART area)
- IANA review
- Version Changed - Review Needed
- Consensus
- Unknown
- IETF stream
- draft-ietf-rtcweb-audio
- Proposed Standard
- WebRTC Audio Codec and Processing Requirements
- Token
- Alissa Cooper (ART area)
- IANA review
- IANA OK - No Actions Needed
- Consensus
- Unknown
- Last call expires
- 2016-03-09
- IETF stream
- draft-ietf-dprive-dns-over-tls
- Proposed Standard
- Specification for DNS over TLS
- Token
- Terry Manderson (INT area)
- IANA review
- IANA - Review Needed
- Consensus
- Unknown
- Last call expires
- 2016-03-15
- IETF stream
- draft-ietf-cdni-redirection
- Proposed Standard
- Request Routing Redirection interface for CDN Interconnection
- Token
- Barry Leiba (ART area)
- IANA review
- IANA - Review Needed
- Consensus
- Unknown
- Last call expires
- 2016-03-16
- IPR
-
Juniper Networks, Inc.'s Statement about IPR related to draft-ietf-cdni-redirection
- IETF stream
- draft-ietf-netext-pmipv6-flowmob
- Proposed Standard
- Proxy Mobile IPv6 Extensions to Support Flow Mobility
- Token
- Brian Haberman (INT area)
- IANA review
- IANA - Review Needed
- Consensus
- Unknown
- Last call expires
- 2016-03-15
- IETF stream
- draft-ietf-netmod-yang-json
- Proposed Standard
- JSON Encoding of Data Modeled with YANG
- Token
- Benoit Claise (OPS area)
- IANA review
- IANA OK - No Actions Needed
- Consensus
- Yes
- Last call expires
- 2016-03-09
- IETF stream
- draft-ietf-netmod-yang-metadata
- Proposed Standard
- Defining and Using Metadata with YANG
- Token
- Benoit Claise (OPS area)
- IANA review
- IANA - Not OK
- Consensus
- Yes
- Last call expires
- 2016-03-09
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-p2psip-concepts
- Informational
- Concepts and Terminology for Peer to Peer SIP
- Token
- Alissa Cooper (ART area)
- IANA review
- IANA OK - No Actions Needed
- Consensus
- Unknown
- IETF stream
- draft-ietf-v6ops-ipv6-ehs-in-real-world
- Informational
- Observations on the Dropping of Packets with IPv6 Extension Headers in the Real World
- Token
- Joel Jaeggli (OPS area)
- IANA review
- IANA OK - No Actions Needed
- Consensus
- Yes
- IETF stream
- draft-ietf-rtcweb-audio-codecs-for-interop
- Informational
- Additional WebRTC audio codecs for interoperability.
- Token
- Alissa Cooper (ART area)
- IANA review
- IANA OK - No Actions Needed
- Consensus
- Unknown
- Last call expires
- 2016-03-09
- IETF stream
- draft-ietf-aqm-fq-codel
- Experimental
- FlowQueue-Codel
- Token
- Martin Stiemerling (TSV area)
- IANA review
- IANA - Review Needed
- Consensus
- Unknown
- Last call expires
- 2016-03-17
- IETF stream
- draft-ietf-aqm-docsis-pie
- Informational
- A PIE-Based AQM for DOCSIS Cable Modems
- Token
- Martin Stiemerling (TSV area)
- IANA review
- IANA - Review Needed
- Consensus
- Unknown
- Last call expires
- 2016-03-15
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
- IETF stream
- draft-martin-urn-globus
- Informational
- A URN Namespace for Globus
- Token
- Barry Leiba (ART area)
- IANA review
- IANA - Review Needed
- Consensus
- Unknown
- Last call expires
- 2016-03-09
- IETF stream
- draft-schoenw-opsawg-copspr-historic
- Informational
- Reclassification of COPS-PR and SPPI to Historic
- Note
- To follow the procedure 2 at http://www.ietf.org/iesg/statement/designating-rfcs-as-historic.html, we need an IETF Last Call of 2 weeks for draft-schoenw-opsawg-copspr-historic-03
https://datatracker.ietf.org/doc/status-change-copspr-sppi-to-historic/ had already its 2 weeks IETF Last Call - Token
- Benoit Claise (OPS area)
- IANA review
- IANA - Review Needed
- Consensus
- Unknown
- Last call expires
- 2016-03-30
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
(None)
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
(None)
4.2.2 Proposed for approval
(None)