Re: [spring] Last Call: (SRv6 Network Programming) to Proposed Standard

2020-08-20 Thread Brian E Carpenter
IMHO there is still a logical defect in the description of the PSP flavor at https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-17#section-4.16.1 The description of the PSP flavor considers the packet to have (Segments Left == 0 and Destination Address == the PSP node's

Re: [spring] WG adoption call for draft-hegde-spring-node-protection-for-sr-te-paths

2020-08-20 Thread Dhruv Dhody
Hi WG, Authors, I support adoption. Looking forward to changes as per the discussion in the other thread started by Joel. I found a few things that can increase the readability of the document. Minor - The document doesn't use normative keywords of RFC 2119 (RFC 2119 is in reference somehow

[spring] Opsdir last call review of draft-ietf-spring-srv6-network-programming-17

2020-08-20 Thread Dan Romascanu via Datatracker
Reviewer: Dan Romascanu Review result: Has Issues This document together with the companion document [I-D.filsfils-spring-srv6-net-pgm-illustration] defines the SRv6 Network Programming concept and specifies the main segment routing behaviors to enable the creation of interoperable overlays with

[spring] Opsdir last call review of draft-ietf-spring-srv6-network-programming-17

2020-08-20 Thread Dan Romascanu via Datatracker
Reviewer: Dan Romascanu Review result: Has Issues This document together with the companion document [I-D.filsfils-spring-srv6-net-pgm-illustration] defines the SRv6 Network Programming concept and specifies the main segment routing behaviors to enable the creation of interoperable overlays with