[v6ops] 答复: WGLC for draft-ietf-v6ops-hbh-05

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Wed, 22 November 2023 12:12 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3A5C151061 for <v6ops@ietfa.amsl.com>; Wed, 22 Nov 2023 04:12:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=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=unavailable 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 Jy6tKgdmrkiJ for <v6ops@ietfa.amsl.com>; Wed, 22 Nov 2023 04:12:22 -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 D466CC14CE29 for <v6ops@ietf.org>; Wed, 22 Nov 2023 04:12:21 -0800 (PST)
Received: from lhrpeml100002.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Sb0Nl3r9Dz6JBXM for <v6ops@ietf.org>; Wed, 22 Nov 2023 20:07:19 +0800 (CST)
Received: from canpemm100005.china.huawei.com (7.192.105.21) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Wed, 22 Nov 2023 12:12:18 +0000
Received: from canpemm500008.china.huawei.com (7.192.105.151) by canpemm100005.china.huawei.com (7.192.105.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Wed, 22 Nov 2023 20:12:16 +0800
Received: from canpemm500008.china.huawei.com ([7.192.105.151]) by canpemm500008.china.huawei.com ([7.192.105.151]) with mapi id 15.01.2507.035; Wed, 22 Nov 2023 20:12:16 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Tom Herbert <tom=40herbertland.com@dmarc.ietf.org>, Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] WGLC for draft-ietf-v6ops-hbh-05
Thread-Index: AdoM0SDY1e2b1TxXTGuvdJpDt0odxgFT4kUAAsa/T+A=
Date: Wed, 22 Nov 2023 12:12:16 +0000
Message-ID: <0fdb7e4fb5cd4c5983370f80af24de10@huawei.com>
References: <1d22666296d545a7b36898adf300c700@huawei.com> <CALx6S37g9kyvokw9UpMcbp7M_K9UPUeHFeH654r60+QRAvxq2Q@mail.gmail.com>
In-Reply-To: <CALx6S37g9kyvokw9UpMcbp7M_K9UPUeHFeH654r60+QRAvxq2Q@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.28.73]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/AfQNA0tjz1RhybJYVFYrwpT8Nkg>
Subject: [v6ops] 答复: WGLC for draft-ietf-v6ops-hbh-05
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Nov 2023 12:12:24 -0000

Hi Tom, 

Thank you for your suggestions. 

To me it is a good suggestion to change the title of Section 8 "Requirements" to "Design principles", which also follows the logics among the current related on-going drafts. 

How about we add the following sentences in the paragraph starting with " The maximum length of an HBH Options..." in Section 3 where the draft-ietf-6man-eh-limits is also referenced? 

"Parsing buffers with a limited size are commonly used in router implementations. The parsing buffer contains the headers of a packet that can be processed in the fast path and typically have sizes like 128, 256, 284 bytes."

Best Regards, 
Shuping 



-----邮件原件-----
发件人: v6ops <v6ops-bounces@ietf.org> 代表 Tom Herbert
发送时间: 2023年11月9日 0:51
收件人: Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>
抄送: v6ops@ietf.org
主题: Re: [v6ops] WGLC for draft-ietf-v6ops-hbh-05

Hi,

Thanks for the draft.

Even though it's informational, the requirements listed in section 8 seem to be a bit vague. For instance:

 *  HBH Options need to be designed in a manner so that they don't reduce the probability of packet delivery.

That's good as a general principle, but I'm not sure how useful that is to a protocol developer (what does "designed in a manner" mean?)

Also, section 8 contains only one normative requirement and it's not clear that that is an operational requirement. For the rest of section 8, these seem more like design principles and not requirements, so maybe the section should be titled "Design Principles" or something without the word "requirements"

In section 3 or 6, it would be good to mention parsing buffers with a limited size that are commonly used in router implementations. The parsing buffer contains the headers of a packet that can be processed in the fast path and typically have sizes like 128, 256, 284 bytes.
It's problematic for routers when the headers a router wants to inspect don't fit into the parsing buffer (in particular, if they need to access the transport layer to perform port filtering). In turn, for extension headers, including HBH, there is motivation for the sender to limit their size to increase the probability of successful delivery (ietf-6man-eh-limits suggests defines limits with suggested defaults)

Tom


On Wed, Nov 1, 2023 at 7:40 AM Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org> wrote:
>
> Hi folks,
>
>
>
> Because 6man has issued WGLC for draft-ietf-6man-hbh-processing, this message starts the WGLC for its companion draft-ietf-v6ops-hbh-05. Because next week is IETF 118, to allow sufficient time for people to review and comment, the WGLC will end on Nov 22.  Thank you.
>
>
>
> Ron and XiPeng
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops