110 likes | 120 Views
This is a summary of the Softwires Working Group interim meeting, which discusses solutions for hub and spoke and mesh scenarios. Conclusions and next steps are outlined, along with deliverables for future work.
E N D
Softwires IETF 65
Note Well • Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: • the IETF plenary session, • any IETF working group or portion thereof, • the IESG, or any member thereof on behalf of the IESG, • the IAB or any member thereof on behalf of the IAB, • any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, • the RFC Editor or the Internet-Drafts function • All IETF Contributions are subject to the rules of RFC 3978 and RFC 3979. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. • Please consult RFC 3978 for details.
Agenda • 05 mins: Admistrativa • 25 mins: Report from the Interim Meeting • 30 mins: Mesh • 30 mins: Hubs and Spokes • 10 mins: Fred Templin IP tunneling and MTU • 10 mins: General documents the working group needs to take on • 10 mins: Next Steps and Phase 2
Interim Meeting Summary.1 • NOTES: http://bgp.nu/~dward/softwires/2006-02SoftwiresInterimNotes.html • Reviewed some current deployments • KDDI, Freenet6 • Reviewed Security Analysis • Criteria for selection was evaluated based on MUSTs from Problem Statement • ATS6, TSP, 2@L2TPv2, L2TPv3 were proposed as solutions for Hub & Spoke • V4overV6 and tunnel saf were proposed as solutions for Mesh
Interim Meeting Conclusions.1 • Attendees reached consensus on solutions for both scenarios • L2TPv2 was selected as Phase 1 solution for H&S • L2TPv3 was selected as Phase 2 solution for H&S • Combined MPBGP solutions from Yong Cui and C. Metz was selected for Mesh solution • Attendees reached conclusion on next steps • Phase 1 Framework solution for H&S to be written immediately How to solve H&S scenarios w/ L2TPv2 • Phase 2 Framework solution for H&S to be presented as soon as Phase 1 is documented How to solve all H&S requirements w/ L2TPv3 and propose extensions • Create Framework doc for solutions to Mesh scenario How to solve all Mesh requirements w/ MPBGP and propose extensions Adopt Multicast solution by Shepherd, Wu, Li, Farinacci as WG doc • Adopt security analysis and radius extensions as WG docs
Interim Meeting Conclusions.2 • Meeting continued second day w/ break out sessions on two scenarios • Proposed third interim meeting in “September” • Discuss Framework for Phase 2 H&S • List extension set for Phase 2 • Finalize extension set for Mesh • Meeting in Hong Kong was very successful • Many thanks to hosts: CERNET and CHUK • Many thanks to Mark Townsley (INT AD) for being present and keeping us to present and future process • Rough consensus was achieved and notes posted to list
WG activities since the interim meeting • The chairs posted on March 3rd a message with the title: "Notes and Consensus from Interim Meeting in Hong Kong". A number of clarification questions were asked on the mailing list since. • Problem Statement draft at -01. Needs final, final edits in -02 (any second now) • Softwire ML statistics since the interim meeting: • 26 From: Jordi Palet Martinez • 15 From: Alain Durand • 12 From: Maria A. Dos Santos • 11 From: David Ward • 8 From: JF Tremblay • 7 From: Michael Fiumano • 5 From: Bill Storer • 3 From: Tim Chown • 2 From: Ole Troan • 1 From: HUI-HCHBJ DENG • 1 From: Eric Gray • 1 From: Laurent Toutain • 1 From: Tschofenig, Hannes • 1 From: Bruno STEVANT • 1 From: Marc Blanchet • 1 From: Pekka Savola • Much interesting discussion on TTM, support, deployment and technical criteria • No Open issues remain
Consensus • Given that: • There was discussion involving many wg participants • No open issues considered remaining • Solution providers will represent a common vision in next presentations as stated in interim meeting notes and conclusion • We declare rough working group consensus: • Hub & Spokes scenario: • L2TPv2 chosen as the immediate solution • L2TPv3 in phase 2 as a backward compatible upgrade • Mesh scenario: • Conjoined effort for extensions to MPBGP based on work presented by Chris Metz and Yong Cui
Presentations • Mesh • H&S • Fred • Next steps
Deliverables • General docs • Security analysis • Radius accounting • Mesh • Framework doc using MPBGP • Multicast draft extensions • tunnel-safi and any additional softwires attributes • To be reviewd by L2VPN, L3VPN, IDR, Security types • Hub and Spoke • Phase 1 Framework doc using L2TPv2 • Phase 2 Framework doc using L2TPv3Extensions
Next Deliveries • July 2006 • Security analysis • Radius accounting • Mesh Framework doc using MPBGP • Mesh Multicast draft extensions • Mesh tunnel-safi and any additional softwires attributes • Hub and Spoke Phase 1 Framework doc using L2TPv2 • Potential Interim WG meeting September 2006 • Focus on Hub and Spoke Phase 2 and Mesh extensions • November 2006 • Hub and Spoke Phase 2 Framework doc using L2TPv3 • Any new Mesh extensions • March 2007 • Hub and Spoke Phase 2 Extensions