[Lsr] some doubt about RFC5329 ( Traffic Engineering Extensions to OSPF Version 3)
"Zengmin (A)" <jenny.zeng@huawei.com> Tue, 20 April 2021 06:34 UTC
Return-Path: <jenny.zeng@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FC453A11AB for <lsr@ietfa.amsl.com>; Mon, 19 Apr 2021 23:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_RATIO_02=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 VPF6PQbVG195 for <lsr@ietfa.amsl.com>; Mon, 19 Apr 2021 23:34:41 -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 0126A3A11A5 for <lsr@ietf.org>; Mon, 19 Apr 2021 23:34:41 -0700 (PDT)
Received: from fraeml734-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FPYgD71wJz70gZR for <lsr@ietf.org>; Tue, 20 Apr 2021 14:29:12 +0800 (CST)
Received: from dggpemm500005.china.huawei.com (7.185.36.74) by fraeml734-chm.china.huawei.com (10.206.15.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Tue, 20 Apr 2021 08:34:37 +0200
Received: from dggema774-chm.china.huawei.com (10.1.198.216) by dggpemm500005.china.huawei.com (7.185.36.74) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Tue, 20 Apr 2021 14:34:35 +0800
Received: from dggema774-chm.china.huawei.com ([10.9.49.88]) by dggema774-chm.china.huawei.com ([10.9.49.88]) with mapi id 15.01.2176.012; Tue, 20 Apr 2021 14:34:35 +0800
From: "Zengmin (A)" <jenny.zeng@huawei.com>
To: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr]some doubt about RFC5329 ( Traffic Engineering Extensions to OSPF Version 3)
Thread-Index: Adc1rxoxIHndZa5IT2yTlS6B9lRkVQ==
Date: Tue, 20 Apr 2021 06:34:35 +0000
Message-ID: <f2642406dc8849c58b4c4b6455f35181@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.140]
Content-Type: multipart/related; boundary="_006_f2642406dc8849c58b4c4b6455f35181huaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/geCuv7NC3Ec0hPsydXho1ZwQvIY>
Subject: [Lsr] some doubt about RFC5329 ( Traffic Engineering Extensions to OSPF Version 3)
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2021 06:34:46 -0000
Hi ALL, In RFC5329, OSPFv3 TE Link TLV have below sub-TLVs 18 - Neighbor ID (8 octets) ： Neighbor Interface ID ， Neighbor Router ID 19 - Local Interface IPv6 Address 20 - Remote Interface IPv6 Address question1： 4.4. Remote Interface IPv6 Address Sub-TLV if link-LSA not have a prefix length of 128 and the LA-bit how to get remote Interface ipv6 address to fill the tlv value. question2： if router only advertise : 18 - Neighbor ID (8 octets) ： Neighbor Interface ID ， Neighbor Router ID 19 - Local Interface IPv6 Address how to match router's TE Link TLV with peer router's TE Link TLV question3： 4. Link TLV --- " The Neighbor ID sub-TLV is mandatory for OSPFv3 Traffic Engineering support. " it means Local Interface IPv6 Address Sub-TLV is not mandatory if only advertise : 18 - Neighbor ID (8 octets) how to match router's TE Link TLV with peer router's TE Link TLV Thanks, Jenny In section 4 Link TLV： [cid:image001.png@01D735F2.45CB2D20] [cid:image002.png@01D735F2.45CB2D20] [cid:image003.png@01D735F2.45CB2D20]