IESG agenda: 2020-10-22

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

            (Error reading /a/www/www6/iesg/internal/task.txt)
          

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-6man-rfc4941bis
Proposed Standard
Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6
Token
Erik Kline (INT 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-lwig-tcp-constrained-node-networks
Informational
TCP Usage Guidance in the Internet of Things (IoT)
Token
Erik Kline (INT area)
IANA review
IANA OK - No Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-cose-x509
Informational
CBOR Object Signing and Encryption (COSE): Header parameters for carrying and referencing X.509 certificates
Token
Barry Leiba (SEC area)
IANA review
IANA OK - Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-opsawg-model-automation-framework
Informational
A Framework for Automating Service and Network Management with YANG
Token
Robert Wilton (OPS area)
IANA review
IANA OK - No Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-v6ops-slaac-renum
Informational
Reaction of Stateless Address Autoconfiguration (SLAAC) to Flash- Renumbering Events
Token
Warren Kumari (OPS area)
IANA review
IANA OK - No Actions Needed
Consensus
Yes
Reviews

IETF stream
draft-ietf-v6ops-cpe-slaac-renum
Informational
Improving the Reaction of Customer Edge Routers to Renumbering Events
Token
Warren Kumari (OPS area)
IANA review
IANA OK - No Actions Needed
Consensus
Yes
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:

  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-irtf-cfrg-argon2
IETF conflict review for draft-irtf-cfrg-argon2
IRTF Informational
draft-irtf-cfrg-argon2
The memory-hard Argon2 password hash and proof-of-work function
Token
Roman Danyliw

Conflict review
conflict-review-irtf-nwcrg-network-coding-satellites
IETF conflict review for draft-irtf-nwcrg-network-coding-satellites
IRTF Informational
draft-irtf-nwcrg-network-coding-satellites
Network coding for satellite systems
Token
Martin Duke

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

WG name
Building Blocks for HTTP APIs (httpapi)
Charter
charter-ietf-httpapi-(00-02)
Area
ART (Barry Leiba)

WG name
JSON Path (jsonpath)
Charter
charter-ietf-jsonpath-(00-01)
Area
ART (Murray Kucherawy)

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 #1180561] Designated expert for RFC 8411, SMI Security for Cryptographic Algorithms (IANA)

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