Ole,

I have reviewed version-02 of this document and believe that it still has the 
following major issues:

- Section 3.1.1 assumes implementation details (e.g., that the implementation 
has an OAM process) but fails to describe any externally observable behavior. 
The externally observable behaviors are described, incompletely, in Sections 
4.1.2 and 4.2.2.

- Section 3.5 seems to be incomplete. What TLV are we talking about and what 
role does it play?

- Section 4 talks about future revisions of this document. Aren't we in WGLC?

- Section 4.1.2.1 - When the ping succeeds, what does the success message look 
like? An ICMP Echo Response? What is the source address? A SID?

- Section 4.1.2.2 - Does this work with PSP?

- Section 4.2.2.1 - Do we need to examine flags even when SL == 0?

                                                                                
                    Ron



Juniper Business Use Only

-----Original Message-----
From: ipv6 <ipv6-boun...@ietf.org> On Behalf Of Ole Troan
Sent: Wednesday, December 4, 2019 3:53 PM
To: 6man WG <i...@ietf.org>; SPRING WG <spring@ietf.org>
Cc: 6man Chairs <6man-cha...@ietf.org>
Subject: 6man w.g. last call for <draft-ietf-6man-spring-srv6-oam>

Hello,

  As agreed in the working group session in Singapore, this message starts a 
new two week 6MAN Working Group Last Call on advancing:

  Title    : Operations, Administration, and Maintenance (OAM) in Segment 
Routing Networks with IPv6 Data plane (SRv6)
  Author   : Z. Ali, C. Filsfils, S. Matsushima, D. Voyer, M. Chen
  Filename : draft-ietf-6man-spring-srv6-oam-02
  Pages    : 23
  Date     : 2019-11-20
                         
    
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-6man-spring-srv6-oam/__;!8WoA6RjC81c!XSqnzjZKANP41cvNa8ybSjYCuTDO6XCHjQyZ4ARNtx4MhYWG7vdEvXi-22No-zDm$
 

as a Proposed Standard.  

Substantive comments and statements of support for publishing this document 
should be directed to the mailing list.
Editorial suggestions can be sent to the author. This last call will end on the 
18th of December 2019.

To improve document quality and ensure that bugs are caught as early as 
possible, we would require at least two reviewers to do a complete review of 
the document.  Please let the chairs know if you are willing to be a reviewer.

The last call will be forwarded to the spring working group, with discussion 
directed to the ipv6 list.

Thanks,
Bob & Ole, 6man co-chairs


--------------------------------------------------------------------
IETF IPv6 working group mailing list
i...@ietf.org
Administrative Requests: 
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ipv6__;!8WoA6RjC81c!XSqnzjZKANP41cvNa8ybSjYCuTDO6XCHjQyZ4ARNtx4MhYWG7vdEvXi-2-1yR5ZL$
--------------------------------------------------------------------

_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Reply via email to