Re: [IPv6] Adoption call for draft-bonica-6man-comp-rtg-hdr

Bob Hinden <bob.hinden@gmail.com> Wed, 08 November 2023 11:11 UTC

Return-Path: <bob.hinden@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 2626FC170610; Wed, 8 Nov 2023 03:11:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=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 LwwNt5-IuI_4; Wed, 8 Nov 2023 03:11:55 -0800 (PST)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 52A8BC17DBF0; Wed, 8 Nov 2023 03:11:55 -0800 (PST)
Received: by mail-pl1-x632.google.com with SMTP id d9443c01a7336-1cc2fc281cdso51716985ad.0; Wed, 08 Nov 2023 03:11:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699441915; x=1700046715; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=NArltTYNpBFmL1oTGrtDCVx9WY5jbVjRbRFWx29c864=; b=M2BylpWGp1barraLpNVbJA4jVc4ajBHUI0Bryng2UoffsYW7Jc8CIBVUOvEXpYPdhI 1ee8ydEkP9BOl5iedmmYsxVsDcUEoilwaPjJ4jqwst5RNAkpMAhQnOnKj0/08lWurRZD p8qqIWfdxY5OCzd1WHCM6/I0KyVqS2jbHzQYdnsuTta5pUQKOSvpwr3uS+kxmuF7Sh59 a5PqsuDC1YZHnhpGVdqjV29DzQihbfYeJdgkwiSG7T+1FKjhCB4NT1HZ6csMUyq96HI2 QKgbEfzy/ZWfjsHG+9ny0T2MnTa75RBqanV6ICWkJM49faETeciNxVIJ5s+hj7OFrNOf oIaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699441915; x=1700046715; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=NArltTYNpBFmL1oTGrtDCVx9WY5jbVjRbRFWx29c864=; b=BvBy1pCib9S5NSEANwAwROZkgoaq94iAT1jYtTp/2JA6yXSvFs5msoBofHPwjE4tpc /GA4DeIjv0X0XRoHJKdCmdZVTMae9F6vRxqmkAL3mY1xifN9uQXMRPpCuWRy3f/kVT4d to1h3EbeM/rK/Bv7QzocxATWKy983PxfV/BOkgXSPMhKC9WKRjqL7sZp3k32grODLKKp d9S05KuAuOKm6oDu2yts2zxnTIkrYHwIDl5pkhCl+0MWUuMWtchZCgO7IAvQWIvSn1XF P686rFkrUmkxUln1Hm+psQe84vZ1gRWAKj63aBuOvSe0lTWdDkPrvyKjG1d8XBW6u+tf KVtQ==
X-Gm-Message-State: AOJu0YyXXNMJWqgeLrhrekxBp2SDrUA3LzJKAyjMky7a+QM++Mf7qh3c 1kY4f/qC/dk4QTjQeVe4u+w=
X-Google-Smtp-Source: AGHT+IF+Ai5U1KOfVXWPk+pAvS8U81HpL6l+mm30YOAzqGEpP5Spcg4xgl7TZR/eSmk21HKt/ADSpw==
X-Received: by 2002:a17:902:6b88:b0:1cc:13d0:d515 with SMTP id p8-20020a1709026b8800b001cc13d0d515mr1532248plk.20.1699441914714; Wed, 08 Nov 2023 03:11:54 -0800 (PST)
Received: from smtpclient.apple (dhcp-8254.meeting.ietf.org. [31.133.130.84]) by smtp.gmail.com with ESMTPSA id k4-20020a170902d58400b001c5fd2a28d3sm1498285plh.28.2023.11.08.03.11.52 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Nov 2023 03:11:54 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <6402E03D-5822-402D-92A4-9FEEA1855966@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_04CCAD21-899E-44EC-92BE-66E57E9DF160"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Date: Wed, 08 Nov 2023 12:11:40 +0100
In-Reply-To: <DM6PR11MB46925E6F8367B45579EC88A1DEA8A@DM6PR11MB4692.namprd11.prod.outlook.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "Zafar Ali (zali)" <zali=40cisco.com@dmarc.ietf.org>, IPv6 List <ipv6@ietf.org>, "draft-bonica-6man-comp-rtg-hdr.authors@ietf.org" <draft-bonica-6man-comp-rtg-hdr.authors@ietf.org>
To: "Zafar Ali (zali)" <zali@cisco.com>
References: <CAFU7BARQLAS+w7kKUPSBgFacc5GXNAaJ97qkJg9VyjbhoNibcQ@mail.gmail.com> <DM6PR11MB4692AC74DBE305C99CD69BF6DEA8A@DM6PR11MB4692.namprd11.prod.outlook.com> <CE0F54E2-7256-4952-B017-6DFD416DCB58@gmail.com> <DM6PR11MB46925E6F8367B45579EC88A1DEA8A@DM6PR11MB4692.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/krJiuSr5CGU8nJpAd4qRK5KZ1Do>
Subject: Re: [IPv6] Adoption call for draft-bonica-6man-comp-rtg-hdr
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: Wed, 08 Nov 2023 11:11:59 -0000

Zafar,

We follow our normal process.   That is discussion, adoption call, discussion, w.g. last call, etc., etc.

Bob


> On Nov 8, 2023, at 11:57 AM, Zafar Ali (zali) <zali@cisco.com> wrote:
> 
> Hi Bob,
> 
> What is 6man’s bar for acceptance of a new “routing" header.
> Especially, in the case of CRH:
> In consultation with 6man, the Routing Area appointed a design team.
> One of the authors of CRH draft was part of the design team that decided CRH is not needed.
> After the design team decision, is there any WG in the routing area where CRH was presented, reviewed, found needed?
> All similar routing headers have been the work of other working groups, e.g., RPL->ROLL, SRH->SPRING.
> CRH is a new flavor of label to IPv6 mapping technology, more akin to MPLS in IPv6 that routing area has already standardized [RFC7510].
> 
> Thanks
> 
> Regards … Zafar
> 
> From: ipv6 <ipv6-bounces@ietf.org <mailto:ipv6-bounces@ietf.org>> on behalf of Bob Hinden <bob.hinden@gmail.com <mailto:bob.hinden@gmail.com>>
> Date: Wednesday, November 8, 2023 at 6:36 AM
> To: Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org <mailto:zali=40cisco.com@dmarc.ietf.org>>
> Cc: IPv6 List <ipv6@ietf.org <mailto:ipv6@ietf.org>>, Bob Hinden <bob.hinden@gmail.com <mailto:bob.hinden@gmail.com>>, draft-bonica-6man-comp-rtg-hdr.authors@ietf.org <mailto:draft-bonica-6man-comp-rtg-hdr.authors@ietf.org> <draft-bonica-6man-comp-rtg-hdr.authors@ietf.org <mailto:draft-bonica-6man-comp-rtg-hdr.authors@ietf.org>>
> Subject: Re: [IPv6] Adoption call for draft-bonica-6man-comp-rtg-hdr
> 
> Hi Zafar,
> 
> Regarding the higher level issue you are asking about the 6MAN charter and defining new routing headers, I note that the RFC8200 IPv6 specification defines the IPv6 Routing header in Section 4.4.  That definition includes an 8 bit Routing Type field, allowing for up to 255 different routing headers to be defined in IPv6.   In the IANA registry types 7-252 are unassigned.
> 
> Defining a new routing header is not a major change or addition to the IPv6 specification.
> 
> Bob
> 
> 
> 
> On Nov 8, 2023, at 9:39 AM, Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org <mailto:zali=40cisco.com@dmarc.ietf.org>> wrote:
> 
> Hi,
> 
> When consulting the 6man charter...
> What protocol limitation/issue is CRH addressing for IPv6?
> What IPv6 maintenance/upkeep is CRH achieving?
> “is not chartered to develop major changes or additions to the IPv6 specifications”
> CRH is a new flavor of label to IPv6 mapping technology, more akin to MPLS in IPv6 that IETF has already standardized [RFC7510].
> Being a new “routing header” (that is now being claimed as being distinct from Segment Routing) is there any WG in the “routing area” where this work has been presented and reviewed?
> Has the routing area accepted and agreed to the necessity and the appropriateness of this new technology? Is there a document that captures the requirements for this technology and the use cases that are not met by existing IETF technologies?
> I have not seen a statement from 6man chairs on how this work falls within its charter as the authors have said this is not Segment Routing related work that is driven by the Spring WG.
> 
> I object the adoption of draft-bonica-6man-comp-rtg-hdr.
> 
> Thanks
> 
> Regards … Zafar
> 
> From: ipv6 <ipv6-bounces@ietf.org <mailto:ipv6-bounces@ietf.org>> on behalf of Jen Linkova <furry13@gmail.com <mailto:furry13@gmail.com>>
> Date: Thursday, October 26, 2023 at 5:05 AM
> To: 6man <ipv6@ietf.org <mailto:ipv6@ietf.org>>
> Cc: draft-bonica-6man-comp-rtg-hdr.authors@ietf.org <mailto:draft-bonica-6man-comp-rtg-hdr.authors@ietf.org> <draft-bonica-6man-comp-rtg-hdr.authors@ietf.org <mailto:draft-bonica-6man-comp-rtg-hdr.authors@ietf.org>>
> Subject: [IPv6] Adoption call for draft-bonica-6man-comp-rtg-hdr
> 
> This email starts an adoption call for the following document:
> 
> Title: The IPv6 Compact Routing Header (CRH)
> Draft name: draft-bonica-6man-comp-rtg-hdr
> Link:  https://datatracker.ietf.org/doc/draft-bonica-6man-comp-rtg-hdr/
> 
> Substantive comments and statements of support for adopting this
> document should be sent to the mailing list. Editorial suggestions can
> be sent to the authors.
> 
> The adoption call ends on Monday, Nov 13th, 23:59 UTC.
> 
> --
> SY, Jen Linkova aka Furry
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org <mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------