Minutes interim-2019-iesg-11 2019-05-30 14:00
minutes-interim-2019-iesg-11-201905301400-00

INTERNET ENGINEERING STEERING GROUP (IESG)
Minutes of the May 30, 2019 IESG Teleconference

Reported by: Cindy Morgan, IETF Secretariat

ATTENDEES 
--------------------------------- 
Deborah Brungard (AT&T) / Routing Area
Alissa Cooper (Cisco) / IETF Chair, General Area
Michelle Cotton (ICANN) / IANA Liaison 
Roman Danyliw (CERT/SEI) / Security Area
Liz Flynn (AMS) / IETF Secretariat, Narrative Scribe
Sandy Ginoza (AMS) / RFC Editor Liaison 
Wes Hardaker (USC/ISI) / IAB Liaison
Ted Hardie (Google) / IAB Chair
Benjamin Kaduk (Akamai Technologies) / Security Area
Suresh Krishnan (Kaloom) / Internet Area
Mirja Kuehlewind (Ericsson) / Transport Area
Warren Kumari (Google) / Operations and Management Area
Barry Leiba (Futurewei Technologies) / Applications and Real-Time Area
Cindy Morgan (AMS) / IETF Secretariat
Amy Vezza (AMS) / IETF Secretariat
Magnus Westerlund (Ericsson) / Transport Area

REGRETS 
---------------------------------
Ignas Bagdonas (Equinix) /  Operations and Management Area
Heather Flanagan / RFC Series Editor
Alexey Melnikov / Applications and Real-Time Area
Alvaro Retana (Futurewei Technologies) / Routing Area
Adam Roach (Mozilla) / Applications and Real-Time Area
Martin Vigoureux (Nokia) / Routing Area
Eric Vyncke (Cisco) / Internet Area
Portia Wenze-Danley (ISOC) / Interim LLC Executive Director

OBSERVERS
--------------------------------- 
Adrian Farrel
Greg Wood


MINUTES 
--------------------------------- 
1. Administrivia 
1.1 Approval of the Minutes

The minutes of the May 16, 2019 Teleconference were approved. The 
Secretariat will place the minutes in the public archives.

The narrative minutes of the May 16, 2019 Teleconference were 
approved. The Secretariat will place the minutes in the public archives.

1.2 Documents Approved since the May 16, 2019 IESG Teleconference
1.2.1 Protocol Actions
  o draft-ietf-spring-segment-routing-mpls-22  (Proposed Standard)
  o draft-ietf-netconf-yang-push-25  (Proposed Standard)
  o draft-ietf-netconf-netconf-event-notifications-22  (Proposed 
    Standard)
  o draft-ietf-mmusic-data-channel-sdpneg-28  (Proposed Standard)
  o draft-ietf-netconf-subscribed-notifications-26  (Proposed Standard)
  o draft-ietf-payload-flexible-fec-scheme-20  (Proposed Standard)
  o draft-ietf-sidrops-rtr-keying-06  (Proposed Standard)

1.2.2 Document Actions
  o draft-wilde-service-link-rel-10  (Informational)

1.3 Review of Action Items

DONE:
  o Suresh Krishnan to discuss naming experts for the registries created 
    by draft-irtf-icnrg-ccnxsemantics with Colin Perkins.
  o Barry Leiba to write up text on the IESG's expectations regarding 
    conflicts of interest and the disclosure of 
    funding sources.
  o Suresh Krishnan to update the text for material behind a paywall 
    to update the reference to section 7.1; update the document shepherd 
    writeup; and draft text for a possible IESG statement to circulate 
    with the WG Chairs. 
  o Alissa to report back on the discussion about the Meeting Room 
    Policy at LLC Board retreat.
  o Warren Kumari and Ted Hardie to write a document on Implementation 
    Target Sets (aka Living Documents).

