Re: [v6ops] I-D Action: draft-ietf-v6ops-hbh-00.txt

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Tue, 12 October 2021 00:48 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 304A63A0820 for <v6ops@ietfa.amsl.com>; Mon, 11 Oct 2021 17:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 U0Y0V7elYDoS for <v6ops@ietfa.amsl.com>; Mon, 11 Oct 2021 17:48:39 -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 1756B3A0768 for <v6ops@ietf.org>; Mon, 11 Oct 2021 17:48:39 -0700 (PDT)
Received: from fraeml737-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4HSxm73R2Tz67b1p for <v6ops@ietf.org>; Tue, 12 Oct 2021 08:45:43 +0800 (CST)
Received: from dggeml757-chm.china.huawei.com (10.1.199.137) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2308.8; Tue, 12 Oct 2021 02:48:35 +0200
Received: from dggeml757-chm.china.huawei.com (10.1.199.137) by dggeml757-chm.china.huawei.com (10.1.199.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Tue, 12 Oct 2021 08:48:33 +0800
Received: from dggeml757-chm.china.huawei.com ([10.1.199.137]) by dggeml757-chm.china.huawei.com ([10.1.199.137]) with mapi id 15.01.2308.008; Tue, 12 Oct 2021 08:48:33 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-hbh-00.txt
Thread-Index: AQHXvr88z33bh38rdUi0V0vJo/4/66vOhrHg
Date: Tue, 12 Oct 2021 00:48:33 +0000
Message-ID: <079aee25ef4841b8bcda81e1a651d6b1@huawei.com>
References: <163397062241.17461.12937788911173662943@ietfa.amsl.com>
In-Reply-To: <163397062241.17461.12937788911173662943@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.169.151]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9R5aQ5j3iNRIDDQ7WEd9Eh45xoY>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-hbh-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 12 Oct 2021 00:48:45 -0000

Hi all, 

The new version of this draft has been uploaded. Many thanks for all the comments and suggestions we received! 

The main changes we have made are the followings,

1.	The title is changed to avoid the misleading towards a solution draft. 
2.	The purpose of this draft is further clarified in both the abstract and the introduction sections. 
3.	The scope of this draft is also clarified in section 2. 
4.	Necessary reference is added.
5.	Directly quote the specifications in the existing RFCs wherever are suitable. 
6.	Requirements in Section 7 are updated according to the received comments but still need more work which will be conducted in the later versions. 
7.	Section 8 is significantly changed instead of being completely deleted since we believe the migration is also very important to consider. 
8.	New sections on other network scenarios are still not yet added. We will work on them in the later versions. 

More work are still needed, and we will continue to working on this draft and keep improving it. Your comments and suggestions are always welcomed. 

Thank you! 

Best regards, 
Shuping

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Tuesday, October 12, 2021 12:44 AM
> To: i-d-announce@ietf.org
> Cc: v6ops@ietf.org
> Subject: [v6ops] I-D Action: draft-ietf-v6ops-hbh-00.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the IPv6 Operations WG of the IETF.
> 
>         Title           : Operational Issues with Processing of the
> Hop-by-Hop Options Header
>         Authors         : Shuping Peng
>                           Zhenbin Li
>                           Chongfeng Xie
>                           Zhuangzhuang Qin
>                           Gyan Mishra
> 	Filename        : draft-ietf-v6ops-hbh-00.txt
> 	Pages           : 14
> 	Date            : 2021-10-09
> 
> Abstract:
>    This document describes the processing of the Hop-by-Hop Options
>    Header (HBH) in today's routers in the aspects of standards
>    specification, common implementations, and default operations.  This
>    document outlines the reasons why the Hop-by-Hop Options Header is
>    rarely utilized in current networks.  In addition, this document
>    describes how the HBH could be used as a powerful mechanism allowing
>    deployment and operations of new services requiring a more optimized
>    way to leverage network resources of an infrastructure.  The Hop-by-
>    Hop Options Header is taken into consideration by several network
>    operators as a valuable container for carrying the information
>    facilitating the introduction of new services.  The purpose of this
>    draft is to document the reasons why the HBH is rarely used within
>    networks and to define a proper list of requirements aiming to allow
>    a better leverage of the HBH capability.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-hbh/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-hbh-00
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops