Re: Request for WG adoption of draft-rtg-dt-encap-02

Erik Nordmark <nordmark@acm.org> Fri, 29 May 2015 05:44 UTC

Return-Path: <nordmark@acm.org>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E19A41AD373; Thu, 28 May 2015 22:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no
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 a5VXL6mAK061; Thu, 28 May 2015 22:44:23 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 8652C1B2A19; Thu, 28 May 2015 22:44:23 -0700 (PDT)
Received: from [10.0.1.65] (70-36-183-173.dsl.dynamic.sonic.net [70.36.183.173]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t4T5heZd000606 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 28 May 2015 22:43:43 -0700
Message-ID: <5567FC89.1000703@acm.org>
Date: Thu, 28 May 2015 22:43:37 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Xuxiaohu <xuxiaohu@huawei.com>, Alia Atlas <akatlas@gmail.com>, Jeff Tantsura <jeff.tantsura@ericsson.com>
Subject: Re: Request for WG adoption of draft-rtg-dt-encap-02
References: <D184F48F.9A0F0%jeff.tantsura@ericsson.com> <CAG4d1reOu=nFrUyB7h-D=aBkaujAZmb8dLL9-9H90d8tEv5A8Q@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08337A3A@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08337A3A@NKGEML512-MBS.china.huawei.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVbzpFlPOyMM0OnhJVKIzHlltSrGqVDN5iemexEdX+//B0WXnxdHkG4T91poBjjKQhdfJ4FU2BwqQRGcp3GxZnwe
X-Sonic-ID: C;EpCeqMUF5RGq/zDDQUxNRQ== M;bJChqsUF5RGq/zDDQUxNRQ==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/oDywTnKFMOq7nmzQbjvrdceoOtY>
Cc: "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 May 2015 05:44:25 -0000

On 5/28/15 6:17 PM, Xuxiaohu wrote:
>
> Support the WG adoption of this draft and fully agree with Alia that 
> it would be much constructive to include more consideration around 
> MPLS and IP/UDP . For instance, does the MPLS encapsulation need an 
> explicit protocol identifier field to indicate the payload type in the 
> long run (e.g., completely eliminate the trouble of first nibble issue 
> for any future MPLS payload type)?
>
Xiaohu,
In -02 we added some text about the considerations for the first nibble 
over MPLS. But as the rest of the document this is phrased as a 
consideration and not a requirement.

> Does IP/UDP need a mandatory fragmentation capability on the tunnel layer?
>
That is a very good question. The IETF and Internet experience is that 
successful protocols are likely to be deployed outside of their initial 
target domain. So even if the initial target domain(s) don't need 
fragmentation it would seem prudent to at least include the option to be 
able to do fragmentation and reassembly. (Likewise goes for having 
sufficient extensibility to add higher levels of security should the 
protocol be used in different domains.)

Regards,
     Erik

> Best regards,
>
> Xiaohu
>
> *From:*rtgwg [mailto:rtgwg-bounces@ietf.org] *On Behalf Of *Alia Atlas
> *Sent:* Thursday, May 28, 2015 11:17 PM
> *To:* Jeff Tantsura
> *Cc:* rtgwg-chairs@ietf.org; rtgwg@ietf.org
> *Subject:* Re: Request for WG adoption of draft-rtg-dt-encap-02
>
> I support adopting this draft in RTGWG.
>
> I do hope to see the WG expand it to include more considerations 
> around MPLS
>
> as well as IP/UDP.
>
> Thanks,
>
> Alia
>
> On Fri, May 22, 2015 at 5:58 PM, Jeff Tantsura 
> <jeff.tantsura@ericsson.com <mailto:jeff.tantsura@ericsson.com>> wrote:
>
> Hi RTGWG,
>
> The authors have requested the RTGWG to adopt draft-rtg-dt-encap-02 as
> working group document.
>
>
> Please indicate support or no-support by June 8, 2015.
>
> If you are listed as a document author or contributor please respond to
> this email stating of whether or not you are aware of any relevant IPR.
> The response needs to be sent to the RTGWG mailing list. The document will
> not advance to the next stage until a response has been received from each
> author and each individual that has contributed to the document.
>
>
>
> Cheers,
> Jeff & Chris
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org <mailto:rtgwg@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtgwg
>
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg