IETF Logo Mail Archive

Re: [mpls] Available IP version numbers.

ietf@sergey.dev Mon, 19 April 2021 18:53 UTC

Return-Path: <ietf@sergey.dev>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C46D3A3F09 for <mpls@ietfa.amsl.com>; Mon, 19 Apr 2021 11:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.196
X-Spam-Level:
X-Spam-Status: No, score=-0.196 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sergey.dev
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 PVgwJsQA4khc for <mpls@ietfa.amsl.com>; Mon, 19 Apr 2021 11:53:32 -0700 (PDT)
Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [5.45.198.240]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A42E83A3F04 for <mpls@ietf.org>; Mon, 19 Apr 2021 11:53:32 -0700 (PDT)
Received: from myt5-52bcf6ee3a24.qloud-c.yandex.net (myt5-52bcf6ee3a24.qloud-c.yandex.net [IPv6:2a02:6b8:c00:2f93:0:640:52bc:f6ee]) by forward100j.mail.yandex.net (Yandex) with ESMTP id BA07750E04ED; Mon, 19 Apr 2021 21:53:27 +0300 (MSK)
Received: from myt6-efff10c3476a.qloud-c.yandex.net (myt6-efff10c3476a.qloud-c.yandex.net [2a02:6b8:c12:13a3:0:640:efff:10c3]) by myt5-52bcf6ee3a24.qloud-c.yandex.net (mxback/Yandex) with ESMTP id zRHtHRfmWN-rRIuKpXI; Mon, 19 Apr 2021 21:53:27 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sergey.dev; s=mail; t=1618858407; bh=ZrGHhf3x4M8rxbR1gNJGDEpjsNeltLEZRgIuIo+1hko=; h=Subject:Date:References:To:From:Message-ID:In-Reply-To; b=PHJ8NwsnFmLDOCsa+yyfIjQsl8Wq3S8cypI4c8WeXJBZAMsDAbIftb5Wyqjm1vq95 8vcfiCP4wzPDsBHsbyugZhgctSFBK6eJVzXyx+p8c1OYtSv3vNMvI8ZDcGoPAiswpM Uqc735I386/p4QjiWRvvR/ATJhnmKBLDHahdp3cA=
Authentication-Results: myt5-52bcf6ee3a24.qloud-c.yandex.net; dkim=pass header.i=@sergey.dev
Received: by myt6-efff10c3476a.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id nTOQTY9KjR-rQKqCbML; Mon, 19 Apr 2021 21:53:26 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present)
From: ietf@sergey.dev
To: 'Loa Andersson' <loa.pi.nu@gmail.com>, 'mpls' <mpls@ietf.org>
References: <A5C8DFA9-3601-4838-9461-727CC40507B1@gmail.com>
In-Reply-To: <A5C8DFA9-3601-4838-9461-727CC40507B1@gmail.com>
Date: Mon, 19 Apr 2021 11:53:23 -0700
Message-ID: <003701d7354d$4810e660$d832b320$@sergey.dev>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKUPgr7n0r+Iugvfy2N2vrBHUrKs6lCHa1A
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/FbqG8VRTqYFw9qpaH9Mtmxzkuyo>
Subject: Re: [mpls] Available IP version numbers.
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2021 18:53:37 -0000

Hi Loa,
In an adjacent thread ("mpls open dt & the first nibble discussion") I raised a question about why do we even expect to take something from IP numbering. Would appreciate your feedback on this one.


-----Original Message-----
From: mpls <mpls-bounces@ietf.org> On Behalf Of Loa Andersson
Sent: Saturday, April 17, 2021 1:13 AM
To: mpls <mpls@ietf.org>
Subject: [mpls] Available IP version numbers.

DT,

We had a discussion on how many IP version numbers are available. 

It should be remembered that in IANA “Reserved” really means “Reserved, do not assign”. 

0,1,5,7,8,9 and 15 are reserved. 
2,3,10,11,12,13 and 14 are unassigned
4 and 6 are assigned 

To make the reserved requires a standard track RFC. 

So we 7 IP version numbers available, that is a sufficient low number to make me nervous, if I owned the registry. 

I would nit count on having more IP version numbers assigned to “us”, especially since we already have an agreement (PWE3), accepting to get two numbers and committing to not use more. 

/Loa

Sent from my iPhone
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

v2.23.0 | Report a Bug | By Email