Re: [v6ops] Call for adoption: draft-peng-v6ops-hbh

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Sat, 11 September 2021 04:01 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 ECD9F3A2FA9 for <v6ops@ietfa.amsl.com>; Fri, 10 Sep 2021 21:01:06 -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=unavailable 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 608hhlAQFTBd for <v6ops@ietfa.amsl.com>; Fri, 10 Sep 2021 21:01:02 -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 6ED323A2FAC for <v6ops@ietf.org>; Fri, 10 Sep 2021 21:01:02 -0700 (PDT)
Received: from fraeml704-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4H5zWS2RBTz67L3Y; Sat, 11 Sep 2021 11:59:00 +0800 (CST)
Received: from dggeml708-chm.china.huawei.com (10.3.17.138) by fraeml704-chm.china.huawei.com (10.206.15.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Sat, 11 Sep 2021 06:00:58 +0200
Received: from dggeml757-chm.china.huawei.com (10.1.199.137) by dggeml708-chm.china.huawei.com (10.3.17.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Sat, 11 Sep 2021 12:00:57 +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; Sat, 11 Sep 2021 12:00:56 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Call for adoption: draft-peng-v6ops-hbh
Thread-Index: AdelnWfJ3fGWLYNIQiK+F0VNim+BZf//vMOA//2caFA=
Date: Sat, 11 Sep 2021 04:00:56 +0000
Message-ID: <bbeab7d9e9c140a4bc2c24aeed442245@huawei.com>
References: <BL0PR05MB5316375D7503A85477DF874AAED59@BL0PR05MB5316.namprd05.prod.outlook.com> <ca24a2d5-d347-7a7a-8f5a-55bd53dd4525@gmail.com>
In-Reply-To: <ca24a2d5-d347-7a7a-8f5a-55bd53dd4525@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.77.96]
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/N2DJPYdRzjcHCE8hkae70ZTipAc>
Subject: Re: [v6ops] Call for adoption: draft-peng-v6ops-hbh
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: Sat, 11 Sep 2021 04:01:07 -0000

Dear Brian, 

Our main purpose of this work, as we presented in the IETF meetings, is to ultimately 
1. Break the endless cycle that resulted in HBH to become a DOS vector.
2. Enable the HBH options header to be utilized in a safe/secure way without impacting the management plane.
3. Ease the deployments of the new HBH based network services in a multi-vendor/operator’s scenario that can now be deployed without operational impact.

This document acts as a requirement document and not a solution document so the purpose is to describe the current state and what needs to be fixed.

As you pointed out, we agree that the purpose is not very clear now, we will extend the introduction section that currently has a small paragraph on the purpose of this draft, and add more information to make it more clear. It will also be reflected in the abstract. 

Thank you for your comments to help us to improve the draft.

Best regards, 
Shuping 



> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Brian E
> Carpenter
> Sent: Friday, September 10, 2021 5:09 AM
> To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; v6ops@ietf.org
> Subject: Re: [v6ops] Call for adoption: draft-peng-v6ops-hbh
> 
> I'm afraid I don't understand at all what this draft proposes. To be explicit:
> 
> >  8. Migration Strategies
> 
> Migration from what to what?
> 
> > 1. The source of the HBH options header encapsulation.The information to
> be carried in the HBH options header needs to be first categorized and
> encapsulated into either control options or forwarding options, and then
> encapsulated in different packets.
> ...
> > The edge nodes should check whether the packet contains an HBH header
> with control or forwarding option.
> What different packets? How are control and forwarding options
> distinguished? Is this proposal suggesting two kinds of HBH option? If so it
> belongs in 6man. If not, I have no idea what it actually suggests.
> 
> Regards
>    Brian
> 
> On 10-Sep-21 05:10, Ron Bonica wrote:
> > Folks,
> >
> >
> >
> > This message initiates a call for adoption for draft-peng-v6ops-hbh
> (https://datatracker.ietf.org/doc/draft-peng-v6ops-hbh/
> <https://datatracker.ietf.org/doc/draft-peng-v6ops-hbh/>).
> >
> >
> >
> > Please post comments by September 24, 2021.
> >
> >
> >
> >
>                   Fred and Ron
> >
> >
> >
> >
> > Juniper Business Use Only
> >
> >
> > _______________________________________________
> > 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