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

Erik Nordmark <nordmark@sonic.net> Thu, 14 May 2015 21:29 UTC

Return-Path: <nordmark@sonic.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 DACF01A885F; Thu, 14 May 2015 14:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 CL89hyWACeqS; Thu, 14 May 2015 14:29:10 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 855801A8AB5; Thu, 14 May 2015 14:29:10 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t4ELT327009487 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 14 May 2015 14:29:03 -0700
Message-ID: <5555139E.5050101@sonic.net>
Date: Thu, 14 May 2015 14:29:02 -0700
From: Erik Nordmark <nordmark@sonic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Jeff Tantsura <jeff.tantsura@ericsson.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> <BLUPR05MB2922E8F69F69BDDC887D8C8A9DE0@BLUPR05MB292.namprd05.prod.outlook.com>, <554CBC1B.2040403@sonic.net> <3D64D6B0-14F6-43D7-8374-2E65659F1ABF@ericsson.com>
In-Reply-To: <3D64D6B0-14F6-43D7-8374-2E65659F1ABF@ericsson.com>
Content-Type: text/plain; charset=windows-1251; format=flowed
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVZ1GUiYTO3t4k+kxv6ez0izyTJF96Q2hXSCfmi4CcuxSdP5anXGxVtrKjkzBcxg6l8mFj10rbEFbFR1SQu9YbFF
X-Sonic-ID: C;HGQhPoD65BG0efjYVPtzAg== M;gM0rPoD65BG0efjYVPtzAg==
X-Sonic-Spam-Details: 1.2/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dt-encap-considerations/rqLiBVjLvAvaS8uNQbgWERd2YX8>
Cc: "rtg-dt-encap-considerations@ietf.org" <Rtg-dt-encap-considerations@ietf.org>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "Larry Kreeger \(kreeger\)" <kreeger@cisco.com>, Chris Bowers <cbowers@juniper.net>, Alia Atlas <akatlas@gmail.com>
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: Thu, 14 May 2015 21:29:13 -0000

On 5/8/15 7:09 AM, Jeff Tantsura wrote:
> Erik,
>
> Please publish 02, we will review it as well as  ask for a Routing Directorate QA reviewer and poll WG in parallel.
OK, the DT should get 02 out by the end of next week.

   Erik

> Chris - what do you think?
>
>
>
> Regards,
> Jeff
>
>> On May 8, 2015, at 11:38 PM, Erik Nordmark <nordmark@sonic.net> wrote:
>>
>>
>> Chris,
>>
>> When are you planning to do the WG adoption call?
>> You could either do that now on -01, or wait for about 2 weeks and we will have a -02 out.
>>
>> Thanks,
>>    Erik
>>
>>> On 5/8/15 5:42 AM, Chris Bowers wrote:
>>>
>>> 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
>>>
>>>
>>>
>>> _______________________________________________
>>> Rtg-dt-encap-considerations mailing list
>>> Rtg-dt-encap-considerations@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtg-dt-encap-considerations