Comments on draft-ietf-6man-spring-srv6-oam-03

xiao.min2@zte.com.cn Mon, 23 March 2020 05:52 UTC

Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 104383A07B3 for <ipv6@ietfa.amsl.com>; Sun, 22 Mar 2020 22:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NHHJo3oac1Lt for <ipv6@ietfa.amsl.com>; Sun, 22 Mar 2020 22:52:46 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90AB93A07AB for <6man@ietf.org>; Sun, 22 Mar 2020 22:52:46 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id 26D7A670BD8F865278A3; Mon, 23 Mar 2020 13:52:44 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl1.zte.com.cn with SMTP id 02N5qbC0079148; Mon, 23 Mar 2020 13:52:37 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp01[null]) by mapi (Zmail) with MAPI id mid201; Mon, 23 Mar 2020 13:52:37 +0800 (CST)
Date: Mon, 23 Mar 2020 13:52:37 +0800
X-Zmail-TransId: 2af95e784ea5cbce451b
X-Mailer: Zmail v1.0
Message-ID: <202003231352376196257@zte.com.cn>
Mime-Version: 1.0
From: xiao.min2@zte.com.cn
To: zali@cisco.com
Cc: 6man@ietf.org
Subject: Comments on draft-ietf-6man-spring-srv6-oam-03
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 02N5qbC0079148
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/eJE5QIZKX6xj6_iREafPSWYFi7w>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2020 05:52:50 -0000

Hi Zafar,






I have several comments on draft-ietf-6man-spring-srv6-oam-03 as below.


In section 4.1.1 and 4.2.2.1, several descriptions of node behavior on "performs the standard SRH processing" and "executes the END.X function" can be improved.


For example, in section 4.1.1, I propose to change the description of Node N2 behavior.


OLD

Node N2, which is an SRv6 capable node, performs the standard SRH processing.  Specifically, it executes the END.X function (B:2:C31) and forwards the packet on link3 to N3.

NEW

Node N2, which is an SRv6 capable node, performs the standard SRv6 SID and SRH processing.  Specifically, it executes the END.X function (B:2:C31) and forwards the packet on link3 to N3.

As I understand, the behavior of executing the END.X function is not part of SRH processing, but part of SRv6 SID (IPv6 DA) processing, right?

In section 4.1.1, I propose to insert one more sentence clarifyiing the behavior of the egress SRv6 capable node.

OLD

Similarly, the egress node (IPv6 classic or SRv6 capable) does not require any change to process the ICMPv6 echo request.

NEW

Similarly, the egress node (IPv6 classic or SRv6 capable) does not require any change to process the ICMPv6 echo request, and there is no difference in processing of the ICMPv6 echo request at an IPv6 classic node and an SRv6 capable node.

This inserted sentence is almost the same with thatBes is present in section 4.2.1 as "There is no difference in processing of the traceroute probe at an IPv6 classic node and an SRv6 capable node." The reason is that I was asked whether the ICMPv6 echo reply would carry SRH when the egress node is SRv6 capable, as I understand , the answer is NO, but I couldn't find explicit text in the current draft.

In section 4.2.2.1, s/hop count/hop limit/g, s/hop-count/hop-limit/g

In section 4.2.2.1, s/2001:DB8:3:4::41/2001:DB8:3:4:41; In section 4.2.1, s/2001:DB8:4:5::52::/2001:DB8:4:5:52::/g, s/2001:DB8:3:4::41/2001:DB8:3:4:41. In addition, the displayed interface IPv6 addresses in Figure 3 have the last ::, but that in Figure 4 have no the last ::, shouldn't they be the same?




Best Regards,

Xiao Min