Support.  The content of these drafts has been stable for a while, I think they 
are ready to progress.

I have some comments regarding to PSP, USP and USD flavors in 
draft-filsfils-spring-srv6-network-programming-07.

1:            What is the motivation for introducing the USD flavor?  With USD, 
then the END, END.T and END.X can be the last SID?

2:            In 
section-4.1<https://tools.ietf.org/html/draft-filsfils-spring-srv6-network-programming-06#section-4.1>
 , 4.2 and 4.3, the document says that End, End.X, End.T can not be the last 
SID of SID list.

                But in 
section-4.21.2<https://tools.ietf.org/html/draft-filsfils-spring-srv6-network-programming-06#section-4.21.2>,
 the End, End.X, and End.T can be the last SID when there is another SRH 
following.

                Even, in that case, the last SID of the SID list MUST be SID of 
End, End.X, and End.T, correct?

                If End, End.X, End.T can not be the last SID of SID list, then 
USP of End, End.X, End.T can not work.

So I think the text should be: End, End.X, and End.T SID can be the last SID if 
(1) it has USD flavor or (2) it has USP flavor while there is another SRH 
following it.

Thanks,
Cheng

From: spring [mailto:[email protected]] On Behalf Of Pablo Camarillo 
(pcamaril)
Sent: Thursday, February 14, 2019 4:56 PM
To: [email protected]
Subject: [spring] draft-filsfils-spring-srv6-network-programming

Dear Spring,

We have submitted a new revision of 
draft-filsfils-spring-srv6-network-programming. There are several minor updates 
to the document, mainly addressing ICMP and having better alignment with SRH 
draft. Also, based on WG feedback, we have split the document moving the 
illustrations into a new informational draft.
As always, any feedback or question is more than welcome.
https://datatracker.ietf.org/doc/draft-filsfils-spring-srv6-network-programming/
https://datatracker.ietf.org/doc/draft-filsfils-spring-srv6-net-pgm-illustration/

We believe that the content of both drafts is mature and has been stable since 
the first revision in March 2017. We are tracking several opensource and vendor 
proprietary implementations. Some of these have actually participated in a 
public interop more than a year ago.
For these reasons we believe that both documents are ready to progress and be 
adopted by the working group.

Thanks,
Pablo (on behalf of authors&contributors)

_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring

Reply via email to