Re: [mpls] [nvo3] Encapsulation considerations

Xuxiaohu <xuxiaohu@huawei.com> Thu, 09 April 2015 02:20 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81EA81B2A28; Wed, 8 Apr 2015 19:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.761
X-Spam-Level:
X-Spam-Status: No, score=-1.761 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 1qYiwCyXgeYn; Wed, 8 Apr 2015 19:20:30 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19E9C1B2A27; Wed, 8 Apr 2015 19:20:28 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUQ26433; Thu, 09 Apr 2015 02:20:27 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Apr 2015 03:20:26 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.209]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Thu, 9 Apr 2015 10:20:21 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Erik Nordmark <nordmark@acm.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [nvo3] Encapsulation considerations
Thread-Index: AQHQcljZ0fVc246YHEKvkFIl2pYVuJ1D7uKA
Date: Thu, 09 Apr 2015 02:20:21 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08323BD3@NKGEML512-MBS.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0832353F@NKGEML512-MBS.china.huawei.com> <5525C22C.1030303@acm.org>
In-Reply-To: <5525C22C.1030303@acm.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/e6KDDRGJ1lYBp3nPAM_Pv4nY0Ac>
Cc: "mpls@ietf.org" <mpls@ietf.org>, BIER <bier@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [mpls] [nvo3] Encapsulation considerations
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Apr 2015 02:20:31 -0000

Hi Erik,

> -----Original Message-----
> From: Erik Nordmark [mailto:nordmark@acm.org]
> Sent: Thursday, April 09, 2015 8:05 AM
> To: Xuxiaohu; nvo3@ietf.org
> Subject: Re: [nvo3] Encapsulation considerations
> 
> On 4/7/15 7:15 PM, Xuxiaohu wrote:
> > Hi Erik,
> >
> > As it has said in the draft : "... We later expanded the scope somewhat to
> consider how the encapsulations would play with MPLS "transport", which is
> important because SFC and BIER seem to target being dependent of the
> underlying "transport"...", it would be necessary to consider the first nibble
> issue for those encapsulations which may be transported over MPLS. More
> specifically, for those encapsulations which may be directly encapsulated further
> with an MPLS header, they must not start with the value 4 (IPv4) or the value 6
> (IPv6) in the first nibble. Otherwise, they would be mistakenly interpreted as IP
> payloads by transit LSRs and therefore be subjected to ECMP and potential
> packet misordering.
> 
> Xiaohu,
> Good point.
> 
> But I couldn't tell from the emails on the BIER list whether the constraints on the
> first nibble value is a strict requirement in all cases, or whether it is conditional
> on something (and if so, what is the condition).

The conditions that I have thought of include: 1) the encapsulation is sensitive to packet misordering; 2) the encapsulation may be transported over an MPLS PSN; 3) LSRs within that MPLS PSN may use the contents of the MPLS payload to select the ECMP path.

Best regards,
Xiaohu 

> Once I know that answer we can definitely add some text pointing out the issue.
> 
> Thanks,
>     Erik
> 
> >
> > Best regards,
> > Xiaohu
> >
> >> -----Original Message-----
> >> From: Erik Nordmark [mailto:nordmark@sonic.net]
> >> Sent: 2015年3月26日 5:01
> >> To: nvo3@ietf.org
> >> Subject: [nvo3] Encapsulation considerations
> >>
> >>
> >> I presented part of this at the most recent NVO3 interim meeting.The
> >> full
> > 12
> >> areas of considerations where presented at RTGWG earlier this week.
> >>    The draft is
> >>      http://datatracker.ietf.org/doc/draft-rtg-dt-encap/
> >>    and the slides are at
> >>     http://www.ietf.org/proceedings/92/slides/slides-92-rtgwg-8.pdf
> >>
> >> There is probably additional things in there to consider for NVO3,
> >> and
> > advice
> >> that can be reused to make it easier to move NVO3 forward.
> >>
> >> Regards,
> >>      Erik
> >>
> >>
> >>
> >
> > _______________________________________________
> > nvo3 mailing list
> > nvo3@ietf.org
> > https://www.ietf.org/mailman/listinfo/nvo3
> >