Narrative Minutes interim-2018-iesg-25 2018-12-20 15:00
narrative-minutes-interim-2018-iesg-25-201812201500-00
Meeting Narrative Minutes | Internet Engineering Steering Group (iesg) IETF | |
---|---|---|
Date and time | 2018-12-20 15:00 | |
Title | Narrative Minutes interim-2018-iesg-25 2018-12-20 15:00 | |
State | (None) | |
Other versions | plain text | |
Last updated | 2024-02-23 |
narrative-minutes-interim-2018-iesg-25-201812201500-00
INTERNET ENGINEERING STEERING GROUP (IESG) Narrative Minutes of the 2018-12-20 IESG Teleconference These are not an official record of the meeting. Narrative Scribe: Amy Vezza, IETF Secretariat Corrections: NONE ATTENDEES --------------------------------- Ignas Bagdonas (Equinix) / Operations and Management Area Ben Campbell (Oracle) / Applications and Real-Time Area Michelle Cotton (ICANN) / IANA Liaison Spencer Dawkins (Wonder Hamster Internetworking) / Transport Area Sandy Ginoza (AMS) / RFC Editor Liaison Ted Hardie (Google) / IAB Chair Benjamin Kaduk (Akamai Technologies) / Security Area Suresh Krishnan (Kaloom) / Internet Area Warren Kumari (Google) / Operations and Management Area Terry Manderson (ICANN) / Internet Area Alexey Melnikov / Applications and Real-Time Area Cindy Morgan (AMS) / IETF Secretariat Alexa Morris (AMS) / IETF Secretariat Eric Rescorla (Mozilla) / Security Area Alvaro Retana (Huawei) / Routing Area Adam Roach (Mozilla) / Applications and Real-Time Area Jeff Tantsura (Apstra) / IAB Liaison Martin Vigoureux (Nokia) / Routing Area Amy Vezza (AMS) / IETF Secretariat REGRETS --------------------------------- Deborah Brungard (AT&T) / Routing Area Alissa Cooper (Cisco) / IETF Chair, General Area Heather Flanagan / RFC Series Editor Liz Flynn (AMS) / IETF Secretariat, Narrative Scribe Mirja Kuehlewind (ETH Zurich) / Transport Area Portia Wenze-Danley (ISOC) / Interim LLC Executive Director OBSERVERS --------------------------------- Greg Wood 1.2 Bash the agenda Amy: Does anyone want to add anything new to today's agenda? Hearing nothing new. Any other changes? We did have a Conflict Review moved to January 10 this morning, so I will tell you when we come to it. 1.3 Approval of the minutes of past telechats Amy: Anyone have an objection to the minutes of the December 6 telechat being approved? Hearing no objection; we will get those posted. I did see the revised narrative minutes from December 6 sent before Liz left; does anyone have an objection to approving those? Hearing no objection so we will get those posted. 1.4 List of remaining action items from last telechat 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) EKR: Still in progress. 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) Amy: We are still working on this, right? Alvaro: Amy and I and Alexa have made some progress. I have an update to send, but I was going to wait until after the holidays to follow up, and same status for the next one. 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) [See above] 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. Amy: Deborah sent the approved text to the chairs list, so this is done. 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) Amy: This is a follow up email to Deborah's task, and I didn't see this yet, but this is likely to happen after the holidays when everyone is back. 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) Amy: Saw discussion. Have you followed up with the tools team? Spencer: I sent a request this morning. Amy: We will mark this as done. o Alvaro Retana to send email to the IESG with proposed re-labeling of scheduling conflicts. - Added 2018-12-06 (1 telechat ago) Alvaro: Still in progress. o Alissa Cooper to follow up with Michelle Cotton and Barry Leiba to update RFC 8126 to detail what information should be included in the IANA Registry. - Added 2018-12-13 (0 telechats ago) o Alexey Melnikov to find designated experts for RFC 5435 [IANA #1132764]. - Added 2018-12-18 (0 telechats ago) Amy: This is a MI item and was to assign to Alexey, this is to make sure Alexey is aware of this task. Alexey: Yes. 2. Protocol actions 2.1 WG submissions 2.1.1 New items (1 of 6) draft-ietf-ntp-bcp-10 (Network Time Protocol Best Current Practices) Intended status: Best Current Practice Token: Suresh Krishnan Amy: There are a number of discusses, do we need to discuss? Suresh: Don't think so. I talked to the shepherd yesterday and the author won't be able to update for another week at least. So keep on it over email. Thanks for the security stuff. Amy: Revised ID? Suresh: For sure, thank you. 2. Protocol actions 2.1 WG submissions 2.1.1 New items (2 of 6) draft-ietf-idr-te-pm-bgp-17 (BGP-LS Advertisement of IGP Traffic Engineering Performance Metric Extensions) Intended status: Proposed Standard Token: Alvaro Retana Amy: There is a discuss. Alvaro: I don't know if it needs discussion. Benjamin? Benjamin: I saw that Les replied and it's possible I was just confused. I expect that I can go and look at the mail and clear, so I don't think there is anything to talk about. Alvaro: In general, we're just transporting what has been generated by the BGPs. Benjamin: Yeah, I will look and probably clear. Alvaro: Go take a look and let me know. Amy: Sounds like AD Followup? Alvaro: Yes, thank you. 2. Protocol actions 2.1 WG submissions 2.1.1 New items (3 of 6) draft-ietf-alto-xdom-disc-04 (Application Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery) Intended status: Proposed Standard Token: Mirja Kuehlewind Amy: Discusses but Mirja isn't here. Suresh: Think it will require a revised ID. The authors replied to me with an elaborate set of pseudocode, so I'm trying to figure out if that will work, but I think revised ID. Amy: Okay. Sounds like the discussion is ongoing, and we'll let Mirja follow up. Revised ID. Thank you. 2. Protocol actions 2.1 WG submissions 2.1.1 New items (4 of 6) draft-ietf-mpls-rsvp-shared-labels-07 (Signaling RSVP-TE tunnels on a shared MPLS forwarding plane) Intended status: Proposed Standard Token: Deborah Brungard Amy: Deborah isn't here, currently have a discuss for the document. Do you think this will require a revised ID? Alvaro: Yes, I'm sure it will. Amy: Revised ID needed, and we'll let Deborah followup. 2. Protocol actions 2.1 WG submissions 2.1.1 New items (5 of 6) draft-ietf-lsr-isis-rfc7810bis-04 (IS-IS Traffic Engineering (TE) Metric Extensions) Intended status: Proposed Standard Token: Alvaro Retana Amy: No discusses, approved. Alvaro: There are a couple of things I want the authors to look at, so revised ID needed, please. Amy: Certainly. Approved announcement to be sent revised ID needed. Let us know when we can send. 2. Protocol actions 2.1 WG submissions 2.1.1 New items (6 of 6) draft-ietf-httpbis-cdn-loop-01 (CDN Loop Prevention) Intended status: Proposed Standard Token: Alexey Melnikov Amy: A discuss. Do we need to discuss? Alexey: No I don't think so. Still waiting for authors to reply. Amy: Revised ID? Alexey: Yes, I think so. 2. Protocol actions 2.1 WG submissions 2.1.2 Returning items NONE 2. Protocol actions 2.2 Individual submissions 2.2.1 New items NONE 2. Protocol actions 2.2 Individual submissions 2.2.2 Returning items NONE 2. Protocol actions 2.3 Status changes 2.3.1 New items NONE 2. Protocol actions 2.3 Status changes 2.3.2 Returning items NONE 3. Document actions 3.1 WG submissions 3.1.1 New items NONE 3. Document actions 3.1 WG submissions 3.1.2 Returning items NONE 3. Document actions 3.2 Individual submissions via AD 3.2.1 New items (1 of 2) draft-wilde-service-link-rel-08 (Link Relation Types for Web Services) Intended status: Informational Token: Alexey Melnikov Amy: I have a discuss, do we need to discuss? Alexey: No. I am waiting for authors to reply. Benjamin: If we move to experimental, most of my concerns evaporate. Alexey: It's already informational, so what's the concern? Benjamin: I think Experimental to me has a connotation of more changes expected in the future. where Informational says here is a thing you can use or not use. Alexey: I think it's about implementations. I can check with the authors to see if they have a strong opinion. Benjamin: Yes, we should wait for the authors. No one else is chiming in so I may be in the rough. Amy: so waiting for authors, possibly revised ID needed? Alexey: Yes. 3. Document actions 3.2 Individual submissions via AD 3.2.1 New items (2 of 2) draft-wilde-sunset-header-08 (The Sunset HTTP Header) Intended status: Informational Token: Alexey Melnikov Amy: No discusses in the tracker. Approved? Alexey: Some good comments in the tracker so I'd like this to be point raised. Also Mirja's question about informational vs experimental. I will reply to her. Amy: Approved, point raised. 3. Document actions 3.2 Individual submissions via AD 3.2.2 Returning items NONE 3. Document actions 3.3 Status changes 3.3.1 New items NONE 3. Document actions 3.3 Status changes 3.3.2 Returning items NONE 3. Document actions 3.4 IRTF and Independent Submission stream documents 3.4.1 New items (1 of 4) conflict-review-browne-sfc-nsh-kpi-stamp-00 (IETF conflict review for draft-browne-sfc-nsh-kpi-stamp) draft-browne-sfc-nsh-kpi-stamp-06 Amy: No discusses in the tracker, so it looks like conflict review is approved and can be sent back to the ISE unless there is an objection. Martin: Thank you. Amy: We will get this sent shortly, not on Monday. Possibly tomorrow. 3. Document actions 3.4 IRTF and Independent Submission stream documents 3.4.1 New items (2 of 4) conflict-review-contreras-layered-sdn-00 (IETF conflict review for draft-contreras-layered-sdn) draft-contreras-layered-sdn-03 (Cooperating Layered Architecture for Software Defined Networking (CLAS)) Intended status: Informational Token: Ignas Bagdonas Amy: No discusses, so it looks like conflict review is approved. Hearing no objection, we will also send that message back to the ISE soon, probably tomorrow, before the holiday. 3. Document actions 3.4 IRTF and Independent Submission stream documents 3.4.1 New items (3 of 4) conflict-review-irtf-nfvrg-gaps-network-virtualization-00 (IETF conflict review for draft-irtf-nfvrg-gaps-network-virtualization) draft-irtf-nfvrg-gaps-network-virtualization-10 (Network Virtualization Research Challenges) Intended status: Informational Token: Deborah Brungard Amy: This is an IRTF document. It looks like there are no discusses so it looks like this is approved to go back to the IRSG unless there is an objection. Hearing none, we will get that sent shortly as well. 3. Document actions 3.4 IRTF and Independent Submission stream documents 3.4.1 New items (4 of 4) conflict-review-irtf-cfrg-gcmsiv-00 (IETF conflict review for draft-irtf-cfrg-gcmsiv) draft-irtf-cfrg-gcmsiv-09 (AES-GCM-SIV: Nonce Misuse-Resistant Authenticated Encryption) Intended status: Informational Token: Eric Rescorla Amy: This is the document moved to January 10. This was on the agenda to assign a reviewer, and EKR has moved this forward to January for the review. 3. Document actions 3.4 IRTF and Independent Submission stream documents 3.4.2 Returning items NONE 4. Working Group actions 4.1 WG creation 4.1.1 Proposed for IETF review NONE 4. Working Group actions 4.1 WG creation 4.1.2 Proposed for approval NONE 4. Working Group actions 4.2 WG rechartering 4.2.1 Under evaluation for IETF review NONE 4. Working Group actions 4.2 WG rechartering 4.2.2 Proposed for approval NONE 5. IAB News We Can Use Amy: Deborah is absent, Jeff is not on voice, so Ted, any IAB news to share? Ted: We have received the NomCom's request for confirmation for the IESG slate, but because it's hitting us over the holidays, our plan is to gather any questions by January 2nd and make our first run at discussing on January 9th. So please be aware it won't be until January. Amy: Thank you Ted. 6. Management issues 6.1 [IANA #1132764] Designated experts for RFC 5435 (IANA) Amy: This is the designated expert task list item that was assigned to Alexey at the top of the call and he is aware of it, so we can move on. 7. Any Other Business (WG News, New Proposals, etc.) Amy: Any WG news, new proposals, anything? No. Amy: A personal note - the Secretariat will be on winter holidays starting on Saturday, back on January 2nd. I'll be checking email sporadically, so if anything comes up like a Last Call, please be aware it might be delayed. Hopefully no one will be doing IETF work, please have a holiday. And have a happy and safe new year, and we will talk to you all on January 10th. There will not be an informal on January 3rd.