Re: [spring] FW: New Version Notification for draft-ietf-6man-spring-srv6-oam-05.txt

Thank you Zafar.  As we discussed, these changes address my concerns.
Yours,
Joel

On 6/12/2020 12:35 PM, Zafar Ali (zali) wrote:
> Dear WG:
> 
> We have just posted 
> https://www.ietf.org/internet-drafts/draft-ietf-6man-spring-srv6-oam-05.txt. 
> 
> 
> This version addresses comments received during the interim meeting and 
> all outstanding comments.
> 
> Since the interim meeting:
> 
>   * The authors had WebEx calls with Joel M. Halpern and Bob Hinden.
>   * The authors also had a WebEx with Greg Mirsky.
>   * During these calls, the author went over their comments and walked
>     over how the proposed diffs address their feedback. 
> 
> The authors thank Joel, Greg, Loa, Bob and the WG for all the comments.
> 
> The authors believe that the diffs address their and other outstanding 
> comments from the WG.
> 
> How the diffs address the comments is detailed in the following:
> 
>   * Joel Halpern comment from the interim meeting,
>     https://datatracker.ietf.org/doc/minutes-interim-2020-6man-01-202003310730/.
>     Specifically, "Joel Halpern: You said you added illustrations to
>     address my comments. You did add illustrations, but the description
>     does not address my comment. The document needs to address what the
>     router actually has to do when the O bit is set. The text does not
>     describe this."
>       o Section 2.1.1. O-flag Processing has been enhanced to address
>         Joel's comments. It has been reviewed with Joel and Bob during
>         the WebEx meeting with them. The author believes the changes
>         address Joel's comments. 
>   * Greg Mirsky's comment from the interim meeting,
>     https://datatracker.ietf.org/doc/minutes-interim-2020-6man-01-202003310730/.
>     Specifically, "Greg Mirsky: I did not read the latest version, so I
>     haven't seen the latest changes. I think your interpretation of RFC
>     7799 is incorrect. O-bit, according to the definition or active,
>     passive, and "in-between." OAM would be an example of the hybrid OAM
>     method. I also think what you are trying to achieve with O-bit is
>     achievable with current iOAM (in-situ OAM). "
>       o The terminology now uses the hybrid OAM mechanism. Section
>         2.1.1. (O-flag Processing) Section 3.3 (A Controller-Based
>         Hybrid OAM Using O-flag) has been enhanced to address Greg's
>         comments. The diffs have been discussed with Greg during the
>         WebEx meeting with them. The author believes the changes address
>         Greg's comments. 
>   * There was an outstanding comment from Greg in
>     https://mailarchive.ietf.org/arch/msg/ipv6/esi3EWdjWMEu9zSP-pjzxI2gEmw/.
>     Specifically, Greg asked: Isn't using assigned by IANA port number
>     sufficient to identify active IP OAM packets? Wouldn't the same be
>     applicable in SRv6 OAM? Removed END.OP SID and the associated
>     changes in the illustration section to address this comment.
>   * The new version addresses pending comments from Loa Anderson by a
>     rewrite of the introduction and abstract. All other comments from
>     https://mailarchive.ietf.org/arch/msg/ipv6/LKsWbnA0aWYem4AbHWrUURNd-3c/ has
>     been already addressed.
>   * Migrated addresses used for illustration to IPv6 addresses reserved
>     for documentation.
>   * Fixed .xml file, as per Bob’s comment.
>   * Fixed IDnit issues.
>   * Misc. editorial changes including illustration enhancement in 3.4
>     (Monitoring of SRv6 Paths)
> 
> Thanks
> 
> Regards … Zafar (on behalf of the co-authors and contributors)
> 
> *From: *"internet-drafts@ietf.org" <internet-drafts@ietf.org>
> *Date: *Friday, June 12, 2020 at 12:27 PM
> *To: *Daniel Voyer <daniel.voyer@bell.ca>, Mach Chen 
> <mach.chen@huawei.com>, "Clarence Filsfils (cfilsfil)" 
> <cfilsfil@cisco.com>, Satoru Matsushima 
> <satoru.matsushima@g.softbank.co.jp>, "Zafar Ali (zali)" <zali@cisco.com>
> *Subject: *New Version Notification for 
> draft-ietf-6man-spring-srv6-oam-05.txt
> 
> A new version of I-D, draft-ietf-6man-spring-srv6-oam-05.txt
> 
> has been successfully submitted by Zafar Ali and posted to the
> 
> IETF repository.
> 
> Name:draft-ietf-6man-spring-srv6-oam
> 
> Revision:05
> 
> Title:Operations, Administration, and Maintenance (OAM) in Segment 
> Routing Networks with IPv6 Data plane (SRv6)
> 
> Document date:2020-06-12
> 
> Group:6man
> 
> Pages:20
> 
> URL: 
> https://www.ietf.org/internet-drafts/draft-ietf-6man-spring-srv6-oam-05.txt
> 
> Status: https://datatracker.ietf.org/doc/draft-ietf-6man-spring-srv6-oam/
> 
> Htmlized: https://tools.ietf.org/html/draft-ietf-6man-spring-srv6-oam-05
> 
> Htmlized: 
> https://datatracker.ietf.org/doc/html/draft-ietf-6man-spring-srv6-oam
> 
> Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-spring-srv6-oam-05
> 
> Abstract:
> 
>     This document describes how the existing IPv6 OAM mechanisms can be
> 
>     used in an SRv6 network.  The document also introduces enhancements
> 
>     for controller-based OAM mechanisms for SRv6 networks.
> 
> Please note that it may take a couple of minutes from the time of submission
> 
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
> 