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

Jeff Tantsura <jeff.tantsura@ericsson.com> Fri, 08 May 2015 14:09 UTC

Return-Path: <jeff.tantsura@ericsson.com>
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 DA1D71A1B57; Fri, 8 May 2015 07:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 5UZvvs0oD_uP; Fri, 8 May 2015 07:09:45 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF9C71A040B; Fri, 8 May 2015 07:09:44 -0700 (PDT)
X-AuditID: c618062d-f79a96d000007fb1-24-554c6b9aa868
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 1B.74.32689.A9B6C455; Fri, 8 May 2015 09:54:03 +0200 (CEST)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0210.002; Fri, 8 May 2015 10:09:41 -0400
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: Erik Nordmark <nordmark@sonic.net>
Thread-Topic: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations
Thread-Index: AQHQFAIB9AftLv4vd0W9L13ZsyC06p0bwPaAgFW+SwCAAAD4AIABs5kAgAAPe4D//8Xwzw==
Date: Fri, 8 May 2015 14:09:41 +0000
Message-ID: <3D64D6B0-14F6-43D7-8374-2E65659F1ABF@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>
In-Reply-To: <554CBC1B.2040403@sonic.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="windows-1251"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrCLMWRmVeSWpSXmKPExsUyuXRPoO7sbJ9Qg4OXBC0+PbzEbPFjvavF gjeLWSxedm5gs5jQ94rJYv/axcwObB5Tfm9k9dg56y67x5IlP5k8rjddZfd42t3MEsAaxWWT kpqTWZZapG+XwJWx9kkzU8Fas4qry+IaGJ9odzFyckgImEj8a7zDCGGLSVy4t56ti5GLQ0jg KKPE28V72CGcZYwS/5b/ZAKpYhMwkPj/7TgLiC0ioCZx9elXsCJmgb+MEoub/wO1c3AIC+RL zP4bC1FTIPHj6ydGCDtMouXbdTYQm0VARWLWgX+sIDavgL3Ezg1fmCCWnWeSeLTnAwvIHE4B TYlVHytAahiBrvt+ag3YDcwC4hK3nsxngrhaQGLJnvPMELaoxMvHIDM5gGoMJP5tYIYo15ZY tvA1M8QqQYmTM5+wTGAUnYVk0iyEjllIOmYh6VjAyLKKkaO0OLUsN93IYBMjMJqOSbDp7mDc 89LyEKMAB6MSD2/CA+9QIdbEsuLK3EOM0hwsSuK8ix4cDBESSE8sSc1OTS1ILYovKs1JLT7E yMTBKdXAqN4eY6ktHmtZKrLp5l7d2ivTHIJCf5/+EXjs+4cf87WEeeYFSO/LO/noedvpM4fT P393ePD3F8sX7/uLtqyaGb7hn4Oq5Artzkmn58rtvJ3cyjhtcbHZyl0/3bslp09/oXSyWGnu qWXZ2Ub6bjwzPVbwtUv9EdK1fyh3/qq0fuGuv9/acg2+vVdiKc5INNRiLipOBAAxrph4hwIA AA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dt-encap-considerations/8mKstlxyVAtnT79nMdvejaWgbW8>
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: Fri, 08 May 2015 14:09:48 -0000

Erik,

Please publish 02, we will review it as well as  ask for a Routing Directorate QA reviewer and poll WG in parallel.
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
>