Re: [spring] 6man w.g. last call for <draft-ietf-6man-spring-srv6-oam>

Hello Ole and all,

I re-read this version again with the following comments for the WGLC.

1. Section 4.2.2.2, the penultimate bullet.
The sentence "The traceroute process at node N4 checks if its local SID (B:2:C31) is locally programmed" should be "The traceroute process at node N4 checks if its local SID (B:4:C52) is locally programmed".

2. Requirements Language
[RFC8174] should be added as a nomative reference.

3. Section 3.5 SRH TLV
This section only tells us SRH TLV is defined in ietf-6man-segment-routing-header, nothing else. I think this section should be removed.

4. Section 4.3 Monitoring of SRv6 Paths
This section is a story or a use case. No specification is defined in this section. It should be removed or moved to an appendix.

5. Section 2.1 Abbreviations
ICMPv6 is defined in RFC4443. Why does this draft use it as multi-part ICMPv6 defined in RFC4884. This is confusing.

6. Section 4.1.3 Error Reporting
ICMPv6 is defined in ICMPv6 related RFCs. Does this section want to extend ICMPv6? If yes, I don't think this doc is the appropriate place. If no, why do we need this section? to emphasize the things that a router should do?

With all the commets above, I don't think this doc is mature enough to pass the WGLC.

Best Regards,
Zhenqiang Li

li_zhenqiang@hotmail.com

From: Ole Troan
Date: 2019-12-05 04:53
To: 6man WG; SPRING WG
CC: 6man Chairs
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://datatracker.ietf.org/doc/draft-ietf-6man-spring-srv6-oam/

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
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------