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

Xiejingrong <xiejingrong@huawei.com> Wed, 10 July 2019 02:54 UTC

Return-Path: <xiejingrong@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 CEFF8120131 for <spring@ietfa.amsl.com>; Tue, 9 Jul 2019 19:54:45 -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 vGCGY-N7vATh for <spring@ietfa.amsl.com>; Tue, 9 Jul 2019 19:54:44 -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 D19B31200E6 for <spring@ietf.org>; Tue, 9 Jul 2019 19:54:43 -0700 (PDT)
Received: from LHREML710-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 67467982135153556DF6 for <spring@ietf.org>; Wed, 10 Jul 2019 03:54:41 +0100 (IST)
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 10 Jul 2019 03:54:40 +0100
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 10 Jul 2019 03:54:40 +0100
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Wed, 10 Jul 2019 03:54:40 +0100
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Wed, 10 Jul 2019 10:54:29 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: Comments on <draft-ietf-spring-srv6-network-programming-01>
Thread-Index: AdU2yLeIH/gcBcBYRKuUnmoAo9B4eQ==
Date: Wed, 10 Jul 2019 02:54:29 +0000
Message-ID: <16253F7987E4F346823E305D08F9115AAB8DC899@nkgeml514-mbx.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.111.217.214]
Content-Type: multipart/alternative; boundary="_000_16253F7987E4F346823E305D08F9115AAB8DC899nkgeml514mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/6h67pCyux2ZdVSbJWAsZamkw2go>
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: Wed, 10 Jul 2019 02:54:46 -0000

Hi,

I remember there had been lots of discussions on the list about two points,
One is the definition of ENH, the other is the use of Next Header 59.
Seems like this rev doesn't accept any of them, but make them clear in text.
They work for me.

But one point I am even more confused:
   The SRv6 Endpoint Behavior numbers are maintained by the working
   group until the RFC is published.  Note to the RFC Editor: Remove
   this paragraph before publication.

Why does this document say to create a new registry, but hold the Behavior numbers privately ?
We need the IANA registry be created and allocation from the registry.

Thanks
Jingrong