IESG agenda: 2018-04-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: March 8, 2018

  o Kathleen Moriarty and Benjamin Kaduk to find a designated expert for 
    RFC 5793 [IANA #1050763].
    - Added 2018-02-22 (2 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-sidr-slurm
Proposed Standard
Simplified Local internet nUmber Resource Management with the RPKI
Token
Alvaro Retana (RTG area)
IANA review
Version Changed - Review Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-6tisch-6top-protocol
Proposed Standard
6top Protocol (6P)
Token
Suresh Krishnan (INT area)
IANA review
IANA - Review Needed
Consensus
Yes
Reviews
Last call expires
2018-03-26

IETF stream
draft-ietf-mmusic-trickle-ice-sip
Proposed Standard
A Session Initiation Protocol (SIP) Usage for Trickle ICE
Token
Ben Campbell (ART area)
IANA review
IANA OK - Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-pce-lsp-setup-type
Proposed Standard
Conveying path setup type in PCEP messages
Token
Deborah Brungard (RTG area)
IANA review
IANA OK - Actions Needed
Consensus
Yes
Reviews
Last call expires
2018-03-28

IETF stream
draft-ietf-6man-ndpioiana
Proposed Standard
IPv6 ND PIO Flags IANA considerations
Token
Suresh Krishnan (INT area)
IANA review
IANA OK - Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-6lo-rfc6775-update
Proposed Standard
Registration Extensions for 6LoWPAN Neighbor Discovery
Token
Suresh Krishnan (INT area)
IANA review
Version Changed - Review Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-ice-trickle
Proposed Standard
Trickle ICE: Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (ICE) Protocol
Token
Ben Campbell (ART area)
IANA review
IANA OK - Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-tls-iana-registry-updates
Proposed Standard
IANA Registry Updates for TLS and DTLS
Token
Benjamin Kaduk (SEC area)
IANA review
IANA OK - Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-tls-record-limit
Proposed Standard
Record Size Limit Extension for Transport Layer Security (TLS)
Token
Benjamin Kaduk (SEC area)
IANA review
IANA OK - Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-i2rs-rib-data-model
Proposed Standard
A YANG Data Model for Routing Information Base (RIB)
Token
Martin Vigoureux (RTG area)
IANA review
IANA - Review Needed
Consensus
Yes
Reviews
Last call expires
2018-03-30

IETF stream
draft-ietf-l2sm-l2vpn-service-model
Proposed Standard
A YANG Data Model for L2VPN Service Delivery
Token
Ignas Bagdonas (OPS area)
IANA review
IANA - Not OK
Consensus
Yes
Reviews

IETF stream
draft-ietf-i2rs-yang-dc-fabric-network-topology
Proposed Standard
A YANG Data Model for Fabric Topology in Data Center Networks
Token
Martin Vigoureux (RTG area)
IANA review
IANA - Review Needed
Consensus
Yes
Reviews
Last call expires
2018-04-03

2.1.2 Returning items

(None)

2.2 Individual submissions

2.2.1 New items

IETF stream
draft-ietf-trill-over-ip
Proposed Standard
TRILL (Transparent Interconnection of Lots of Links) Over IP Transport
Token
Martin Vigoureux (NONE area)
Deferred by
Mirja Kühlewind on 2018-03-08
IANA review
Version Changed - Review Needed
Consensus
Yes
Reviews

2.2.2 Returning items

(None)

2.3 Status changes

2.3.1 New items

IETF stream
status-change-bier-core-to-proposed-standard
None
Promote BIER Architecture and Encapsulation to Proposed Standard (based on updating charter)
Token
Alia Atlas (IETF area)
Deferred by
Eric Rescorla on 2018-03-08

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-teas-scheduled-resources
Informational
Framework for Scheduled Use of Resources
Token
Deborah Brungard (RTG area)
IANA review
IANA OK - No Actions Needed
Consensus
Yes
Reviews
Last call expires
2018-03-28
IPR
Director of licensing's Statement about IPR related to draft-ietf-teas-scheduled-resources
Huawei Technologies Co.,Ltd's Statement about IPR related to draft-ietf-teas-scheduled-resources

IETF stream
draft-ietf-rmcat-sbd
Experimental
Shared Bottleneck Detection for Coupled Congestion Control for RTP Media.
Token
Mirja Kühlewind (TSV area)
IANA review
IANA OK - No Actions Needed
Consensus
Unknown
Reviews

IETF stream
draft-ietf-i2rs-rib-info-model
Informational
Routing Information Base Info Model
Token
Martin Vigoureux (RTG area)
IANA review
IANA OK - No Actions Needed
Consensus
Yes
Reviews
Last call expires
2018-03-30

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-gutmann-scep
Informational
Simple Certificate Enrolment Protocol
Token
Alexey Melnikov (NONE area)
IANA review
IANA OK - Actions Needed
Consensus
Yes
Reviews

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.3.3 For action

IETF stream
status-change-kerberos-3des-rc4-to-historic
None
Deprecating 3DES and RC4 in Kerberos (Status Change)
Token
Eric Rescorla (IETF area)

3.4 IRTF and Independent Submission stream documents

The IESG will use RFC 5742 responses:

  1. The IESG has concluded that there is no conflict between this document and IETF work;
  2. The IESG has concluded that this work is related to IETF work done in WG <X>, but this relationship does not prevent publishing;
  3. 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;
  4. 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
  5. 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)

3.4.3 For action

Conflict review
conflict-review-nir-cfrg-rfc7539bis
IETF conflict review for draft-nir-cfrg-rfc7539bis
IRTF Informational
draft-nir-cfrg-rfc7539bis
ChaCha20 and Poly1305 for IETF Protocols
Token
Alissa Cooper

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)

5. IAB news we can use

6. Management issues

6.1 [IANA #1053888] Designated expert for RFC-irtf-cfrg-xmss-hash-based-signatures (Amanda Baber/IANA)

6.2 Network Configuration (netconf) Recharter

6.3 IESG Liaisons and Assignments

7. Any Other Business (WG News, New Proposals, etc.)