Re: [spring] About the upper layer header processing in RFC8754(SRH)

"Xiejingrong (Jingrong)" <xiejingrong@huawei.com> Mon, 15 June 2020 02:29 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 853803A0891; Sun, 14 Jun 2020 19:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 gfcuLyk5Ndtr; Sun, 14 Jun 2020 19:29:26 -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 B24373A087F; Sun, 14 Jun 2020 19:29:25 -0700 (PDT)
Received: from lhreml708-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id C88D23A5A56D0FB4B1B0; Mon, 15 Jun 2020 03:29:21 +0100 (IST)
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by lhreml708-chm.china.huawei.com (10.201.108.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Mon, 15 Jun 2020 03:29:21 +0100
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by nkgeml707-chm.china.huawei.com (10.98.57.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 15 Jun 2020 10:29:18 +0800
Received: from nkgeml705-chm.china.huawei.com ([10.98.57.154]) by nkgeml705-chm.china.huawei.com ([10.98.57.154]) with mapi id 15.01.1913.007; Mon, 15 Jun 2020 10:29:18 +0800
From: "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>
To: Aijun Wang <wangaj3@chinatelecom.cn>, "ipv6@ietf.org" <ipv6@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: About the upper layer header processing in RFC8754(SRH)
Thread-Index: AdZCuMJHBVRRTak/QdaJrs+4Mzv0gAAAwI2A
Date: Mon, 15 Jun 2020 02:29:18 +0000
Message-ID: <f677afa195154a97bd66e5c9688b8734@huawei.com>
References: <000001d642ba$b89f3480$29dd9d80$@chinatelecom.cn>
In-Reply-To: <000001d642ba$b89f3480$29dd9d80$@chinatelecom.cn>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.118]
Content-Type: multipart/alternative; boundary="_000_f677afa195154a97bd66e5c9688b8734huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/WW9d_QBGamAti8pOC_EPUrH0iGY>
Subject: Re: [spring] About the upper layer header processing in RFC8754(SRH)
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: Mon, 15 Jun 2020 02:29:28 -0000

Hi Aijun,
Very good catch!
I think the 4.3.1.2 need to be updated !
I would like to propose some text (maybe later today) for RFC8754 4.3.1.2, as well as some other text in SRv6-PGM section 4.1 (and some related sections) I have observed  about the Upper-layer processing for further discussion.

Thanks
Jingrong


From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Aijun Wang
Sent: Monday, June 15, 2020 10:14 AM
To: ipv6@ietf.org; spring@ietf.org
Subject: About the upper layer header processing in RFC8754(SRH)

Hi, Folks:
RFC8754(SRH) section 4.3.1.2(https://tools.ietf.org/html/rfc8754#section-4.3.1.2) describes the process of upper layer header as the followings:
IF (Upper-layer Header is IPv4 or IPv6) and
       local configuration permits {
     Perform IPv6 decapsulation
     Resubmit the decapsulated packet to the IPv4 or IPv6 module
   }
   ELSE {
   ......
}
And in network programming draft section 9.1(https://datatracker.ietf.org/doc/html/draft-ietf-spring-srv6-network-programming-15#section-9.1), one new Ethernet Next Header Type(143) is proposed.

Although the detail process of this new next header are described in the network program draft,  does it need to update the section 4.3.1.2 of RFC8754 to reflect the process of new header type(143)?

Best Regards

Aijun Wang
China Telecom