Softwire IETF 78. 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.

Slides:



Advertisements
Similar presentations
IETF Calsify.
Advertisements

MPTCP – Multipath TCP WG Meeting Honolulu, IETF-91, 14th Nov 2014 Philip Eardley Yoshifumi Nishida 1.
Softwire IETF 87 July Preparation Blue sheet Note taker? Jabber room? …
L2VPN WG “NVO3” Meeting IETF 82 Taipei, Taiwan. Agenda Administrivia Framing Today’s Discussions (5 minutes) Cloud Networking: Framework and VPN Applicability.
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.
PPSP Working Group IETF-89 London, UK 16:10-18:40, Tuesday, Webex: participation.html.
CCAMP Working Group Online Agenda and Slides at: Tools start page:
IETF 90: NetExt WG Meeting. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet- Draft.
MPTCP – Multipath TCP WG Meeting Toronto, IETF-90, 21 st July 2014 Philip Eardley Yoshifumi Nishida 1.
Multiple Interfaces (MIF) WG IETF 78, Maastricht, Netherlands Margaret Wasserman Hui Deng
CLUE WG IETF-89 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
L3VPN WG IETF 78 09/11/ :00-15:00 Chairs: Marshall Eubanks Danny McPherson Ben Niven-Jenkins.
DIME WG IETF 82 Dime WG Agenda & Status THURSDAY, November 17, 2011 Jouni Korhonen & Lionel Morand.
71th IETF, Philadelphia, March 2008 ROLL Working Group Meeting IETF-71, March 2008, Philadelphia Online Agenda and Slides at:
SIPCLF Working Group Spencer Dawkins Theo Zourzouvillys IETF 76 – November 2009 Hiroshima, Japan.
IETF #82 DRINKS WG Meeting Taipei, Taiwan Fri, Nov 18 th
Softwire IETF 84. Preparation Blue sheet Note taker? Jabber room? …
EAP Method Update (EMU) IETF-79 Chairs Joe Salowey Alan DeKok.
1 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.
November 2010IETF TRILL WG1 TRILL Working Group TRansparent Interconnection of Lots of Links Mailing list: Tools site:
PAWS Protocol to Access White Space DB IETF 81 Gabor Bajko, Brian Rosen.
GROW IETF 78 Maastricht, Netherlands. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
ECRIT Virtual Interim Meeting 3rd June 2009, 1PM EDT (New York) Marc Linsner Hannes Tschofenig.
IETF 86 PIM wg meeting. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC.
IETF 79 - Beijing, China1 Martini Working Group IETF 79 Beijing Chairs: Bernard Spencer
BEHAVE Working Group IETF 81 – Quebec City July 2011 Chairs: Dave Thaler, Dan Wing, 1.
ROLL Working Group Meeting IETF-81, Quebec City July 2011 Online Agenda and Slides at: bin/wg/wg_proceedings.cgi Co-chairs:
Extensible Messaging and Presence Protocol (XMPP) WG Interim Meeting, Monday, January 7,
L3VPN WG IETF 78 30/07/ :00-11:30 Chairs: Marshall Eubanks Danny McPherson Ben Niven-Jenkins.
Softwires IETF 67 Alain Durand, David Ward. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF.
Tictoc working group Thursday, 28 July – 1720 EDT (1920 – 2120 UTC) Karen O’Donoghue and Yaakov Stein, co-chairs.
SIPREC WG, IETF# , GMT+2 John Elwell (WG co-chair) Brian Rosen (WG co-chair)
CCAMP Working Group Online Agenda and Slides at: Data tracker:
Web Authorization Protocol (oauth) IETF 90, Toronto Chairs: Hannes Tschofenig, Derek Atkins Responsible AD: Kathleen Moriarty Mailing List:
Web Authorization Protocol (oauth) Hannes Tschofenig.
Operations and Management Open Area Meetings IRTF-68 Prague, March 2007.
IETF DRINKS Interim Meeting (#82.5) Virtual Interim Meeting Wed, Feb 1 st p-6p UTC/9a-1p Eastern.
BFD IETF 83. 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.
IRTF SAM RG IETF 83 Chairs: John Buford, Avaya Labs Research Thomas Schmidt, HAW Hamburg.
IETF 82 Softwire Meeting Chairs: Alain Durand Ole Troan (acting as)
December 2007IETF TRILL WG1 TRILL Working Group TRansparent Interconnection of Lots of Links Mailing list: Website:
Mary Barnes (WG co-chair) Cullen Jennings (WG co-chair) DISPATCH WG IETF 90.
OAuth WG Blaine Cook, Hannes Tschofenig. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
Authentication and Authorization for Constrained Environment (ACE) WG Chairs: Kepeng Li, Hannes
IETF 89, LONDON, UK LISP Working Group. 2 Agenda and slides:  lisp.html Audio Stream 
MPTCP – MULTIPATH TCP WG meeting #1 Nov 9 th, 2009 Hiroshima, ietf-76.
MPTCP – MULTIPATH TCP WG meeting #5 Nov 8 th & 10 th 2010 Beijing, ietf-79 Yoshifumi Nishida Philip Eardley.
IETF – NVO3 WG Virtual Interim Meeting Chairs: Secretary: Sam Aldrin Benson Schliesser Matthew Bocci.
DMM WG IETF 84 DMM WG Agenda & Status Tuesday, July 31 st, 2012 Jouni Korhonen, Julien Laganier.
Transport Layer Security (TLS) IETF-84 Chairs: Eric Rescorla Joe Salowey.
Interface to the Routing System (IRS) BOF IETF 85, Atlanta November 2012.
IETF #81 - NETCONF WG session 1 NETCONF WG IETF 81, Quebec City, Canada MONDAY, July 25, Bert Wijnen Mehmet Ersue.
Transport Layer Security (TLS) IETF 73 Thursday, November Chairs: Eric Rescorla Joe Salowey.
ISIS IETF 71 Chris Hopps, David Ward. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
Transport Layer Security (TLS) IETF-78 Chairs Joe Salowey Eric Rescorla
ROLL Working Group Meeting IETF-82, Tapei, November 2011 Online Agenda and Slides at: bin/wg/wg_proceedings.cgi Co-chairs:
Agenda Behcet Sarikaya Dirk von Hugo November 2012 FMC BOF IETF
IETF #82 - NETCONF WG session 1 NETCONF WG IETF 82, Taipei, Taiwan TUESDAY, November 15, Afternoon Session III Bert Wijnen Mehmet Ersue.
Opsawg chairs Scott Bradner Chris Liljenstolpe. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an.
IETF #85 - NETCONF WG session 1 NETCONF WG IETF 85, Atlanta, USA WEDNESDAY, November 7, Bert Wijnen Mehmet Ersue.
NETWORK-BASED MOBILITY EXTENSIONS WG (NETEXT) July 28 th, 2011 IETF81 1.
Network Virtualization Overlays (NVO3) NVO3 Meeting, IETF 90, Toronto Benson Schliesser Matthew Bocci
Agenda Stig Venaas Behcet Sarikaya November 2011 Multimob WG IETF
SALUD WG IETF 78 Maastricht Friday, July 30, London Chair: Dale R. Worley.
Source Packet Routing in Networking WG (spring) IETF 89 – London Chairs: John Scudder Alvaro Retana
STIR Secure Telephone Identity Revisited
TRILL Working Group TRansparent Interconnection of Lots of Links
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.
CAPWAP Working Group IETF 73 Minneapolis 18 Nov 2008, 17:10-18:10
Agenda Wednesday, March 30, :00 – 11:30 AM
Presentation transcript:

Softwire IETF 78

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 sessionThe IESG, or any member thereof on behalf of the IESGAny IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspicesAny IETF working group or portion thereof The IAB or any member thereof on behalf of the IABThe RFC Editor or the Internet-Drafts functionAll IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). Statements made outsideRFC 5378 and RFC 3979 (updated by RFC 4879). 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 5378 and RFC 3979 for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

Agenda Chairs intro Document status Charter discussion Gateway Initiated Dual-Stack Lite Deployment (Frank Brockners) DHCPv6 Option for Dual-Stack Lite (Tomasz Mrugalski) RADIUS Extensions for Dual-Stack Lite (Roberta Maglione) RADIUS Attribute for 6rd (Sheng Jiang) Softwire Mesh Management Information Base (MIB) (Peng Wu) Deployment Considerations for Dual-Stack Lite (Yiu Lee) Public IPv4 over Access IPv6 Network (Peng Wu) IPv4-IPv6 Multicast: Problem Statement and Use Cases (Mohamed Boucadair) Softwire Mesh Multicast (Mingwei Xu) Multicast Support for Dual Stack Lite and 6RD (Behcet Sarikaya) Multicast Extensions to DS-Lite (Jacni Qin) A Generic Approach to Multicast Encapsulation In Support of IPv6 Transition (Tina Tsou)

Document Status DS-Lite DHCP option: – IESG approved, IANA code point allocated DS-Lite: – in IESG, IETF wide last call DS-Lite radius extension: – WG last call completed

IETF78: What is next for the wg? Most of milestones achieved: DS-Lite & 6rd Need to re-charter. Items considered with ADs are: – Operational considerations: 6rd, DS-Lite – CPE bootstrap (IPv4, IPv6, Dual Stack, 6rd, DS-Lite) – DS-Lite extensions (eg GI-DS-Lite) – ??? Multicast: Mesh, 6rd, DS-lite – ??? MIB Multicast & MIBs have been in the charter for a long time, but little progress. Is there real energy to work on those or should they be dropped?

IETF80: New charter proposal The Softwires Working Group is specifying the standardization of discovery, control and encapsulation methods for connecting IPv4 networks across IPv6 networks and IPv6 networks across IPv4 networks in a way that will encourage multiple, inter-operable implementations. For various reasons, native IPv4 and/or IPv6 transport may not be available in all cases, and there is a need to tunnel IPv4 in IPv6 or IPv6 in IPv4 to cross a part of the network which is not IPv4 or IPv6 capable. The Softwire Problem Statement, RFC 4925, identifies two distinct topological scenarios that the WG will provide solutions for: "Hubs and Spokes" and "Mesh." In the former case, hosts or "stub" networks are attached via individual, point-to-point, IPv4 over IPv6 or IPv6 over IPv4 softwires to a centralized Softwire Concentrator. In the latter case (Mesh), network islands of one Address Family (IPv4 or IPv6) are connected over a network of another Address Family via point to multi-point softwires among Address family Border Routers (AFBRs). The WG will reuse existing technologies as much as possible and only when necessary, create additional protocol building blocks. For generality, all base Softwires encapsulation mechanisms should support all combinations of IP versions over one other (IPv4 over IPv6, IPv6 over IPv4, IPv4 over IPv4, IPv6 over IPv6). IPv4 to IPv6 translation mechanisms (NAT-PT), new addressing schemes, and block address assignments are out of scope. DHCP options developed in this working group will be reviewed jointly with the DHC WG. RADIUS attributes developed in this working group will be reviewed jointly with the RADEXT WG. The MIB Doctors directorate will be asked to review any MIB modules developed in the SOFTWIRE working group. BGP and other routing and signaling protocols developed in this group will be reviewed jointly with the proper working groups and other workings that may take interest (e.g. IDR, L3VPN, PIM, LDP, SAAG, etc).

Work area Developments for Mesh softwires topology; the Mesh topology work will be reviewed in the l3vpn and idr WGs – Multicast – MIB module Developments for 6rd: – Multicast – Operational specification – RADIUS option for 6rd server – MIB module Developments for Dual-Stack Lite (DS-Lite): – Multicast – Operational specification – RADIUS option for AFTR – Proxy extensions: GI-DS-Lite; DS-Lite with no NAT or NAT on the B4 element – MIB module Finalize discovery and configuration mechanisms for a gateway to use DS-Lite or 6rd; these discovery and configuration mechanisms must take into a account other operating environments such as dual-stack and tunneling mechanisms not defined by the softwire WG. Development of new mechanisms will involve the dhc and/or v6ops WGs as appropriate.

Goals & Milestomes Apr 2011 Submit DS-lite RADIUS option for Proposed Standard Apr 2011 Adopt DS-lite operational document as WG document Jul 2011 Submit 6rd RADIUS option for Proposed Standard Jul 2011 Submit GI DS-lite for Proposed Standard Jul 2011 Adopt B4NAT as WG document Aug 2011 Adopt 6rd operational document as WG document Aug 2011 Adopt Multicast extensions document as WG document Aug 2011 Submit DS-lite operational document for Informational Sep 2011 Submit B4NAT for Informational Nov 2011 Submit Multicast extensions document for Informational Nov 2011 Submit 6rd operational document for Informational Nov 2011 Adopt 6rd MIB module as WG document Nov 2011 Adopt DS-lite MIB module as WG document Nov 2011 Adopt Mesh topology MIB module as WG document Nov 2012 Submit 6rd MIB module for Proposed Standard Nov 2012 Submit DS-lite MIB module for Proposed Standard Nov 2012 Submit Mesh topology MIB module for Proposed Standard

Summary of charter discussions on the mailing list “additional” topics discussion: – inter-AS softwire Mesh – 6a44: 6over4 with legacy CPE NAT – Stateless 4over6 – VET and SEAL – sa46t – 4rd – IPv6 over L2TPv3 Wording: – NAT-PT -> NAT64 – No need to “support all combinations of IP versions over one other.” – “DS-Lite with no NAT or NAT on the B4 element”