[spring] Question of SRH.Last_entry=0 in Reduced mode

Huzhibo <huzhibo@huawei.com> Wed, 29 June 2022 01:09 UTC

Return-Path: <huzhibo@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 1C65BC159493 for <spring@ietfa.amsl.com>; Tue, 28 Jun 2022 18:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vff4iiXQT7bT for <spring@ietfa.amsl.com>; Tue, 28 Jun 2022 18:09:53 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91EC9C14CF14 for <spring@ietf.org>; Tue, 28 Jun 2022 18:09:53 -0700 (PDT)
Received: from fraeml745-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LXjxH3Vgrz6866J for <spring@ietf.org>; Wed, 29 Jun 2022 09:07:31 +0800 (CST)
Received: from canpemm100010.china.huawei.com (7.192.104.38) by fraeml745-chm.china.huawei.com (10.206.15.226) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 29 Jun 2022 03:09:46 +0200
Received: from canpemm500009.china.huawei.com (7.192.105.203) by canpemm100010.china.huawei.com (7.192.104.38) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 29 Jun 2022 09:09:44 +0800
Received: from canpemm500009.china.huawei.com ([7.192.105.203]) by canpemm500009.china.huawei.com ([7.192.105.203]) with mapi id 15.01.2375.024; Wed, 29 Jun 2022 09:09:44 +0800
From: Huzhibo <huzhibo@huawei.com>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: Question of SRH.Last_entry=0 in Reduced mode
Thread-Index: AdiLVIBKnb5cy0HxQCC6Y57UeOaDOw==
Date: Wed, 29 Jun 2022 01:09:44 +0000
Message-ID: <e9b50f7f389749b39579acc14cdda959@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.45]
Content-Type: multipart/alternative; boundary="_000_e9b50f7f389749b39579acc14cdda959huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/6fZkUuIsY169CNnjqxgP4aj85To>
Subject: [spring] Question of SRH.Last_entry=0 in Reduced mode
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
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, 29 Jun 2022 01:09:58 -0000

Hi SPRING,

I have a simple question: Do we allow to have empty Segment list in SRH?   For instance, only carry common SRH header(8 Bytes) or carry the Common header with option TLV without any SID.

According to the definition of RFC8754[1], "TLVs are present when the Hdr Ext Len is greater than (Last Entry+1)*2".

In reduced mode, if we only have one single SRv6 SID or one single CSID container, the single SRv6 SID/CSID container will be put in the DA and no SID will be carried in the SRH.

In this case, we will meet some errors:

1.       the node will not process the TLV if the length of TLV is longer that (0+1)*2.

2.       the node cannot locate the correct beginning of the TLV because no matter 1 SID or 0 SID in the SRH, the last entry will be 0 in both cases.

We may suggest to disable reduced mode and encode the SID in the SRH when only one SID/CSID container in the SRH, so that the node can process the TLV(HMAC, etc.) correctly.

Thoughts?

Zhibo

[1]. https://datatracker.ietf.org/doc/html/rfc8754#section-2