[v6ops] How was a /16 of IPv6 asigned from ARIN to non large network?
Momoka Yamamoto <momoka.my6@gmail.com> Thu, 07 December 2023 19:29 UTC
Return-Path: <momoka.my6@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 963A0C14CE33 for <v6ops@ietfa.amsl.com>; Thu, 7 Dec 2023 11:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level:
X-Spam-Status: No, score=-1.855 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 XVFA3aXZxrrM for <v6ops@ietfa.amsl.com>; Thu, 7 Dec 2023 11:29:15 -0800 (PST)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 86E84C14F600 for <v6ops@ietf.org>; Thu, 7 Dec 2023 11:29:15 -0800 (PST)
Received: by mail-lf1-x136.google.com with SMTP id 2adb3069b0e04-50c222a022dso750061e87.1 for <v6ops@ietf.org>; Thu, 07 Dec 2023 11:29:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701977353; x=1702582153; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=SEjFZE6/eTsDwPEHqIF6Hx25tnjvvusUWcZ7yTxZqAY=; b=ekYAL23WDmE6Iqhna+PItybtRld05FzSDA2udbpzqVXgl+xGXbyq0pUveXJUAnEN4c qul2VvMYuSlmMpD1w18a64jSZn5JBS7QwdDZTlS1l+g2rZQ65nkLkVGzvRR9r6PQeAo7 BpN6mF86Jlgt45ZM97yYenYC0mXULqmvYLhc+Fh97/dTLDmVDpTZNfN68cb1JBRIsl1W Ci0HME0fh7rrtPcUJcRGL1JNAI5kq1skwiNdlhROHgn7MxJt/M4NlITnc8UlQvKSOPdO de4CWFjyhUEpsVyp2FrHD9M5PrOqfhw9ANaaYV0f5oNWc1/sHL9cb9XjwSQo887Jb91z vMTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701977353; x=1702582153; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=SEjFZE6/eTsDwPEHqIF6Hx25tnjvvusUWcZ7yTxZqAY=; b=WuoTuPjSyDyRh4w0tB0jDH5dItKma6npDISi5ftnOvJcIffqUjwMozQy71u+GsNlHA +cCw6FOsAlk433m40Vj8ko2BrGidto99nm1iB8RJH32WZ1WAW8qoZ7V9gHg6oMfwuadB A2gbRTdGD0lLGNnVJPvbqtPIqde3/yDwYmGBd2t+sy1xbvOW9JyglkvzQJKWoiHkNWm4 KQvAmL/goaYLl/W4DeQYGfJ+07Zd34Gd4pdjnjOTuJfGgSqY9ZUSsi9wg3Ev5miPhS1c FofdipeAd7aSrT+n01KFoL3dUQBUC+ZUIWoHzWaDTQHhgvIOhFPcHKtDNW+BWkLPuZtq oM9Q==
X-Gm-Message-State: AOJu0YxrJyYDlmnK3DBZn5cOg36y8l5ZDFrZEbLmuTfqyW6gRaGMwdgS NDFl0//mUTQhBV0yKhqgj9kUdwqJe+x0xZjlYMbgnnTurr4=
X-Google-Smtp-Source: AGHT+IFbKci/4rvPA4nxYZ+xUsr3ZhqDfpgYRek9GwB9W/qOGBVMcLoAliXzUcAwtH253X3aWTKMT0GCQvk02v4EZ6c=
X-Received: by 2002:a19:6557:0:b0:50b:d764:8826 with SMTP id c23-20020a196557000000b0050bd7648826mr2025692lfj.114.1701977353091; Thu, 07 Dec 2023 11:29:13 -0800 (PST)
MIME-Version: 1.0
From: Momoka Yamamoto <momoka.my6@gmail.com>
Date: Fri, 08 Dec 2023 04:29:01 +0900
Message-ID: <CAD9w2qYxwSUEkzkiHspJH4bn9_Tu6YxFqbfv_6tGFYQbPDUUSg@mail.gmail.com>
To: list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008c0033060bf07b4b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ThaSy_hNlx1GP59EFAJ9NkBXP5A>
Subject: [v6ops] How was a /16 of IPv6 asigned from ARIN to non large network?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 07 Dec 2023 19:29:19 -0000
Daryll Swer just posted to the WGLC > 1. Regarding section 2, it appears the largest assignment is a /16 (2630::/16), a fairly new assignment— https://whois.arin.net/rest/net/NET6-2630-2 > > "The four largest assignments made to end users have been /19s" Creating a new thread as I think this should be discussed outside of the specific draft. Geoff at the mic I thought you said at the moment we are only allocating a maximum /20 Even if a /16 is needed for a huge network looking at BGP tools CAPITAL-ONE does NOT look like it has a large network. Why does it need it? Why did ARIN allocate this to them? https://bgp.tools/rir-owner/ARIN-CAPITA-120 This question would be different if it was a Tier-1 or Google, AWS. (still /16 is wild) Is this a special allocation? What meaning does this have? I see it is the very first /16 of ARIN's new 2630:0000::/12 2630:: - 2630:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF It is 1/16th of *ARIN's* 2630::/12. It is HUGE. Momoka
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Daryll Swer
- [v6ops] How was a /16 of IPv6 asigned from ARIN t… Momoka Yamamoto
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Nick Buraglio
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Ed Horley
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Momoka Yamamoto
- [v6ops] I think that a /20 is enough for the new … Gábor LENCSE
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Daryll Swer
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Gert Doering
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Geoff Huston
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Jeroen Massar
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Owen DeLong
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Daryll Swer
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Brian E Carpenter
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… David Farmer
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Owen DeLong
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Owen DeLong
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Owen DeLong
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Momoka Yamamoto
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Owen DeLong
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Daryll Swer
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Ed Horley
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… owen@Delong.com
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Daryll Swer
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… owen@Delong.com
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… Daryll Swer
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… David Farmer
- Re: [v6ops] How was a /16 of IPv6 asigned from AR… owen@Delong.com