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

Aijun Wang <wangaj3@chinatelecom.cn> Mon, 15 June 2020 02:15 UTC

Return-Path: <wangaj3@chinatelecom.cn>
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 431AE3A0890; Sun, 14 Jun 2020 19:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=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 A7pU8XlWO_av; Sun, 14 Jun 2020 19:15:02 -0700 (PDT)
Received: from chinatelecom.cn (prt-mail.chinatelecom.cn [42.123.76.220]) by ietfa.amsl.com (Postfix) with ESMTP id BBBE83A081C; Sun, 14 Jun 2020 19:14:58 -0700 (PDT)
HMM_SOURCE_IP: 172.18.0.48:23916.61224681
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.75?logid-d4772793cd2c405ca38c6ab82de6ca54 (unknown [172.18.0.48]) by chinatelecom.cn (HERMES) with SMTP id BDFD3280169; Mon, 15 Jun 2020 10:14:00 +0800 (CST)
X-189-SAVE-TO-SEND: 66040164@chinatelecom.cn
Received: from ([172.18.0.48]) by App0024 with ESMTP id d4772793cd2c405ca38c6ab82de6ca54 for ipv6@ietf.org; Mon Jun 15 10:14:40 2020
X-Transaction-ID: d4772793cd2c405ca38c6ab82de6ca54
X-filter-score: filter<0>
X-Real-From: wangaj3@chinatelecom.cn
X-Receive-IP: 172.18.0.48
X-MEDUSA-Status: 0
Sender: wangaj3@chinatelecom.cn
From: Aijun Wang <wangaj3@chinatelecom.cn>
To: ipv6@ietf.org, spring@ietf.org
Date: Mon, 15 Jun 2020 10:13:57 +0800
Message-ID: <000001d642ba$b89f3480$29dd9d80$@chinatelecom.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01D642FD.C6C27480"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdZCuMJHBVRRTak/QdaJrs+4Mzv0gA==
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/toZCUlJiINjT7mlV83ZxBqDpev8>
Subject: [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:15:07 -0000

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-pro
gramming-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