Routing Area Open Meeting Agenda Atlanta November 2012 Meeting Room: Grand Ballroom D Time: November 8th (1pm-3pm) 1. Administrivia - See Slides 2. Working Group Reports BFD - BFD did not meet. - Minor recharter. BFD for aggregation of LAG (groups). Allows them to adopt a draft in this area. - MIB work needs to be complete. - P2MP work has lagged. - Security is problematic, not so much interest. - Need to update their milestones. CCAMP - Document status: – 2 RFCs published (1 this week) – 1 in RFC editor queue – 1 with IESG (waiting on update from authors) – 2 Sets of documents post WG LC • 1 with authors, 1 with chairs - Meeting status: – Met for 2 sessions, co-chair waylaid by Sandy – Trying to wrap up WSON work – 3 new areas of work discussed, still individual documents • Multi-layer adaptation • Overlays • Flexible grid (optical) ForCES - Met on Wednesday, we had about 45 people - it was a tightly scheduled meeting. - original charter schedule, one of the two outstanding documents has started the journey to publication. The other one to follow shortly. - Given we have seen renewed interest in the ForCES work thanks to SDN, since Vancouver we have allowed for folks to publish out-of-charter drafts. Since October we had 4 drafts that managed to beat the draft 0 deadline. Three others, in the same vein, have not yet been published. - We have 2 more drafts released with revised versions. - The meeting focus was to review whether we re-charter or proceed to shutdown. A lively discussion ensued - conclusion is we need to go back and enumerate the out-of-charter work items and poll who was willing to do the work and review such work. - Two outstanding documents, one is sitting with AD. - Mini-BOF covering new work. Conclusion is to prepare a list of work items. - Adrian encouraged anyone interested to follow list and help make decisions. IDR - Two documents in RFC editors queue. - Link state distribution proceeding and expanding. - Proposal for L3VPN authentication (CIDR, L3VPN and IDR). - IP FRR work proposed. Asked authors to do this in Routing area. IRS - The IRS effort is looking into allowing applications access to monitor and control some aspects of the operation of routers. One example is adding static routes to RIB and/or Label FIB. - There is a mailing list to discuss this, and are multiple drafts (10 or 11) - WG forming BOF was held. - There was consensus to go ahead with chartering a WG. - There was also rough consensus that we would like to reduce the number of deliverables in the draft proposed WG charter. - Details will be discussed on the irs-discuss list. ISIS - On agenda, ISIS multi instance, metric extensions for TE (DC), interface address. Check audio. - A new RFC and two close. KARP - WG Documents currently undergoing review - KARP Threats/Requirements (one DISCUSS to be cleared) - OSPF Analysis (on IESG telechat) - TCP-based RP Analysis (in IETF LC) - Crypto Key Tables (in WG LC) - Presentations this meeting - Operations Model for Router Keying (expected WG LC before IETF86) - IS-IS Analysis (WG adoption evaluation underway) - BFD Analysis (WG adoption evaluation underway) - TCP-AO Master Key Tuple Negotiation in IKEv2 (WG discussion) - Simplified Peer Authentication (WG discussion) L2VPN - Tuesday - Ali show - Covered everything not VPN - In E-VPN space a lot of work still exists. L3VPN - L3VPN WG is meeting tomorrow. Agenda is full, with non WG documents only. - WG just adopted a new document: draft-rosen-l3vpn-mvpn-mldp-nlri and also adopted draft-ietf-l3vpn-end-system since Vancouver. - We thus have 6 WG documents. - One them just went through WG LC: draft-ietf-l3vpn-virtual-hub - We also have a good number of individual documents and two of them will be polled for adoption after Atlanta. MPLS - The MPLS WG met yesterday and will meet again later this afternoon. - One new RFC since last time (I think that this makes 104 RFCs in total since September of 1999). - 27 current WG documents. - Of those WG documents, one is in the RFC editor’s queue, four have been submitted to AD for publication, another was just returned to the WG after being submitted for publication. - We have updated WG milestones. - We had a presentation on one WG draft and had or will have presentations on 20 other related drafts. NVO3 - Good progress made at an interim in Boston in September - Problem statement and framework adopted - Met on Thursday morning at this IETF - Topics on agenda included: o Problem statement and Framework, Expect a WG LC after this IETF, Data plane and control plane requirements: o Try to adopt imminently o VM mobility o TES->NVE signalling o Optimal routing o WG needs to decide where this work goes o Use cases - Chairs feel the architecture needs to be better scoped and will appoint a design team to work on this OSPF - No new RFCs since Vancouver - 2 Documents in IESG Review OSPF Hybrid Broadcast and P2MP Interface Type & Hiding Transit-only Networks in OSPF - 3 Documents Recently Completing WG Last Call (OSPF Stub Router Advertisement, Routing for IPv4-embedded IPv6 Packets, and OSPFv3 Instance ID Registry Update) - 2 Documents Requiring Revision, discussion, and WG last call - Security Extension for OSPFv2 when using Manual Key Management & Use of the OSPF-MANET Interface in Single-Hop Broadcast Networks. - 2 Documents Requiring Interest Discussion, implementation, or at least intention to implement OSPF Traffic Engineering (TE) Metric Extensions and OSPF Transport Instance Extensions - 1 New WG Documents with lots of HOMENET Interest - OSPFv3 Auto-Configuration - 3 Individual drafts requiring Discussion (OSPF Topology-Transparent Zone, Applicability of OSPF Topology-Transparent Zone, and OSPF Incremental Link State Database Synchronization). - 2 Individual drafts requiring presentation/discussion - Service Distribution using OSPF and Flow Specification Extensions to OSPF Protocol. PCE - Met Tuesday - H-PCE in editors queue - A few documents preparing for Last Call - Hot topic was stateful PCE extensions - Several emails on list require responses - Siding with current architecture boundary with regards to charter. Will need to check with Ads recharter. PIM - Published RFC 6754, one draft in RFC Editor’s queue - 3 current work items - Working on progressing RFC 4601 on the standards track. Just finished a survey to write an implementation report - 5 new drafts presented - 2 PIM extensions - 3 IGMP/MLD related - None of these adopted at this point ROLL - The ROLL WG met on Monday at 15:00 for two hours. - We have a WG LC open on draft-ietf-roll-mcast-trickle, and accumulated a handful of issues which were discussed. The most important question revolved around the question of when, why and how to encapsulate packets that are crossing the LLN. - We had a presentation on the industrial use of RPL, as outlined in draft-phinney-roll-rpl-industrial-applicability-01 there will shortly start a WG call for adoption of this document. - We heard two additional presentations on things that were believed to be problems in industrial networks. In addition, the problem of storing and non-storing nodes was revisited, but the WG felt that the solution missed the original pathology caused the WG to abandon mixed modes of operation. - We have two WG consensus calls open on adopting two documents (closing on Friday). There have been some challenges getting enough input on some of the applicability documents (some ID authors were lost); things are now in order. SIDR - Interim meeting in Amsterdam, productive work on protocols. - Two drafts in RFC editors queue. - Some of the time overlap with GROW. Looking to adjust agenda to allow people to present all aspects. - In accordance with RTG AD comment, lots of discussion not just presentations. OSPFv3 Based Home Networking Report - A comment from Acee regarding RFC5340. - A number of drafts are work in progress. - Comment from Russ, “not sure if I am terrified or little concern. I would like to read the draft. Is this for RTG discussion list?“ - Comment that this is applicable to a network diameter of 10. - Governments already legislating for power aware devices so it is worth looking at, as a concern is OSPF is active protocol. Acee pointed out that legacy OSPF work for demand circuits (ISDN) might be applicable. 3. Open Discussion / Any other business - “How do people feel about RTG Area meeting time?” - General feedback was Friday morning was good. - “ID Implementations” – Feedback was that Chairs need to monitor standards track drafts and “intent to implement” versus implementations, and if work should be instead be moved from standards track to experimental status or other.