[Pce] F and S bit in draft-ietf-pce-segment-routing
"Chengli (Cheng Li)" <chengli13@huawei.com> Wed, 21 August 2019 03:27 UTC
Return-Path: <chengli13@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F17812006F; Tue, 20 Aug 2019 20:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 9pP34fSyyRJh; Tue, 20 Aug 2019 20:27:09 -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 5BD8F120045; Tue, 20 Aug 2019 20:27:09 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id D812EBCA62C111FC102A; Wed, 21 Aug 2019 04:27:06 +0100 (IST)
Received: from DGGEML402-HUB.china.huawei.com (10.3.17.38) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 21 Aug 2019 04:27:06 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.7]) by DGGEML402-HUB.china.huawei.com ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0439.000; Wed, 21 Aug 2019 11:22:30 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: "draft-ietf-pce-segment-routing@ietf.org" <draft-ietf-pce-segment-routing@ietf.org>
CC: "pce@ietf.org" <pce@ietf.org>
Thread-Topic: F and S bit in draft-ietf-pce-segment-routing
Thread-Index: AdVXzvu4+dlTCsUZQvixd/OE/voQLA==
Date: Wed, 21 Aug 2019 03:22:30 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB0268B69D@dggeml529-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.130.185.75]
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB0268B69Ddggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/SD7yWuj1lOVY2n2PMgK901ygmUs>
Subject: [Pce] F and S bit in draft-ietf-pce-segment-routing
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2019 03:27:11 -0000
Hi authors, I am a little bit confusing of F and S bit in SR-ERO subobject. https://tools.ietf.org/html/draft-ietf-pce-segment-routing-16#section-4.3.1 What is F standing for ? and how about S ? S for SID? It seems like S and F bit can not be set at the same time, correct? Thanks, Cheng
- [Pce] F and S bit in draft-ietf-pce-segment-routi… Chengli (Cheng Li)
- Re: [Pce] F and S bit in draft-ietf-pce-segment-r… Dhruv Dhody