Re: [Lsr] New Version for draft-wang-lsr-hbh-process-00

wangyali <wangyali11@huawei.com> Tue, 17 November 2020 10:30 UTC

Return-Path: <wangyali11@huawei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 759AA3A0E8A for <lsr@ietfa.amsl.com>; Tue, 17 Nov 2020 02:30:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=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 iueIkqp9BwlF for <lsr@ietfa.amsl.com>; Tue, 17 Nov 2020 02:30:52 -0800 (PST)
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 C2B5A3A0E84 for <lsr@ietf.org>; Tue, 17 Nov 2020 02:30:51 -0800 (PST)
Received: from fraeml711-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Cb2H15ZRHz67Df6 for <lsr@ietf.org>; Tue, 17 Nov 2020 18:29:01 +0800 (CST)
Received: from fraeml711-chm.china.huawei.com (10.206.15.60) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 17 Nov 2020 11:30:50 +0100
Received: from DGGEML421-HUB.china.huawei.com (10.1.199.38) by fraeml711-chm.china.huawei.com (10.206.15.60) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Tue, 17 Nov 2020 11:30:49 +0100
Received: from DGGEML524-MBX.china.huawei.com ([169.254.1.26]) by dggeml421-hub.china.huawei.com ([10.1.199.38]) with mapi id 14.03.0487.000; Tue, 17 Nov 2020 18:30:46 +0800
From: wangyali <wangyali11@huawei.com>
To: Huaimo Chen <huaimo.chen@futurewei.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] New Version for draft-wang-lsr-hbh-process-00
Thread-Index: Adat8djmk+9JGVIhQXKR+qlyxbtz5wOqvcqj///ZrVA=
Date: Tue, 17 Nov 2020 10:30:45 +0000
Message-ID: <1520992FC97B944A9979C2FC1D7DB0F4050C4062@dggeml524-mbx.china.huawei.com>
References: <1520992FC97B944A9979C2FC1D7DB0F4050519D2@dggeml524-mbx.china.huawei.com> <MN2PR13MB40871F3CD1BC0BE44FD47398F2E20@MN2PR13MB4087.namprd13.prod.outlook.com>
In-Reply-To: <MN2PR13MB40871F3CD1BC0BE44FD47398F2E20@MN2PR13MB4087.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.136]
Content-Type: multipart/alternative; boundary="_000_1520992FC97B944A9979C2FC1D7DB0F4050C4062dggeml524mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/04Gvs9xMWH5pxBq9p3ZMaj12SaU>
Subject: Re: [Lsr] New Version for draft-wang-lsr-hbh-process-00
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Nov 2020 10:30:55 -0000

Hi Huaimo,

Thanks a lot for your review and comments. Please find my responses in line [Yali].

Best regards,
Yali

From: Huaimo Chen [mailto:huaimo.chen@futurewei.com]
Sent: Tuesday, November 17, 2020 12:59 PM
To: wangyali <wangyali11@huawei.com>; lsr@ietf.org
Subject: Re: [Lsr] New Version for draft-wang-lsr-hbh-process-00

Hi Authors,

    The draft describes extensions to IGP for a node to distribute
capabilities of its links. The capability information about
all the links in a network may be used by another entity such as
a controller.

I have following comments:
1). In section 3, the capabilities of a link or a node is represented
by "Processing Action" (refer to Fig. 1 in the draft). Why do you include
"Max EH Len" in the "Processing Action"? It is not a capability.
[Yali] Since the length of IPv6 Extensions Header exceeds the maximum limit the node is capable to process, the packets carried extensions header should be discarded. Hence, "Max EH Len" defined in this draft is used to indicate the maximum length of extension header supported by the Node or Link. So I think it is also a capability.
What's your thoughts?

2). The text describing the format of "Processing Action"
below seems not consistent with the format in Fig. 1.
"... processing action formed of
a tuple of a 1-octet Extension Header Options identifier and 8-bit
Processing Action Flag."
The above text occurs twice in the draft.
[Yali] I'll fix this in the next version. It should be "...processing action formed of a tuple of a 8-bit Processing Action Flag, a 16-bit Services Flag, and a one-octet Maximum Extensions Header Length."

3). It seems that using word "signal" or "signaling" in the draft
is not good. It is better to use another word and rephrase the related text.
[Yali] I will replace word "signal" by "advertise" and also revise the related text. Is it correct?

Best Regards,
Huaimo
________________________________
From: Lsr <lsr-bounces@ietf.org<mailto:lsr-bounces@ietf.org>> on behalf of wangyali <wangyali11@huawei.com<mailto:wangyali11@huawei.com>>
Sent: Thursday, October 29, 2020 9:19 AM
To: lsr@ietf.org<mailto:lsr@ietf.org> <lsr@ietf.org<mailto:lsr@ietf.org>>
Subject: [Lsr] New Version for draft-wang-lsr-hbh-process-00

Hello WG,

Considering the Hop-by-Hop Options header has been used for IOAM [I-D.ietf-ippm-ioam-ipv6-options], Alternate Marking method [I-D.ietf-6man-ipv6-alt-mark], etc., but as specified in RFC8200, the Hop-by-Hop Options header is only examined and processed if it is explicitly configured. In this case, nodes may be configured to ignore the Hop-by-Hop Options header, drop packets containing a Hop-by-Hop Options header, or assign packets containing a Hop-by-Hop Options header to a slow processing path. Thus, the performance measurement does not account for all links and nodes along a path. In addition, packets carrying a Hop-by-Hop Options header may be dropped, which gravely deteriorates network performance.

Therefore, we propose a new draft about IGP extensions for signaling Hop-by-Hop Options header processing action at node and link granularity. Such advertisement is useful for entities (e.g., the centralized controller) to gather each router's processing action for achieving the computation of TE paths that be able to support a specific service encoded in the Hop-by-Hop Options header.

Please let us know your opinion. Questions and comments are very welcome.

Best regards,
Yali


-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org]
Sent: Thursday, October 29, 2020 8:42 PM
To: Tianran Zhou <zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>; Huzhibo <huzhibo@huawei.com<mailto:huzhibo@huawei.com>>; wangyali <wangyali11@huawei.com<mailto:wangyali11@huawei.com>>
Subject: New Version Notification for draft-wang-lsr-hbh-process-00.txt


A new version of I-D, draft-wang-lsr-hbh-process-00.txt has been successfully submitted by Yali Wang and posted to the IETF repository.

Name:           draft-wang-lsr-hbh-process
Revision:       00
Title:          IGP Extensions for Advertising Hop-by-Hop Options Header Processing Action
Document date:  2020-10-29
Group:          Individual Submission
Pages:          10
URL:            https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-wang-lsr-hbh-process-00.txt&amp;data=04%7C01%7Chuaimo.chen%40futurewei.com%7C1b6010e28c9345df423708d87c0d5f8f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637395744183598793%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=tvJH5rnR%2BAj%2FxTTaxxbKJ6z%2F1OKAog3QdCCJnJkKB2I%3D&amp;reserved=0
Status:         https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-wang-lsr-hbh-process%2F&amp;data=04%7C01%7Chuaimo.chen%40futurewei.com%7C1b6010e28c9345df423708d87c0d5f8f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637395744183598793%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=Wt7W0PL8HGI1EaPK8sV92RWIRGXATD0RGx1AhGIH6xk%3D&amp;reserved=0
Htmlized:       https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-wang-lsr-hbh-process&amp;data=04%7C01%7Chuaimo.chen%40futurewei.com%7C1b6010e28c9345df423708d87c0d5f8f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637395744183598793%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=Zmi3lDpE2aNulJxCiyU%2B9XQzv63EPeMo%2BAWVkatiDRE%3D&amp;reserved=0
Htmlized:       https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-wang-lsr-hbh-process-00&amp;data=04%7C01%7Chuaimo.chen%40futurewei.com%7C1b6010e28c9345df423708d87c0d5f8f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637395744183598793%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=m9Z1uy3W4tT73SQod1DpcT%2BU4malMI25xQtNHTSwkdY%3D&amp;reserved=0


Abstract:
   This document extends Node and Link attribute TLVs to Interior
   Gateway Protocols (IGP) to advertise the Hop-by-Hop Options header
   processing action and supported services (e.g.  IOAM Trace Option and
   Alternate Marking) at node and link granularity.  Such advertisements
   allow entities (e.g., centralized controllers) to determine whether
   the Hop-by-Hop Options header and specific services can be supported
   in a given network.





Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


_______________________________________________
Lsr mailing list
Lsr@ietf.org<mailto:Lsr@ietf.org>
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Flsr&amp;data=04%7C01%7Chuaimo.chen%40futurewei.com%7C1b6010e28c9345df423708d87c0d5f8f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637395744183598793%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=Fae4vhjYo1fN5aIkVTTYMlANFCNyH%2FvxkyznvdjL%2B6U%3D&amp;reserved=0