IETF Logo Mail Archive

[IPv6] Early Allocation on the IPv6 VTN option

Ole Troan <otroan@employees.org> Thu, 01 June 2023 11:19 UTC

Return-Path: <otroan@employees.org>
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 B983FC15106D; Thu, 1 Jun 2023 04:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=employees.org
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 Spa5QKeTyVg0; Thu, 1 Jun 2023 04:19:38 -0700 (PDT)
Received: from proxmox01.kjsl.com (proxmox01.kjsl.com [204.87.183.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 2C427C15106B; Thu, 1 Jun 2023 04:19:38 -0700 (PDT)
Received: from proxmox01.kjsl.com (localhost.localdomain [127.0.0.1]) by proxmox01.kjsl.com (Proxmox) with ESMTP id BCDE2E323D; Thu, 1 Jun 2023 11:19:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=employees.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:from:from:message-id:mime-version:reply-to:subject:subject :to:to; s=prox2023; bh=9ybRO97lpfB9ha+gZI6wxLg2P3lvmHfB9p/HqWD7p SM=; b=Gg6roWocQh8qyAoBNtrGWCn7W6eD8z2Fo7GtkTwHBhragPQfibd/Ty2AF zQerX9HvQvChKqcauUfWa5495faTmXhaFihKptvQRuv7DnaipOgg06mVhaii6SPi 1q0ak/LaAGUDFR0inQfmXcw+AfpGObQH+yy2KEoAFV/V1+Yn4Mr9x6K+wUim12b+ h5m4o8p3sIyTG0Mce6bvQRWgEjt2SDSnhvJwSAEeK6wuZLeCPnTu0s2QbK72ktgl WJYv59edGwkT2fj0gY9xLP/ipGiik2lTpcVy7k7N25bwkE24EN29zTJJWTzo5i5x /PbE9R1J/oyfYZ5NeCLm1Yj/LaaEA==
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by proxmox01.kjsl.com (Proxmox) with ESMTPS id A2015E3239; Thu, 1 Jun 2023 11:19:37 +0000 (UTC)
Received: from smtpclient.apple (unknown [IPv6:2a02:2121:103:3cb3:140:da8c:ce32:a85f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 016744E11B82; Thu, 1 Jun 2023 11:19:36 +0000 (UTC)
From: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
Message-Id: <61164615-A39B-4797-8FB5-70B1F360BD62@employees.org>
Date: Thu, 01 Jun 2023 13:19:24 +0200
Cc: 6man Chairs <6man-chairs@ietf.org>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/H8x2K-VT6ildl8080qOAe3AMZ3M>
Subject: [IPv6] Early Allocation on the IPv6 VTN option
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, 01 Jun 2023 11:19:42 -0000

Dear Working Group,

We have received a request for an early allocation of the IPv6 VTN option specified in:
draft-ietf-6man-enhanced-vpn-vtn-id-04.txt

Conditions for early allocation is outlined in RFC7120.

Note specifically this:
   c. The specifications of these code points must be stable; i.e., if
  there is a change, implementations based on the earlier and later
  specifications must be seamlessly interoperable.

An early allocation will freeze the option format.
Would you mind reviewing the document and especially the option definition and chime in if you think changes are required prior to allocating a code point.

For the chairs,
Ole

v2.23.0 | Report a Bug | By Email