[Idr] Re： [Idr]_draft-chen-idr-bgp-ls-sr-policy-nrp-09_-_WG_adoption_call_(7/22/2024_to

[Idr] Re： [Idr]_draft-chen-idr-bgp-ls-sr-policy-nrp-09_-_WG_adoption_call_(7/22/2024_to_8/9/2024)

Yisong Liu <liuyisong@chinamobile.com> Wed, 24 July 2024 06:20 UTC

MIME-Version: 1.0
Date: Wed, 24 Jul 2024 14:20:17 +0800
From: Yisong Liu <liuyisong@chinamobile.com>
To: Susan Hares <shares@ndzh.com>, idr <idr@ietf.org>
Message-ID: <20240724142017268992679@chinamobile.com>
Content-Type: multipart/Alternative; boundary="----=_001_NextPart268992679_=----"
Message-ID-Hash: 45HFGPINANADPJ7ZKRD5H6HL75IC2N2H
Precedence: list
Subject: [Idr] Re： [Idr]_draft-chen-idr-bgp-ls-sr-policy-nrp-09_-_WG_adoption_call_(7/22/2024_to_8/9/2024)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0n5qbfBvC3-7Txnn8YZvUz4s5iY>

Hi Sue and WG members,

I support the adoption of this draft and my considerations about the questions are :

1. Yes, I think the additional information is very useful for NRP.

2. Yes, I think so.

3. I think there is no.

4. Yes , I think it's ready.

Best Regards

Yisong

发件人: Susan Hares

时间: 2024/07/23(星期二)09:41

收件人: idr;

主题: [Idr]_draft-chen-idr-bgp-ls-sr-policy-nrp-09_-_WG_adoption_call_(7/22/2024_to_8/9/2024)

This begins a 2+ week WG adoption call (7/22 to 8/9/2024)for

draft-chen-bgp-ls-sr-policy-nrp-09.txt.

(https://datatracker.ietf.org/doc/draft-chen-idr-bgp-ls-sr-policy-nrp/)

The authors should respond to this WG adoption call with an email with the IPR statement.

Document focus:

This document defines a new TLV in BGP-LS to report the NRP-ID

associated with an SR Candidate Policy Path (CP).

Links to Spring: During the 5/20/2024 interim, the following question was raised:

What is the relationship between the information in this draft and the information in draft-ietf-spring-resource-aware-segments?

Ran answered the following:

Due to the resource SID mechanism defined in the draft-ietf-spring-resource-aware-segments

(https://datatracker.ietf.org/doc/draft-ietf-spring-resource-aware-segments/)

the headend node does not have information about the relationship between

Candidate Path (CP) and NRP IDs, so it currently does not consider reporting the

relationship between CP and NRP ID. The current draft is only for the scenario

where data packets carry NRP ID. The NRP ID is used with the normal SR SID as

the resource used will be indicated by the NRP-ID. An SR Policy candidate path(CP)

may be instantiated with a specific NRP on the headend node via a local configuration,

PCEP, or BGP SR Policy signaling. Then the state and attributes of the NRP associated

with the candidate path of SR policy can be distributed to the controller.

In your discussion, please consider:

Is the addition of NRP-ID information to SR BGP-LS information valuable to networks? Does the draft clearly specify the TLV? Are there any security concerns about reporting NRP-ID? Is this document ready to adopt?

Cheerily, Sue

[Idr] Re： [Idr]_draft-chen-idr-bgp-ls-sr-policy-n… Yisong Liu