Re: [spring] WGLC for https://datatracker.ietf.org/doc/draft-ietf-spring-mpls-path-segment/

I support publication of this draft.

I see a lot of value for operators with this draft encoding of the path
into a path segment for end to end 1+1 path protection and PM and path
correlation and bidirectional path instantiation for mobile backhaul.

In section 4 it talks about nesting of path segments. So basically on an
end to end path you with the nesting we can take advantage of SID list
compression by a combination of BSID and PSID allocated for the end to end
path where s-PSID amis the PSID of each sub path snd e-SID is the end to
end E2E path.  As BSID is binds the candidate path to the forwarding plane,
is the Per sub path s-PSID and e-SID included as part of of the SR-TE
policy end to end policy.  I  did not see PSID mentioned in the SR path
Segment Policy draft.

This draft does not mention SRv6 use case, however the SR path policy draft
does mention SRv6 support via sub TLV Segment type flag to support both
SR-MPLS and SRv6.  In this draft it does mention use of the path Segment to
define the sub paths in the SR-TE policy.

https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr-policy-path-segment

I found the corresponding path Segment draft for SRv6 path Segment.
Perfect!

https://datatracker.ietf.org/doc/html/draft-li-spring-srv6-path-segment-00

Also the PCE draft for SR path Segment.

https://datatracker.ietf.org/doc/html/draft-ietf-pce-sr-path-segment

I see that the PCE draft uses the PCE CC centralized controller CCI object
for the stateful PCE path Segment instantiated.

Makes sense as this is an E2E inter-as end to end path using sub paths
defined in the compressed SID list s-PSID sub paths.

Regards

Gyan

On Wed, Jul 28, 2021 at 11:08 PM Aijun Wang <wangaijun@tsinghua.org.cn>
wrote:

> Support its publication.
>
>
>
>
>
> Best Regards
>
>
>
> Aijun Wang
>
> China Telecom
>
>
>
> *From:* spring-bounces@ietf.org <spring-bounces@ietf.org> *On Behalf Of *James
> Guichard
> *Sent:* Thursday, July 22, 2021 9:03 PM
> *To:* James Guichard <james.n.guichard@futurewei.com>; spring@ietf.org
> *Cc:* spring-chairs@ietf.org
> *Subject:* Re: [spring] WGLC for
> https://datatracker.ietf.org/doc/draft-ietf-spring-mpls-path-segment/
>
>
>
> Dear WG:
>
>
>
> The WGLC for this document will be extended for a further 2 weeks ending
> August 4th 2021 so that feedback can be obtained from the WG. Other than
> the authors there has been little input so please respond on the mailing
> list with any comments etc.
>
>
>
> Thanks!
>
>
>
> Jim, Joel & Bruno
>
>
>
> *From:* James Guichard <james.n.guichard@futurewei.com>
> *Sent:* Wednesday, July 7, 2021 11:49 AM
> *To:* spring@ietf.org
> *Cc:* spring-chairs@ietf.org
> *Subject:* WGLC for
> https://datatracker.ietf.org/doc/draft-ietf-spring-mpls-path-segment/
>
>
>
> Dear WG:
>
>
>
> This email starts a 2 week Working Group Last Call for
> draft-ietf-spring-mpls-path-segment [1].
>
>
>
> Please read this document if you haven’t read the most recent version and
> send your comments to the SPRING WG list no later than July 21st 2021.
>
>
>
> If you are raising a point which you expect will be specifically debated
> on the mailing list, consider using a specific email/thread for this point.
>
>
>
> Lastly, if you are an author or contributor please response to indicate
> whether you know of any undisclosed IPR related to this document.
>
>
>
> Thanks!
>
>
>
> Jim, Joel & Bruno
>
>
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-spring-mpls-path-segment/
> <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-spring-mpls-path-segment%2F&data=04%7C01%7Cjames.n.guichard%40futurewei.com%7C4336eaaa34f543cc4c9e08d9415ebd06%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637612697462524718%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=v18Zntmw18jYiIXCNMDa7bYNQMZ90U29GVEkuPh5CjE%3D&reserved=0>
>
>
>
>
>
>
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*

*M 301 502-1347*