Re: I-D Action: draft-ietf-6man-hbh-processing-01.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 07 July 2022 22:56 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0E7C15A75A for <ipv6@ietfa.amsl.com>; Thu, 7 Jul 2022 15:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.981
X-Spam-Level:
X-Spam-Status: No, score=-3.981 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=-1.876, 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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 dsNWQzGYhf4D for <ipv6@ietfa.amsl.com>; Thu, 7 Jul 2022 15:55:57 -0700 (PDT)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE745C15AB58 for <ipv6@ietf.org>; Thu, 7 Jul 2022 15:55:57 -0700 (PDT)
Received: by mail-pg1-x535.google.com with SMTP id e132so20883419pgc.5 for <ipv6@ietf.org>; Thu, 07 Jul 2022 15:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=mEu4ucgDirPWbkQiiCiwq8UlHZ5Kuk2fyFvyt7OBmLE=; b=PaHo7dFLJB8l8U6qSXv8423zxT8Dz0Sy/AaXdbHp8btqpdwPC2jPVVQytOGWWltly4 G9hLH5XR3+lEoKPIxA2qLHwnrtjGwn+MZfZPjHF1NMGew7Zm51fwoztqdPtSWfN9wVz0 KX0bB/vhKdh/PtB+9QXMNYSFcX4hj+f0idpePuRQYDNB9U1W3aynrD009+nE2EoAQicw r/ALQMHJbe/fFPFSJe4wd4MdfqxC5QIGW0mkZlWanfWRVlryuDmOEbU0uiO23PnjeZpt 0KKA2ndb1Db1j1VZaDF8VdynpxGCgvDBgzzZLBOFVJjLZoTIOz2Uc+B8gMWBlyOLYJSr 6kog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=mEu4ucgDirPWbkQiiCiwq8UlHZ5Kuk2fyFvyt7OBmLE=; b=ESCS29U6tek2csOVx3qMjmONDJ0RwUQkTuLWp2OtvR4YstDIWw8nKq7XbCM2t/ke/3 Q2ENENTpeb0HLxv+H9JlWL/4miLNSgoo69bpUs9CqxxIEKtTVs/kD6ZiKR+7En8Qb4vN w1/WIpo8RlnUD+fBxDsRGWVLkClZFeWdPPafAJC1aaOdTbSRUOX2OcwTnbImLfInztZF lxLbLzPUoqfKaywjwfGw/X5l2aIg9iiA2BPspLF5LWq0sYg2uVMWDVNEdRr+K/2m7LQS C2Pf5tEkvJDnKzhKhVV8gteD/ktxmHD/qJG5O+xO5g7JVrmzW/pJYh0b0HtiRxfDvmZB TiJg==
X-Gm-Message-State: AJIora9l7eqefE5hM/NiCx8fAI7OeSbFNWEYFx/QWu5bheCBHZ5+jT82 osrwVl0oi7dD10reIXu6pgiCUbs7cEThrw==
X-Google-Smtp-Source: AGRyM1sy7xA3Ze/f7EJeHKnmAoG+g3yKamp9DkdKUBVEU4ZFHjz/dAAbWMDIAmKzYAG9AXesvCxcEA==
X-Received: by 2002:a65:6e94:0:b0:412:74b3:d72d with SMTP id bm20-20020a656e94000000b0041274b3d72dmr387787pgb.471.1657234556522; Thu, 07 Jul 2022 15:55:56 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id u17-20020a17090341d100b0016909678e2csm28752113ple.292.2022.07.07.15.55.54 for <ipv6@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Jul 2022 15:55:55 -0700 (PDT)
Message-ID: <6e1c4762-0216-80b8-ac24-eb69aab5095c@gmail.com>
Date: Fri, 08 Jul 2022 10:55:52 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Subject: Re: I-D Action: draft-ietf-6man-hbh-processing-01.txt
Content-Language: en-US
To: 6man <ipv6@ietf.org>
References: <165718716300.25781.11555178792766969391@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <165718716300.25781.11555178792766969391@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/3rLmfFq0IzqCZO_VDifp0NbaHmg>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2022 22:56:01 -0000

Thanks for the update.

> The authors expectations are that some hop-by-hop options will be	
> processed across the Internet while others will only be processed in	
> a limited domain (e.g., where there is a specific service made	
> available in that network segment that relies on one or more hop-by-	
> hop options).

I think this is a useful comment. However, since we are pointing
this at the standards track, it's a bit vague. Should we
a) require that the specifications of new options explicitly
state whether they are intended for global usage or a limited
domain; and
b) tag all currently specified options for global or limited use?

(Which might generate some IANA actions).

Nits:

> The editors focus for this document is to set a lower bound	

That needs an apostrophe: editors'

...
> The authors expectations are that some hop-by-hop options will be	

And that: authors'

Regards
    Brian Carpenter

On 07-Jul-22 21:46, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 Maintenance WG of the IETF.
> 
>          Title           : IPv6 Hop-by-Hop Options Processing Procedures
>          Authors         : Robert M. Hinden
>                            Godred Fairhurst
>    Filename        : draft-ietf-6man-hbh-processing-01.txt
>    Pages           : 14
>    Date            : 2022-07-07
> 
> Abstract:
>     This document specifies procedures for how IPv6 Hop-by-Hop options
>     are processed.  It modifies the procedures specified in the IPv6
>     Protocol Specification (RFC8200) to make processing of IPv6 Hop-by-
>     Hop options practical with the goal of making IPv6 Hop-by-Hop options
>     useful to deploy and use in the Internet.  When published, this
>     document updates RFC8200.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-hbh-processing/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-6man-hbh-processing-01.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-hbh-processing-01
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt