Re: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations

Chris Bowers <cbowers@juniper.net> Fri, 08 May 2015 12:42 UTC

Return-Path: <cbowers@juniper.net>
X-Original-To: rtg-dt-encap-considerations@ietfa.amsl.com
Delivered-To: rtg-dt-encap-considerations@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9401A0066; Fri, 8 May 2015 05:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RnI9kR9H0jzi; Fri, 8 May 2015 05:42:09 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0102.outbound.protection.outlook.com [207.46.100.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C47571A0068; Fri, 8 May 2015 05:42:08 -0700 (PDT)
Received: from BLUPR05MB292.namprd05.prod.outlook.com (10.141.23.27) by BLUPR05MB289.namprd05.prod.outlook.com (10.141.23.19) with Microsoft SMTP Server (TLS) id 15.1.154.19; Fri, 8 May 2015 12:42:06 +0000
Received: from BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) by BLUPR05MB292.namprd05.prod.outlook.com ([10.141.23.27]) with mapi id 15.01.0154.018; Fri, 8 May 2015 12:42:06 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "Larry Kreeger (kreeger)" <kreeger@cisco.com>, Alia Atlas <akatlas@gmail.com>, "rtg-dt-encap-considerations@ietf.org" <Rtg-dt-encap-considerations@ietf.org>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>
Thread-Topic: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations
Thread-Index: AQHQFAH+I+6o7EGDlUuLu1ye4FsPSZ0bwPaAgFW+SwCAAAD4AIABbSTQ
Date: Fri, 8 May 2015 12:42:06 +0000
Message-ID: <BLUPR05MB2922E8F69F69BDDC887D8C8A9DE0@BLUPR05MB292.namprd05.prod.outlook.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com> <CAG4d1reDCGmGWwtEF1PtfNz-YB3Mjb56cs+epK8n1kpNetmEMw@mail.gmail.com> <D170E277.147C91%kreeger@cisco.com> <D170E3BD.147CA1%kreeger@cisco.com>
In-Reply-To: <D170E3BD.147CA1%kreeger@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;
x-originating-ip: [66.129.239.13]
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB289;
x-microsoft-antispam-prvs: <BLUPR05MB28992F6301F9B828B1E6B2AA9DE0@BLUPR05MB289.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:BLUPR05MB289; BCL:0; PCL:0; RULEID:; SRVR:BLUPR05MB289;
x-forefront-prvs: 0570F1F193
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(377454003)(164054003)(76176999)(19617315012)(33656002)(19625215002)(50986999)(54356999)(46102003)(2950100001)(19580405001)(2900100001)(19580395003)(122556002)(5001770100001)(76576001)(86362001)(74316001)(2656002)(19300405004)(16236675004)(40100003)(189998001)(66066001)(2201001)(102836002)(15975445007)(77096005)(230783001)(99286002)(106116001)(87936001)(77156002)(107886002)(5001960100002)(92566002)(19609705001)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB289; H:BLUPR05MB292.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: multipart/alternative; boundary="_000_BLUPR05MB2922E8F69F69BDDC887D8C8A9DE0BLUPR05MB292namprd_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2015 12:42:06.6031 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB289
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dt-encap-considerations/5KRjPIDnjbmBeAnn1FISPraNS54>
X-Mailman-Approved-At: Fri, 08 May 2015 06:34:26 -0700
Subject: Re: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations
X-BeenThere: rtg-dt-encap-considerations@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Design Team on Encapsulation Considerations discussion list <rtg-dt-encap-considerations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/>
List-Post: <mailto:rtg-dt-encap-considerations@ietf.org>
List-Help: <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 May 2015 12:42:13 -0000

Larry,

I think it makes sense to leave the name as is until the poll for WG adoption takes place on the mailing list.

Regards,
Chris

From: Larry Kreeger (kreeger) [mailto:kreeger@cisco.com]
Sent: Thursday, May 07, 2015 11:43 AM
To: Alia Atlas; rtg-dt-encap-considerations@ietf.org; rtgwg-chairs@ietf.org
Subject: Re: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations

OK, apparently there is no actual alias for routing-discussion-chairs.  Trying again with rtgwg-chairs.

From: Larry Kreeger <kreeger@cisco.com<mailto:kreeger@cisco.com>>
Date: Thursday, May 7, 2015 9:39 AM
To: "routing-discussion-chairs@ietf.org<mailto:routing-discussion-chairs@ietf.org>" <routing-discussion-chairs@ietf.org<mailto:routing-discussion-chairs@ietf.org>>, Alia Atlas <akatlas@gmail.com<mailto:akatlas@gmail.com>>, "rtg-dt-encap-considerations@ietf.org<mailto:rtg-dt-encap-considerations@ietf.org>" <Rtg-dt-encap-considerations@ietf.org<mailto:Rtg-dt-encap-considerations@ietf.org>>
Subject: Re: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations

Hi RTGWG Chairs,

At the RTGWG meeting in Dallas, I thought it was decided for the WG to either adopt, or call to adopt this document.  Erik is getting ready to publish a new version.  Should he rename it as a WG draft before doing that?

Thanks, Larry

From: Alia Atlas <akatlas@gmail.com<mailto:akatlas@gmail.com>>
Date: Friday, March 13, 2015 1:16 PM
To: "routing-discussion@ietf.org<mailto:routing-discussion@ietf.org>" <routing-discussion@ietf.org<mailto:routing-discussion@ietf.org>>
Subject: Re: routing area design team on dataplane encapsulation considerations

This design team has delivered a internet-draft, draft-rtg-dt-encap-01.
This draft will be discussed in RTGWG at IETF 92.  I would encourage you to all
read it and send comments to rtgwg.  I'm certain that the draft will be refined
and improved.

I'd like to thank the design team for their excellent work in a short time-frame.
I hope that this draft encourages useful discussion and thought as we move forward
on various encapsulations.

Regards,
Alia

On Tue, Dec 9, 2014 at 5:46 PM, Alia Atlas <akatlas@gmail.com<mailto:akatlas@gmail.com>> wrote:
I have chartered a Routing Area Design Team to work on data-plane encapsulation considerations.

I've bcc'd nvo3, sfc, bier, and rtgwg as the most directly relevant.  Please keep any conversation in one place on routing-discussion.

Erik Nordmark has kindly agreed to lead this design team.  The members of the design
team are:

  Albert Tian <albert.tian@ericsson.com<mailto:albert.tian@ericsson.com>>
  Erik Nordmark <nordmark@sonic.net<mailto:nordmark@sonic.net>>
  Jesse Gross <jgross@vmware.com<mailto:jgross@vmware.com>>
  Jon Hudson <jon.hudson@gmail.com<mailto:jon.hudson@gmail.com>>
  Larry Kreeger (kreeger) <kreeger@cisco.com<mailto:kreeger@cisco.com>>
  Pankaj Garg <Garg.Pankaj@microsoft.com<mailto:Garg.Pankaj@microsoft.com>>
  Pat Thaler <pthaler@broadcom.com<mailto:pthaler@broadcom.com>>
  Tom Herbert <therbert@google.com<mailto:therbert@google.com>>

The mailing list, rgt-dt-encap-considerations@ietf.org<mailto:rgt-dt-encap-considerations@ietf.org>, is closed but the archives are
publicly available at:
   http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/current/maillist.html

The Design Team is chartered as follows:

There have been multiple efforts over the years that have resulted in new or modified data plane behaviors involving encapsulations. That includes IETF efforts like MPLS, LISP, and TRILL but also industry efforts like Vxlan and NVGRE.  These collectively can be seen as a source of insight into the properties that data planes need to meet.  The IETF is currently working on potentially new encapsulations in NVO3 and SFC and considering working on BIER. In addition there is work on tunneling in the INT area.

This is a short term design team chartered to collect and construct useful advice to parties working on new or modified data plane behaviors that include additional encapsulations.  The goal is for the group to document useful advice gathered from interacting with ongoing efforts.  An Internet Draft will be produced for IETF92 to capture that advice, which will be discussed in RTGWG.

Data plane encapsulations face a set of common issues such as:

  * How to provide entropy for ECMP
  * Issues around packet size and fragmentation/reassembly
  * OAM - what support is needed in an encapsulation format?
  * Security and privacy.
  * QoS
  * Congestion Considerations
  * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
  * Extensibility - e.g., for evolving OAM, security, and/or congestion control
  * Layering of multiple encapsulations e.g., SFC over NVO3 over BIER

The design team will provide advice on those issues. The intention is that even where we have different encapsulations for different purposes carrying different data, each such encapsulation doesn't have to reinvent the wheel for the above common issues.
The design team will look across the routing area in particular at SFC, NVO3 and BIER. It will not be involved in comparing or analyzing any particular encapsulation formats proposed in those WGs and BoFs but instead focus on common advice.

Regards,
Alia