IESG agenda: 2018-12-20

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: December 6, 2018

  o Eric Rescorla to find designated experts for RFC 8411 [IANA 
    #1120853].
    - Added 2018-08-29 (7 telechats ago) 
  o Eric Rescorla to find designated experts for RFC 6509 
    (mikey-payloads) [IANA #1121057].
    - Added 2018-08-30 (6 telechats ago) 
  o Eric Rescorla to find designated experts for RFC 6043
    (mikey-payloads) [IANA #1121239].
    - Added 2018-08-31 (6 telechats ago) 
  o Eric Rescorla to find designated experts for RFC 6267
    (mikey-payloads) [IANA #1121240].
    - Added 2018-08-31 (6 telechats ago) 
  o Eric Rescorla to find designated experts for RFC 6309
    (mikey-payloads) [IANA #1121241].
    - Added 2018-08-31 (6 telechats ago) 
  o Alvaro Retana to follow up on discussion at IETF 103 about putting 
    major discussion points and decisions in the IESG Wiki.
    - Added 2018-11-21 (2 telechats ago) 
  o Alvaro Retana to follow up on how to document decisions made during 
    face-to-face IESG conversations.
    - Added 2018-11-21 (2 telechats ago) 
  o Deborah Brungard to draft text to the WG Chairs list on the subject 
    of community relations, including information about what avenues are 
    open to chairs for escalating issues.
    - Added 2018-11-29 (1 telechat ago) 
  o Alissa Cooper to draft text informing the community about the 
    ongoing discussion with the WG chairs about community relations, 
    including information about what avenues are open to community 
    members for escalating issues.
    - Added 2018-11-29 (1 telechat ago) 
  o Spencer Dawkins to send a request to the tools team to set up a 
    mechanism by which documents that have been newly adopted into 
    working groups are automatically announced to the community as being 
    newly adopted.
    - Added 2018-11-29 (1 telechat ago) 
  o Alvaro Retana to send email to the IESG with proposed re-labeling of 
    scheduling conflicts.
    - Added 2017-12-06 (1 telechat 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-alto-xdom-disc
Proposed Standard
Application Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery
Token
Mirja K├╝hlewind (TSV area)
Deferred by
Benjamin Kaduk on 2018-12-06
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

(None)

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-wilde-service-link-rel
Informational
Link Relation Types for Web Services
Note
Checking with HTTPBIS whether there are any objections to publish.
Token
Alexey Melnikov (ART area)
IANA review
IANA OK - Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-wilde-sunset-header
Informational
The Sunset HTTP Header
Note
Checking with HTTPBIS whether there are any objections to publish.

It is not clear whether this document needs to be Proposed Standard, Informational would suffice for a header field registration.
Token
Alexey Melnikov (ART 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.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

Conflict review
conflict-review-browne-sfc-nsh-kpi-stamp
IETF conflict review for draft-browne-sfc-nsh-kpi-stamp
ISE Informational
draft-browne-sfc-nsh-kpi-stamp
A Key Performance Indicators (KPI) Stamping for the Network Service Header (NSH)
Token
Martin Vigoureux

Conflict review
conflict-review-contreras-layered-sdn
IETF conflict review for draft-contreras-layered-sdn
ISE Informational
draft-contreras-layered-sdn
Cooperating Layered Architecture for Software Defined Networking (CLAS)
Token
Ignas Bagdonas

Conflict review
conflict-review-irtf-nfvrg-gaps-network-virtualization
IETF conflict review for draft-irtf-nfvrg-gaps-network-virtualization
IRTF Informational
draft-irtf-nfvrg-gaps-network-virtualization
Network Virtualization Research Challenges
Token
Deborah Brungard

Conflict review
conflict-review-irtf-cfrg-gcmsiv
IETF conflict review for draft-irtf-cfrg-gcmsiv
IRTF Informational
draft-irtf-cfrg-gcmsiv
AES-GCM-SIV: Nonce Misuse-Resistant Authenticated Encryption
Token
Eric Rescorla

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)

5. IAB news we can use

6. Management issues

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