[bess] MPLS Label value 3 in <draft-dawra-bess-srv6-services-00>
Xiejingrong <xiejingrong@huawei.com> Thu, 27 June 2019 11:56 UTC
Return-Path: <xiejingrong@huawei.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAECF120221; Thu, 27 Jun 2019 04:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 ZFRlbDehSP2q; Thu, 27 Jun 2019 04:56:45 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 ECFD81200C5; Thu, 27 Jun 2019 04:56:44 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 5E932C13D894757ED5C4; Thu, 27 Jun 2019 12:56:43 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 27 Jun 2019 12:56:42 +0100
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0415.000; Thu, 27 Jun 2019 19:56:32 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: "draft-dawra-bess-srv6-services@ietf.org" <draft-dawra-bess-srv6-services@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: MPLS Label value 3 in <draft-dawra-bess-srv6-services-00>
Thread-Index: AdUs3vWoGdUb+Au9QLKp/OVbHShbCg==
Date: Thu, 27 Jun 2019 11:56:31 +0000
Message-ID: <16253F7987E4F346823E305D08F9115AAB8D7F79@nkgeml514-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.217.214]
Content-Type: multipart/alternative; boundary="_000_16253F7987E4F346823E305D08F9115AAB8D7F79nkgeml514mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/MAbBt-WZfqipI0Lc950kBywE-kA>
Subject: [bess] MPLS Label value 3 in <draft-dawra-bess-srv6-services-00>
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2019 11:56:47 -0000
Hi folks, One question about MPLS Label value 3 used in <draft-dawra-bess-srv6-services-00>: the Label value in any service route NLRI encoding MUST be set to Implicit NULL [RFC3032]. Label = Implicit NULL I think the more common use of MPLS Label to represent "invalid" is to use zero, as in RFC7432 and RFC6556. Why this document use value 3 (Implicit NULL as defined in RFC3032) ? Thanks Jingrong
- [bess] MPLS Label value 3 in <draft-dawra-bess-sr… Xiejingrong
- Re: [bess] MPLS Label value 3 in <draft-dawra-bes… Xiejingrong