IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 11 September 2021 21:38 UTC

Return-Path: <brian.e.carpenter@gmail.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 F3E643A0E3F for <v6ops@ietfa.amsl.com>; Sat, 11 Sep 2021 14:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 65uH-MfC63cJ for <v6ops@ietfa.amsl.com>; Sat, 11 Sep 2021 14:38:24 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31B8C3A0E39 for <v6ops@ietf.org>; Sat, 11 Sep 2021 14:38:24 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id m26so5197258pff.3 for <v6ops@ietf.org>; Sat, 11 Sep 2021 14:38:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=Ot/IZruP7tqmXZ8O5VgV++34z60QGx/itm48YZvbASg=; b=RDqd8YYZAI3Ihja17auqqKmY29rtLA0JEvIsemo5zGdNs983qXk4ZeF/p/PJm859Xe Vud+HAJ7IIHNCSFLYU5Uro6fpNdjRWzt6Zq8Aemup6o6uYoJLt8jK0wJpGXd9DUoxdJc FD30Ic/z13v2q4Di0e0RyqpKYZ/c/3Rti5ZrjmcOOfs/yUqKQTwfjO7GCttgNTnAdu8Q U+Z+W9mqTG0t1yxEfC0tcbxOL6S9n6/tpbzqC4TWpCl6a6B6zrYBpR6TL2awgzhj74Fa 372/662HS6Chc6TzUsSWmED5xVcmeaLmdUHnEHFqCmjMs8LPMmKcxzh2JTJR/220kJC8 YsjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Ot/IZruP7tqmXZ8O5VgV++34z60QGx/itm48YZvbASg=; b=C8xIYUaRecWmfSFos537dh+X6m/yutobCGF5f52/7KH5zEytByiti5EcG5+Z2ddA8w 2Tqj4ke/XNqwrB8fyUaYRUZH7cFsYFKHlwlonh1FnB9LhzJs8PRpOxOHtAplDL5t367N S4vqyAG/mYwJJdcFNCXdzZ89dLR2yxQmYMhbDtPUKKVtyukBGj/fWo5qsqt8BxEico8l /NgQJ+odIp23Y5DF2vcAueU2eTBhUUhZyy/pHlC3vLMJ692RK7efjWJo4zY/16ozKmYy nqDl/r8GYkqxV/OBG/YCWZyatUcxGuKHiMf/jwQ/WxByei4p9wvD9eNS6RXwLbNnvGSw 1uRw==
X-Gm-Message-State: AOAM5335LR4pNfHWVHKpsQ3NqqPvTZXbAjsdgbNv3tgYq15hhEYGcvtA w6pYBSfjv05c1KH2G+JaMjhO6p9dFrZxZg==
X-Google-Smtp-Source: ABdhPJy+FOS6EZmUSoPfC48zA7uFRAm9NTRZvroeC3ERwGTTJf4YHlMvt/l4SeTXE/ilz3dEjDH+mA==
X-Received: by 2002:aa7:8e8f:0:b0:416:3e2d:9c2d with SMTP id a15-20020aa78e8f000000b004163e2d9c2dmr3933875pfr.71.1631396302318; Sat, 11 Sep 2021 14:38:22 -0700 (PDT)
Received: from ?IPv6:2406:e003:11aa:d701:80b2:5c79:2266:e431? ([2406:e003:11aa:d701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id j6sm2601333pfn.107.2021.09.11.14.38.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 11 Sep 2021 14:38:21 -0700 (PDT)
To: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <BL0PR05MB5316375D7503A85477DF874AAED59@BL0PR05MB5316.namprd05.prod.outlook.com> <ca24a2d5-d347-7a7a-8f5a-55bd53dd4525@gmail.com> <bbeab7d9e9c140a4bc2c24aeed442245@huawei.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <284dcb57-4d62-1787-e1d4-9fff2818b172@gmail.com>
Date: Sun, 12 Sep 2021 09:38:17 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <bbeab7d9e9c140a4bc2c24aeed442245@huawei.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ks2XOlZvFhQ0Rr0TOSXIZV-kDdw>
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 21:38:32 -0000

Hi Shuping,

Thanks. I think that Gorry Fairhurst's comments express exactly what I want to say. I support adoption, subject to those comments.

Regards
   Brian

On 11-Sep-21 16:00, Pengshuping (Peng Shuping) wrote:
> 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

v2.23.0 | Report a Bug | By Email