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

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Thu, 23 November 2023 07:31 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id AEB73C14F749 for <v6ops@ietfa.amsl.com>; Wed, 22 Nov 2023 23:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.205
X-Spam-Status: No, score=-4.205 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id G_wbNhk6VJ0m for <v6ops@ietfa.amsl.com>; Wed, 22 Nov 2023 23:31:19 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FF80C14CF13 for <v6ops@ietf.org>; Wed, 22 Nov 2023 23:31:19 -0800 (PST)
Received: from lhrpeml500006.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SbVCj6RP3z6D8WQ for <v6ops@ietf.org>; Thu, 23 Nov 2023 15:31:13 +0800 (CST)
Received: from canpemm500008.china.huawei.com ( by lhrpeml500006.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Thu, 23 Nov 2023 07:31:15 +0000
Received: from canpemm500008.china.huawei.com ( by canpemm500008.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Thu, 23 Nov 2023 15:31:13 +0800
Received: from canpemm500008.china.huawei.com ([]) by canpemm500008.china.huawei.com ([]) with mapi id 15.01.2507.035; Thu, 23 Nov 2023 15:31:13 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Nick Hilliard <nick@foobar.org>
CC: Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] WGLC for draft-ietf-v6ops-hbh-05
Thread-Index: AdoM0SDY1e2b1TxXTGuvdJpDt0odxv//fVEA//7GLsCAIfUUAP/+HqOw
Date: Thu, 23 Nov 2023 07:31:13 +0000
Message-ID: <9bf509068f794962b313602f3e4abfbb@huawei.com>
References: <1d22666296d545a7b36898adf300c700@huawei.com> <a8530e08-93d7-e7ce-526f-6a7066663eb1@foobar.org> <14aeaa37e9c44e628f701f47515fb463@huawei.com> <03b3a701-b844-b2f1-6116-a5d784be2810@foobar.org>
In-Reply-To: <03b3a701-b844-b2f1-6116-a5d784be2810@foobar.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
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/7e1-tFX7-4u4gs1wvoEEkLTKl1o>
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: Thu, 23 Nov 2023 07:31:23 -0000

Hi Nick, 

We will address your comments item by item this time. Last time I explained our reasons of having the existing structure and expressed that we are open to changes but no further and other suggestions, so we keep the draft as it is. We will update the draft and make a new version. Thank you!

Best Regards, 

发件人: Nick Hilliard <nick@foobar.org> 
发送时间: 2023年11月22日 18:42
收件人: Pengshuping (Peng Shuping) <pengshuping@huawei.com>
抄送: Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>; v6ops@ietf.org
主题: Re: [v6ops] WGLC for draft-ietf-v6ops-hbh-05

Hi Shuping,

I read your previous response, and waited for a document update which happened a number of weeks later. The only change between -03 and -04 was to introduce a reference to rfc9098:


This change, and your email don't address any of the structural issues in draft-ietf-v6ops-hbh, and all of the items are still essentially outstanding.


Pengshuping (Peng Shuping) wrote on 02/11/2023 01:40:
> Hi Nick,
> Please find our last response to your comments. You did not reply back, so we believe that your concerns have been resolved.
> https://mailarchive.ietf.org/arch/msg/v6ops/Oc1ubq5gmIRO6ctzzmescCrYL3
> k/
> Best Regards,
> Shuping
> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Nick Hilliard
> Sent: Wednesday, November 1, 2023 10:51 PM
> To: Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>
> Cc: v6ops@ietf.org
> Subject: Re: [v6ops] WGLC for draft-ietf-v6ops-hbh-05
> Xipengxiao wrote on 01/11/2023 14:40:
>> Because 6man has issued WGLC for draft-ietf-6man-hbh-processing, this 
>> message starts the WGLC for its companion draft-ietf-v6ops-hbh-05 
>> <https://datatracker.ietf.org/doc/draft-ietf-v6ops-hbh/>. 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.
> I've made a number of comments on various versions of this ID, but none of the concerns I've raised have been addressed adequately by the document authors. On this basis, I don't believe that this document should be published as an RFC.
> Nick
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops