[spring] Comments on draft-ietf-spring-srv6-network-programming-01

Zhuangshunwan <zhuangshunwan@huawei.com> Thu, 11 July 2019 09:17 UTC

Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A81DA1202B9; Thu, 11 Jul 2019 02:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 zvBM3YmYh7yc; Thu, 11 Jul 2019 02:17:00 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 59C94120222; Thu, 11 Jul 2019 02:17:00 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id C5E12EC77C9DFE276A3E; Thu, 11 Jul 2019 10:16:57 +0100 (IST)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 11 Jul 2019 10:16:56 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.134]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Thu, 11 Jul 2019 17:16:50 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: "draft-ietf-spring-srv6-network-programming@ietf.org" <draft-ietf-spring-srv6-network-programming@ietf.org>
CC: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: Comments on draft-ietf-spring-srv6-network-programming-01
Thread-Index: AdU3xVHuiYvAOmOkShGrHwiue53NMQ==
Date: Thu, 11 Jul 2019 09:16:50 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858E5BFB5F4@NKGEML515-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.202.166]
Content-Type: multipart/alternative; boundary="_000_19AB2A007F56DB4E8257F949A2FB9858E5BFB5F4NKGEML515MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/qPLGH1EOWh5yR-waq8bdfTq_ocY>
Subject: [spring] Comments on draft-ietf-spring-srv6-network-programming-01
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2019 09:17:03 -0000

Hi all,

I have read this document again and again, and think it is a good guide to implantation.
Thanks to the authors for introducing this very useful draft.

Few comments:

#1
2.  Terminology
...
   The effective next-header (ENH) is the next-header field of the IP
   header when no SRH is present, or is the next-header field of the
   last SRH.

[Shunwan] It's better to change "the next-header field of the IP header ... " to "the next-header field of the IPv6  header ..." .

#2
4.7.  End.DT2M: Decapsulation and L2 table flooding

   The "Endpoint with decapsulation and specific L2 table flooding"
   function (End.DT2M for short) is a variant of the endpoint function.

   This function may take an argument: "Arg.FE2".  It is an argument
   specific to EVPN ESI filtering.  It is used to exclude a specific OIF
   (or set of OIFs) from L2 table T flooding.

[Shunwan]
This section says: "It is an argument specific to EVPN ESI filtering.  "
Question: Can it also be an argument specific to EVPN E-Tree [RFC8317] Leaf filtering?
If I understand it correctly , the specifications defined in this section can also be easily applied to EVPN E-Tree Leaf filtering.

Thanks,
Shunwan