IN PROGRESS:

  o Ignas Bagdonas to propose an additional question on YANG Model 
    format validation for each of the styles of document write-ups.
  o Roman Danyliw to talk to the tools team to reset the counters on 
    substate change for documents in AD Evaluation.
  o Roman Danyliw to draft text to be posted on ietf.org about reporting 
    protocol vulnerabilities via an email alias and possible procedures 
    on how to assign triage resources. 
  o Suresh Krishnan to write a document on replacing the "updates" with 
    new terminology (amends/amended by; extends/extended by; see also).
  o Roman Danyliw and Barry Leiba to draft a starting point for the 
    discussion on setting expectations with the WG Chairs in reference 
    to responses to inappropriate or unacceptable behaviors. 
  o Martin Vigoureux to work with the IESG to create a list of possible 
    IESG Tutorials and will prioritize them for scheduling on a series 
    of Informal Telechats. 
  o All IESG to coordinate with their co-ADs and send a list of specific 
    "hot topic" items that should be checked. The list to be provided 
    for document authors.
  o Eric Vyncke to write up draft text for the NomCom to help them 
    understand the rules for the NomCom.
  o Suresh Krishnan to write up a NomCom Chair BCP (work with past 
    chairs).
  o Eric Vyncke to draft text for a more coherent BoF Proposal for 
    MEDIA OPS and add to the BoF Wiki.
  o Roman Danyliw to shepherd the www.ietf.org analytics discussion 
    with the community.
  o Warren Kumari, Alvaro Retana, and Mirja Kuehlewind with Spencer 
    Dawkins to continue discussion of the next Deep Dive topic for 
    IETF 105.
  o Alexey Melnikov, Warren Kumari, and Suresh Krishnan to work with the 
    authors of the recall draft on next steps. 
  o Alexey Melnikov to find designated experts for RFC-ietf-core-object-
    security [IANA #1141664].
  o Alvaro Retana to finalize the proposal for relabeling the IETF 
    Meeting Agenda Conflicts, and discuss the proposal with the WG 
    Chairs.
  o Alissa Cooper and Alexa Morris to take the results of the doodle 
    poll for a second 2019 IESG retreat (possibly combined with the IAB) 
    and look at cost effective places.
  o Alexey Melnikov to find designated experts for RFC 8554 [IANA 
    #1142796].
  o Adam Roach to facilitate the discussion on WG Meeting Structure,
    related to alternate room layouts and the facilitation of 
    discussion.

NEW:
  o Ted to write up use cases and requirements for Implementation Target 
    Sets for a future IESG discussion (preliminary date for discussion: 
    June 20, 2019 Informal Telechat).

2. Protocol actions
2.1 WG submissions
2.1.1 New items
  o draft-ietf-pim-igmp-mld-yang-14  - IETF stream
    A YANG Data Model for Internet Group Management Protocol (IGMP) and
    Multicast Listener Discovery (MLD) (Proposed Standard) - 1 of 7
    Token: Alvaro Retana

The document was approved by the IESG pending a final check to be 
completed by Alvaro Retana. The Secretariat will send a working group
submission Protocol Action Announcement. 

  o draft-ietf-roll-useofrplinfo-29  - IETF stream
    Using RPL Option Type, Routing Header for Source Routes and
    IPv6-in-IPv6 encapsulation in the RPL Data Plane (Proposed Standard) 
    - 2 of 7
    Token: Alvaro Retana

The document was approved by the IESG pending a new revision. The 
Secretariat will send a working group submission Protocol Action 
Announcement once Alvaro Retana confirms that the announcement is ready 
to be sent.

  o draft-ietf-acme-caa-07  - IETF stream
    CAA Record Extensions for Account URI and ACME Method Binding
    (Proposed Standard) - 3 of 7
    Token: Roman Danyliw

The document remains under discussion by the IESG in order to resolve
points raised by Benjamin Kaduk, Warren Kumari, and Barry Leiba.*

  o draft-ietf-calext-eventpub-extensions-13  - IETF stream
    Event Publishing Extensions to iCalendar (Proposed Standard) - 4 of 
    7
    Token: Alexey Melnikov

The document remains under discussion by the IESG in order to resolve
points raised by Alissa Cooper, Roman Danyliw, Benjamin Kaduk, and 
Barry Leiba.*

  o draft-ietf-lamps-rfc6844bis-06  - IETF stream
    DNS Certification Authority Authorization (CAA) Resource Record
    (Proposed Standard) - 5 of 7
    Token: Roman Danyliw

The document was approved by the IESG pending a new revision. The 
Secretariat will send a working group submission Protocol Action 
Announcement once Roman Danyliw confirms that the announcement is ready 
to be sent.

  o draft-ietf-mmusic-rfc4566bis-35  - IETF stream
    SDP: Session Description Protocol (Proposed Standard) - 6 of 7
    Token: Adam Roach

The document remains under discussion by the IESG in order to resolve
points raised by Alissa Cooper, Roman Danyliw, and Barry Leiba.*

  o draft-ietf-tsvwg-tinymt32-03  - IETF stream
    TinyMT32 Pseudo Random Number Generator (PRNG) (Proposed Standard) - 
    7 of 7
    Token: Magnus Westerlund

The document remains under discussion by the IESG in order to resolve
points raised by Roman Danyliw and Adam Roach.*

2.1.2 Returning items    
  o draft-ietf-tsvwg-rlc-fec-scheme-14  - IETF stream
    Sliding Window Random Linear Code (RLC) Forward Erasure Correction
    (FEC) Schemes for FECFRAME (Proposed Standard) - 1 of 1
    Token: Magnus Westerlund

The document remains under discussion by the IESG in order to resolve
points raised by Roman Danyliw.*

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
3.1.1 New items
    
  o draft-ietf-lamps-hash-of-root-key-cert-extn-05  - IETF stream
    Hash Of Root Key Certificate Extension (Informational) - 1 of 2
    Token: Roman Danyliw

The document remains under discussion by the IESG in order to resolve
points raised by Benjamin Kaduk.*

  o draft-ietf-sipbrandy-osrtp-09  - IETF stream
    An Opportunistic Approach for Secure Real-time Transport Protocol
    (OSRTP) (Informational) - 2 of 2
    Token: Alexey Melnikov

The document was approved by the IESG pending a final check to be 
completed by Alexey Melnikov. The Secretariat will send a working group 
submission Document Action Announcement.

3.1.2 Returning items
  NONE

3.2 Individual submissions via AD
3.2.1 New items
  NONE

3.2.2 Returning items
  NONE

3.3 Status changes
3.3.1 New items
  NONE

3.3.2 Returning items
  NONE

3.4 IRTF and Independent Submission stream documents
3.4.1 New items
  o conflict-review-kanugovi-intarea-mams-framework-00
    IETF conflict review for draft-kanugovi-intarea-mams-framework
      draft-kanugovi-intarea-mams-framework-03
      Multiple Access Management Services (ISE: Informational) - 1 of 2
    Token: Suresh Krishnan

The IESG has no problem with the RFC Editor publishing this document.
The Secretariat will send a standard "no problem" message to the RFC
Independent Submissions Editor that includes a conflict review response 
prepared by Suresh Krishnan.

  o conflict-review-jenkins-cnsa-cmc-profile-00
    IETF conflict review for draft-jenkins-cnsa-cmc-profile
      draft-jenkins-cnsa-cmc-profile-05
      Commercial National Security Algorithm (CNSA) Suite Profile of
    Certificate Management over CMS (ISE: Informational) - 2 of 2
    Token: Benjamin Kaduk

The IESG has no problem with the RFC Editor publishing this document.
The Secretariat will send a standard "no problem" message to the RFC
Independent Submissions Editor that includes a conflict review response 
prepared by Benjamin Kaduk, pending a final check to be completed by 
Benjamin Kaduk.

3.4.2 Returning items
  o conflict-review-nottingham-safe-hint-01
    IETF conflict review for draft-nottingham-safe-hint
      draft-nottingham-safe-hint-09
      The "safe" HTTP Preference (ISE: Informational) - 1 of 1
    Token: Barry Leiba

The conflict review remains under discussion by the IESG in order to 
resolve points raised by Mirja Kuehlewind.*

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 #1143383] Management Item: Acceptance of media type 
    registration from standards organization National Center for 
    Geospatial Intelligence Standards (NCGIS) (IANA)

The management issue was discussed. The IESG asks IANA to process these 
media-type requests, but to not add this organization to the 'Standards-
related organizations that have registered Media Types in the Standards Tree.' 

6.2 Cross Area SEC Protocol Work (Roman Danyliw)

The management issue was discussed in an executive session.

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

8. Tools Team Report -- 26 May 2019

1. Datatracker Projects
  - The plan was recently updated.
    -- https://trac.tools.ietf.org/tools/ietfdb/browser/trunk/PLAN
    -- One thing to highlight is the increased the priority of the
       transition from Python 2 to Python 3.  This increased priority
       is because Python 2 is being officially deprecated, and it 
       will not receive maintenance starting January 2020.
  - A contract for Meeting Application Improvements was awarded to
    IOLA.  Work will begin shortly.
  - An RFP for IRSG balloting was released and then the period to bid
    was extended to 4 June 2019.  We expect work to begin in June 2019.

2. Community & Other Projects
  - The latest website deliverable from Torchbox is complete, including
    the cleanup of messy redirects between Wagtail and Apache.
  - Handling of 404 on the Wagtail website was improved, avoiding some
    problems that could occur with dynamic links.
  - The Tools Team and the Secretariat are working on a plan for the
    best way to handle static plaintext pages, such as appeals, appeal
    responses, and implementation reports.  Current thinking is to
    manage these outside Wagtail, but the discussion is still ongoing.

3. RFC Services Projects
  - Support for the v3 schema has been enabled for I-D submission, and
    now the IESG needs to make a policy decision about when I-Ds in the
    new format can be submitted to the IESG for publication on the IETF
    stream.
  - The RFC Production Center continues to test the new format tools.
  - The Tools Team has a Statement of Work for the security of the
    tools used by the RFC Production Center.  The new format tools will
    be reviewed once the tools related to the old format are put in
    mothballs.
  - A contract for rendering errata in a more useful was awarded to
    Soaring Hawk Consulting; work began in May 2019.

4. Server Infrastructure
  - The custom DMARC-handling software was deployed for all mail lists
    in June 2018, but there is a desire to move away from the custom
    software to ARC.  The ARC software cannot be configured to handle
    just a few of our mail lists.  Requirements were provided to the
    ARC developers, but so far, they have not offered a release date.
    Alexey continues to try to get a response from the ARC developers,
    but so far we are only getting silence.  This has not changed in
    many months; maybe we will be using our custom code forever.
  - The guides.ietf.org has been deployed in its own container.  In a
    few weeks we expect to move it to hardware controlled by the
    Secretariat.  This experiment is allowing the Tools Team to
    determine whether other services can be containerized and put
    "in the cloud".

5. YANG Catalog
  - Operation of the yangcatalog.org was to transferred to the IETF
    Secretariat.  A few significant things to highlight:
    -- The yangcatalog.org service is running on different hardware
       than ietf.org; it is on a server in Canada.  This placement is
       allowing the Tools Team to determine whether other services can
       be containerized and put "in the cloud".


-----------------------------------------------
* Please see the Datatracker (https://datatracker.ietf.org/doc/) 
for details on documents that are under discussion by the IESG.