Re: Extending a /64

Gyan Mishra <hayabusagsm@gmail.com> Wed, 11 November 2020 06:51 UTC

Return-Path: <hayabusagsm@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 308623A08AF for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 22:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6_Ci1zI0tE9 for <ipv6@ietfa.amsl.com>; Tue, 10 Nov 2020 22:51:28 -0800 (PST)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDE9B3A08A6 for <ipv6@ietf.org>; Tue, 10 Nov 2020 22:51:28 -0800 (PST)
Received: by mail-vs1-xe35.google.com with SMTP id m16so583683vsl.8 for <ipv6@ietf.org>; Tue, 10 Nov 2020 22:51:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+sdXaNLHFMOmVDDM6P6+HZy+zYXIk8bH41FQ1XzG4Ck=; b=hcLOC2pGW6kgf7hnLp0NPCkr8jqbsI6kIg6nEwfsRa8gGrM8Rx/sgF9gREeQsXAN0+ 0wIUbaj7ZOS00KVzPKQowSHKlstW1Vl3ZsWhEglhigIOibFP/nKcscYXH3dxSLla++rj tF0kqvbJ672hUdAINtRRQh3QlIEBtkBdCSn8z6+wkuu9SgZBu/mirOv8cL8JBfY2RN9p a6rd1Tx6RSKFM9/gwceg6mjgZ6V8d3+HK3+xnHOZXm84pPJ4/RaygF7QPknks6Yp2vLp h65BJajUh+fEBbRUjOOPtR2Gwgtz/bDl0KcRpY3AL9/+lj0iqi1gztb3sE05u6WZh8wy p68Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+sdXaNLHFMOmVDDM6P6+HZy+zYXIk8bH41FQ1XzG4Ck=; b=MVoN2Q1G2q1ruB+DuO9YsqKVQFryQvB8aCKaQwndNW9Pg37oWk96oou6TAaZ5+vh/h ENh+cUnwUJtDXyeEzF/zTrLWMzU0s+Subvstn24W74rp1dVUwWKwXtV5mWigUqzXYX1n 7dtBCO65Ll9/3ogEO/2A8d5AuP+5uw2dZ7PGKeaNGDiwooM0sNp1OA7VCq+qXIiWPRSh 4IhYqHmm2NUnwyY3262OB37tsQrxYLYyyMREfIo0RJ9E9w6lBJBXjlxC7kifDCQ3RJRH ccrvfxj57vDEVV/KeFf94L1Q4ZGSwBP0JHNJWCmtLf/39dYv1uZ0i05T7bMr4UzlzCeD Kosg==
X-Gm-Message-State: AOAM532hOZ/ofX6dj+xjxIVhF/Y60eRzCYej/PwPbRVagJN8HxrUpuVW Um9r7nrjkl90Ygv7b+To8yDDxlLX2u3xuKAw94jwxhA39dtMFA==
X-Google-Smtp-Source: ABdhPJyd/QClV1rLh21Rk7EAwx8forfMtSE6VV2+sEDjARQaIpaYUqN3att/fH4PbHpJkz/YDBsTtvYwzp3Xnt3K3UE=
X-Received: by 2002:a67:741:: with SMTP id 62mr8431795vsh.5.1605077487747; Tue, 10 Nov 2020 22:51:27 -0800 (PST)
MIME-Version: 1.0
References: <005ECBB3-088B-4363-BB53-8D4AD25CA3D2@employees.org> <b468124f-f85b-7e20-a354-c6b7eaba3447@mccallumwhyman.com> <20593.1604972743@localhost> <CAKr6gn0tedRz4iBu49Lrw5qMCdXWPcg-66UAOfHeJ_ZUeq8U4g@mail.gmail.com>
In-Reply-To: <CAKr6gn0tedRz4iBu49Lrw5qMCdXWPcg-66UAOfHeJ_ZUeq8U4g@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 11 Nov 2020 01:51:16 -0500
Message-ID: <CABNhwV2c_qaQGY2J62LDh=EZYHo5poYNF_Asf908ofR3wfmW1g@mail.gmail.com>
Subject: Re: Extending a /64
To: George Michaelson <ggm@algebras.org>
Cc: IPv6 <ipv6@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="0000000000007e868005b3cf39a1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/OGZGVFLguWC3W2OXxRyQh-HNyzk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Nov 2020 06:51:31 -0000

For this to be idea to come to fruition we need buy in from both 3GPP
architecture to allow  < 64 ra and IETF as well RFC 4291 and 4862.

Cameron

Would 3GPP architecture just have to update their code  to support shorter
prefix RA, or is there anything else technical that has to change on the
3GPP end.

On Tue, Nov 10, 2020 at 8:15 PM George Michaelson <ggm@algebras.org> wrote:

> There is a liaison function between the RIR and the IETF, and the IETF
> and IANA regarding address dispositions. When people reach a point
> they believe there is a need for an unusual assignment from global
> unicast space, the proper thing to do, is invoke the liaison function,
> and have this dealt with respectfully across distinct process
> boundaries regarding how addresses are managed and delegated.
>
> As long as the people who perform this liaison function are aware of
> this conversation, nothing much else has to be said here. I would ask
> that the WG chairs and AD keep that in mind.
>
> cheers
>
> -George
>
> On Tue, Nov 10, 2020 at 11:45 AM Michael Richardson
> <mcr+ietf@sandelman.ca> wrote:
> >
> >
> > Tony Whyman <tony.whyman@mccallumwhyman.com> wrote:
> >     > In the end, we concluded that we could not bend the existing
> standards
> >     > to do this and did not have the desire to push for change. Hence,
> we
> >     > are in the process of asking IANA for a /16 for the global civil
> >     > aviation community. Hopefully we will get this. However, an
> argument is
> >     > expected given that the current policies push back against such a
> large
> >     > allocation and demand a utilisation efficiency that we will never
> >     > achieve. However, if we don't get a /16 and the standards stay as
> they
> >     > are, then a private address space and NAT at the boundaries may be
> the
> >     > only answer - not really what anyone wants.
> >
> > I think that it's pretty important that the IETF IPv6 community
> understand
> > your needs, and speak clearly in support of your needs.
> >
> > What would happen if you had a /18 or a /20?
> >
> > --
> > Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT
> consulting )
> >            Sandelman Software Works Inc, Ottawa and Worldwide
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD