IETF Logo Mail Archive

[Idr] Mail regarding draft-ietf-idr-segment-routing-te-policy

Zhuangshunwan <zhuangshunwan@huawei.com> Wed, 17 August 2022 11:15 UTC

Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3FAC1527A4 for <idr@ietfa.amsl.com>; Wed, 17 Aug 2022 04:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.206
X-Spam-Level:
X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSzYnr0bQknm for <idr@ietfa.amsl.com>; Wed, 17 Aug 2022 04:15:34 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A188CC1527A6 for <idr@ietf.org>; Wed, 17 Aug 2022 04:15:33 -0700 (PDT)
Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4M752f10lmz67dbJ for <idr@ietf.org>; Wed, 17 Aug 2022 19:12:26 +0800 (CST)
Received: from kwepemi100001.china.huawei.com (7.221.188.215) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Wed, 17 Aug 2022 13:15:30 +0200
Received: from kwepemi500002.china.huawei.com (7.221.188.171) by kwepemi100001.china.huawei.com (7.221.188.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 17 Aug 2022 19:15:28 +0800
Received: from kwepemi500002.china.huawei.com ([7.221.188.171]) by kwepemi500002.china.huawei.com ([7.221.188.171]) with mapi id 15.01.2375.024; Wed, 17 Aug 2022 19:15:28 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Mail regarding draft-ietf-idr-segment-routing-te-policy
Thread-Index: AdiyKNQdyL8nIOAHQMqGopjAbpm/gg==
Date: Wed, 17 Aug 2022 11:15:28 +0000
Message-ID: <458515bea80d4cffa2bbd7b7533bfe49@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.95]
Content-Type: multipart/alternative; boundary="_000_458515bea80d4cffa2bbd7b7533bfe49huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TKVF7jqAbyS6oDCMRMznfMXk5Kw>
Subject: [Idr] Mail regarding draft-ietf-idr-segment-routing-te-policy
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2022 11:15:36 -0000

Hi authors,

Regarding the Length Field of the Weight Sub-TLV, section 2.4.4.1.said its value MUST be 8.
If I understand correctly, maybe it should be 6?

The following text is extracted from the draft https://www.ietf.org/archive/id/draft-ietf-idr-segment-routing-te-policy-20.txt:
[snip]
2.4.4.1.  Weight Sub-TLV

   The Weight sub-TLV specifies the weight associated with a given
   segment list.  The contents of this sub-TLV are used only by the SRPM
   as described in section 2.11 of [RFC9256].

   The Weight sub-TLV is optional and it MUST NOT appear more than once
   inside the Segment List sub-TLV.

   The Weight sub-TLV has the following format:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |   Length      |     Flags     |   RESERVED    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                              Weight                           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Figure 10: Weight sub-TLV

   where:

   o  Type: 9.

   o  Length: Specifies the length of the value field (i.e., not
      including Type and Length fields) in terms of octets.  The value
      MUST be 8.
[snip]

Regards,
Shunwan

v2.23.0 | Report a Bug | By Email