[mpls] 答复: 答复: MPLS WG last call on draft-ietf-mpls-in-udp-03.txt

Xuxiaohu <xuxiaohu@huawei.com> Thu, 26 September 2013 01:38 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 227F121F8B07 for <mpls@ietfa.amsl.com>; Wed, 25 Sep 2013 18:38:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.287
X-Spam-Level:
X-Spam-Status: No, score=-4.287 tagged_above=-999 required=5 tests=[AWL=1.859, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W+PPxWM6TFyx for <mpls@ietfa.amsl.com>; Wed, 25 Sep 2013 18:38:26 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5062811E80E6 for <mpls@ietf.org>; Wed, 25 Sep 2013 18:38:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYG20651; Thu, 26 Sep 2013 01:38:20 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 26 Sep 2013 02:36:57 +0100
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 26 Sep 2013 02:37:49 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.24]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0146.000; Thu, 26 Sep 2013 09:37:44 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Sriganesh Kini <sriganesh.kini@ericsson.com>
Thread-Topic: [mpls] 答复: MPLS WG last call on draft-ietf-mpls-in-udp-03.txt
Thread-Index: AQHOuJTBti6HsDHau06ivnjZ3yhz8ZnUExaggAJ/cYCAAKm1oA==
Date: Thu, 26 Sep 2013 01:37:43 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08211EDA@NKGEML512-MBS.china.huawei.com>
References: <98952a55996f40da8cbcb663561f580b@BLUPR05MB070.namprd05.prod.outlook.com> <CAOndX-tKDYahywihZ8fAv3MyRRUHW2=cNG+FSfkNucpcLws0tw@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08211182@NKGEML512-MBS.china.huawei.com> <CAOndX-uiMYt_m=jxhPnr6v_cDRn1ZHeDzgjBDF74-_6TUzpzgQ@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082115B5@NKGEML512-MBS.china.huawei.com> <CAOndX-v+0-=S7gxMbjHC384w_gvpNO5kNQQYNcUYwwTjD826Xw@mail.gmail.com>
In-Reply-To: <CAOndX-v+0-=S7gxMbjHC384w_gvpNO5kNQQYNcUYwwTjD826Xw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.130]
Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08211EDANKGEML512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Ross Callon <rcallon@juniper.net>, "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "fanyb@gsta.com" <fanyb@gsta.com>
Subject: [mpls] 答复: 答复: MPLS WG last call on draft-ietf-mpls-in-udp-03.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Sep 2013 01:38:31 -0000

Hi Sri,

Since you don’t see how that draft (http://tools.ietf.org/html/draft-yong-l3vpn-nvgre-vxlan-encap-00) helps, I’m curious to know why you had intentionally mentioned draft-quinn-vxlan-gpe before. Have you found any significant difference between them?

Best regards,
Xiaohu

发件人: sriganeshkini@gmail.com [mailto:sriganeshkini@gmail.com] 代表 Sriganesh Kini
发送时间: 2013年9月26日 7:14
收件人: Xuxiaohu
抄送: Ross Callon; mpls@ietf.org; mpls-chairs@tools.ietf.org; fanyb@gsta.com
主题: Re: [mpls] 答复: MPLS WG last call on draft-ietf-mpls-in-udp-03.txt

Hi Xu,

I read the other draft you pointed to and I don't see how that helps. What I had said earlier was that having a protocol-id in a header following the UDP header but before the user payload (in this draft the MPLS packet is the user payload) keeps the design generic and any protocol (not just MPLS applications) can then use such an encapsulation. Standardizing UDP port numbers to denote protocol types consumes the port number space and is unnecessary. Another important point is that developing OAM using a header after the UDP hdr but before the user-payload is easier.

- Sri

On Mon, Sep 23, 2013 at 7:00 PM, Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>> wrote:
Hi Sri,

It’s no problem provided that anybody was willing to use VXLAN-GPE to replace the existing MPLS-based applications such as L2 or L3 VPN services. Furthermore, there is another choice for VXLAN extension other than VXLAN-GPE, which has been described in http://tools.ietf.org/html/draft-yong-l3vpn-nvgre-vxlan-encap-00. I’m willing to hear your further comments on the comparison of these two options for VXLAN extension (Maybe MPLS WG is not a suitable place to talk about this topic).

Xiaohu

发件人: sriganeshkini@gmail.com<mailto:sriganeshkini@gmail.com> [mailto:sriganeshkini@gmail.com<mailto:sriganeshkini@gmail.com>] 代表 Sriganesh Kini
发送时间: 2013年9月24日 3:40
收件人: Xuxiaohu
抄送: Ross Callon; mpls@ietf.org<mailto:mpls@ietf.org>; mpls-chairs@tools.ietf.org<mailto:mpls-chairs@tools.ietf.org>; fanyb@gsta.com<mailto:fanyb@gsta.com>
主题: Re: [mpls] 答复: MPLS WG last call on draft-ietf-mpls-in-udp-03.txt

Hi Xu,

The existing encapsulations you pointed out were defined a long time ago. Whereas the other two are just being proposed now. Moreover if we follow this approach it will require standardizing UDP port numbers for each new protocol to encap into UDP.

- Sri

On Sun, Sep 22, 2013 at 11:02 PM, Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>> wrote:
Hi Sri,

发件人: mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org> [mailto:mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org>] 代表 Sriganesh Kini
发送时间: 2013年9月21日 7:06
收件人: Ross Callon
抄送: mpls@ietf.org<mailto:mpls@ietf.org>; mpls-chairs@tools.ietf.org<mailto:mpls-chairs@tools.ietf.org>; fanyb@gsta.com<mailto:fanyb@gsta.com>
主题: Re: [mpls] MPLS WG last call on draft-ietf-mpls-in-udp-03.txt

There is no reference cited for the "MPLS-in-IP" encapsulation.

[Xiaohu] MPLS-in-IP and MPLS-in-GRE are actually specified in the same RFC that is RFC4023.

What is the applicability of this encapsulation compared to the generalized mechanism in draft-quinn-vxlan-gpe ?

[Xiaohu] The applicability of this encapsulation is the same as the existing IP-based encapsulations for MPLS (e.g., MPLS-in-GRE).

Best regards,
Xiaohu

- Sri

On Thu, Sep 12, 2013 at 9:42 AM, Ross Callon <rcallon@juniper.net<mailto:rcallon@juniper.net>> wrote:
Working Group,

This is to start Working Group last call on  draft-ietf-mpls-in-udp-03.txt

Please send your comments to the mpls working group mailing list (mpls@ietf.org<mailto:mpls@ietf.org>).

Please send both technical comments, and (if you are happy with the document as is)
also send indications of support.

There is one IPR claim that applies to this draft, which can be seen at:
https://datatracker.ietf.org/ipr/1941/

The coauthors and contributor have indicated that they don’t know of any other
IPR applicable to this draft. If anyone else in the working group is aware of IPR
claims against this draft, the time to disclose that is now.

This working group last call will end on September 27, 2013.

Ross
for the wg co-chairs


_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls