IESG agenda: 2016-02-18

Documents on future agendas DISCUSS positions

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: February 4, 2016

  o Alia Atlas to draft an FAQ on interactions in the IETF.
    - Added 2015-12-17 (4 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 (4 telechats ago)
  o Jari Arkko and Barry Leiba to produce the next version of the Note 
    Well and send it to the IESG and IAOC for review.
    - Added 2016-01-21 (2 telechats ago)
  o Benoit Claise to update the IESG statement on interim meetings to 
    include a point about archiving meeting announcements.
    - Added 2016-01-21 (2 telechats ago)
  o Barry Leiba to find designated experts for RFC-ietf-oauth-proof-of-
    possession [IANA #888133].
    - Added 2016-02-04 (1 telechat ago)
  o Barry Leiba to find an additional designated expert for RFC 7762 
    [IANA #891025].
    - Added 2016-02-04 (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-eppext-tmch-smd
Proposed Standard
Mark and Signed Mark Objects Mapping
Token
Barry Leiba (ART area)
IANA review
IANA OK - Actions Needed
Consensus
Yes

IETF stream
draft-ietf-dhc-anonymity-profile
Proposed Standard
Anonymity profile for DHCP clients
Token
Brian Haberman (INT area)
IANA review
IANA OK - No Actions Needed
Consensus
Unknown
Last call expires
2016-02-15
IPR
InterDigital Patent Holdings, Inc.'s Statement about IPR related to draft-ietf-dhc-anonymity-profile

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-lisp-eid-block
Informational
LISP EID Block
Token
Brian Haberman (RTG area)
IANA review
IANA OK - Actions Needed
Consensus
Yes

IETF stream
draft-ietf-lisp-eid-block-mgmnt
Informational
LISP EID Block Management Guidelines
Token
Brian Haberman (RTG area)
IANA review
IANA OK - Actions Needed
Consensus
Yes

IETF stream
draft-ietf-i2rs-problem-statement
Informational
Interface to the Routing System Problem Statement
Token
Deborah Brungard (RTG area)
IANA review
IANA OK - No Actions Needed
Consensus
Yes

IETF stream
draft-ietf-dnsop-edns-chain-query
Experimental
Chain Query requests in DNS
Token
Joel Jaeggli (OPS area)
IANA review
IANA OK - Actions Needed
Consensus
Yes

IETF stream
draft-ietf-dhc-dhcpv6-privacy
Informational
Privacy considerations for DHCPv6
Token
Brian Haberman (INT area)
IANA review
IANA OK - No Actions Needed
Consensus
Yes

IETF stream
draft-ietf-dhc-dhcp-privacy
Informational
Privacy considerations for DHCPv4
Token
Brian Haberman (INT area)
IANA review
IANA OK - No Actions Needed
Consensus
Yes

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-ietf-v6ops-mobile-device-profile
IETF conflict review for draft-ietf-v6ops-mobile-device-profile
ISE Informational
draft-ietf-v6ops-mobile-device-profile
An Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices
Token
Brian Haberman

Conflict review
conflict-review-warden-appsawg-vnc-scheme
IETF conflict review for draft-warden-appsawg-vnc-scheme
ISE Informational
draft-warden-appsawg-vnc-scheme
The "vnc" URI Scheme
Token
Barry Leiba

3.4.2 Returning items

(None)

4. Working Group actions

4.1 WG creation

4.1.1 Proposed for IETF review

WG name
Registration Protocols Extensions (regext)
Charter
charter-ietf-regext-(00-00)
Area
ART (Barry Leiba)

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 #888133] designated experts for RFC-ietf-oauth-proof-of-possession (Barry Leiba)

6.2 [IANA #891025] Designated expert for RFC 7762 (Barry Leiba)

7. Working Group news