Re: Extending a /64
Christopher Morrow <christopher.morrow@gmail.com> Wed, 11 November 2020 19:44 UTC
Return-Path: <christopher.morrow@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 02BB13A0F2E for <ipv6@ietfa.amsl.com>; Wed, 11 Nov 2020 11:44:35 -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 XozHFCq7qJjG for <ipv6@ietfa.amsl.com>; Wed, 11 Nov 2020 11:44:33 -0800 (PST)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 1696D3A0F13 for <ipv6@ietf.org>; Wed, 11 Nov 2020 11:44:33 -0800 (PST)
Received: by mail-qk1-x733.google.com with SMTP id r7so2932495qkf.3 for <ipv6@ietf.org>; Wed, 11 Nov 2020 11:44:33 -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=tahPWrZPnT8wSq/C41T0hqPOXnjixsU/a5NCe8cNhBs=; b=dOz7DZHHc+WtAfD3fT3g2ioRxTjvfLuENhGIPNRDlgPKQXe7I3pJoHNaulNbnbnWXf jSbY2qqlr8yTXUfmOnkr5Z5XUeCZTHuBrZm5s9NpCKHT8NAZxXB1OMEKrniPsiXfUZZ0 Hz/R2UccykTQ/xOzyWWrqLIwOYSq+KS4Gj1A/jacJl1oypcx0RQgrx+1OQpmxAOKciAr 0EKzYNncQ7+raDf7rcEqHEWlczUnewnI/JV/+QJ7RkAYTZp5qmRB3T22DBWwrmTFb879 pmsxiaRFpqkWo9ex4IvI4epXTBXhGdpYaYbS/mOL7/uwDQ19nHHXwSI2K34PUW5b0I5a jsJA==
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=tahPWrZPnT8wSq/C41T0hqPOXnjixsU/a5NCe8cNhBs=; b=NxEhKF0qw3wL4kO3wGDiZ+ZYgALhUzwHuMdRajMq3GzibcfvShsKzskD8rPYQK35kj fjQw4tLx0Zz1sHDP4MqA+mvXjteKJgP5kgsTulzLiIn0IXMOXhsjkX/nH/0y3NuZI6k+ ouAsEYP49jcWwhIDymMiHFR+MLh7AXxgw4431c7RuRlM8XRa1+VqAuRNe9Io6UDLI3PK nY7tQO+AMWbvGP32eK4LG4qCMJX84LM1eNd5VNdALSo5VxanLSQEQIime464kZsjz4tR Hr23NvxqjwrKXDbJdYeWehGIiiw3ffN0ruTPf9UbJscPsu03IYRoy3iyjqiuny5GhJHG /T0w==
X-Gm-Message-State: AOAM532nwUIT2EN+rR/zF2OMEEKj1dvfgHxvln4tF+TbwGm0hBBmv/Rw u+C5BoOUVbPAgKYTDlW4+davHPlegKPoB0U66s+vBq6gZZKcmA==
X-Google-Smtp-Source: ABdhPJx5PNR3aYXFva3s3h0x+HPVzX665tdTVaF5Mvr/gRO5lUy5s/2TuD3n1a/lQOcQY4kJU9ekBNQ4dwCz61PdlDE=
X-Received: by 2002:a37:af81:: with SMTP id y123mr26403866qke.50.1605123872103; Wed, 11 Nov 2020 11:44:32 -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> <CABNhwV2c_qaQGY2J62LDh=EZYHo5poYNF_Asf908ofR3wfmW1g@mail.gmail.com> <CABNhwV3wgdOUKqOyqJ4bTvVv4PKq81anYCxASOTCEMg3T84zig@mail.gmail.com>
In-Reply-To: <CABNhwV3wgdOUKqOyqJ4bTvVv4PKq81anYCxASOTCEMg3T84zig@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Wed, 11 Nov 2020 14:44:21 -0500
Message-ID: <CAL9jLaaDYrXVTGQeWh4aAc-qUVCoxRNokwANpQhuZ4OGdpySMw@mail.gmail.com>
Subject: Re: Extending a /64
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: George Michaelson <ggm@algebras.org>, Michael Richardson <mcr+ietf@sandelman.ca>, IPv6 <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000037a38f05b3da06d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/oA4U3Cws09BZZdlQTHaEAkqvonc>
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 19:44:35 -0000
it seems that this whole conversation is really: https://tools.ietf.org/html/draft-bourbaki-6man-classless-ipv6-05 happening again. right? :) "I'd like to use all the bits in my address as I see fit for my purposes" On Wed, Nov 11, 2020 at 2:03 AM Gyan Mishra <hayabusagsm@gmail.com> wrote: > > Going this route allowing for shorter prefix <64 but not allowing the >64 > due to the race to bottom contentious debate. This would definitely solve > the issue at hand. > > The variable slaac draft solution allows for both longer and shorter > prefixes. I can update it so it only allows for shorter prefixes so this > draft can progress. > > https://datatracker.ietf.org/doc/draft-mishra-6man-variable-slaac/ > > > On Wed, Nov 11, 2020 at 1:51 AM Gyan Mishra <hayabusagsm@gmail.com> wrote: > >> 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 >> >> -- > > <http://www.verizon.com/> > > *Gyan Mishra* > > *Network Solutions A**rchitect * > > > > *M 301 502-134713101 Columbia Pike *Silver Spring, MD > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- >
- Extending a /64 otroan
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 otroan
- Re: Extending a /64 otroan
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 Alexandre Petrescu
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Ca By
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Gyan Mishra
- Re: Extending a /64 otroan
- Re: Extending a /64 JORDI PALET MARTINEZ
- RE: [EXTERNAL] Re: Extending a /64 Manfredi (US), Albert E
- Re: [EXTERNAL] Re: Extending a /64 Mark Smith
- RE: [EXTERNAL] Re: Extending a /64 Manfredi (US), Albert E
- Re: Extending a /64 Brian E Carpenter
- Re: [EXTERNAL] Re: Extending a /64 Gyan Mishra
- Re: [EXTERNAL] Re: Extending a /64 Mark Smith
- Re: Extending a /64 otroan
- Re: [EXTERNAL] Extending a /64 otroan
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 otroan
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 otroan
- Re: Extending a /64 Philip Homburg
- Re: [EXTERNAL] Extending a /64 Gyan Mishra
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 JORDI PALET MARTINEZ
- Re: Extending a /64 Pascal Thubert (pthubert)
- Re: Extending a /64 George Michaelson
- Re: Extending a /64 Gyan Mishra
- Re: Extending a /64 Gyan Mishra
- Re: Extending a /64 Christopher Morrow
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 otroan
- Re: Extending a /64 Christopher Morrow
- Re: Extending a /64 Brian E Carpenter
- Re: Extending a /64 Gyan Mishra
- Re: Extending a /64 Gyan Mishra
- Re: Extending a /64 Alexandre Petrescu
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Mikael Abrahamsson
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Mikael Abrahamsson
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 otroan
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 otroan
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 S Moonesamy
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Brian E Carpenter
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 Brian E Carpenter
- Re: Extending a /64 Nick Hilliard
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 Nick Hilliard
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Gyan Mishra
- Re: Extending a /64 Brian E Carpenter
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Brian E Carpenter
- Re: Extending a /64 JORDI PALET MARTINEZ
- RE: [EXTERNAL] Re: Extending a /64 Manfredi (US), Albert E
- Re: Extending a /64 Gyan Mishra
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Nick Hilliard
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Nick Hilliard
- Re: Extending a /64 JORDI PALET MARTINEZ
- Re: Extending a /64 Simon Hobson
- Re: Extending a /64 Joel M. Halpern
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Joel M. Halpern
- Re: Extending a /64 Alexandre Petrescu
- Re: Extending a /64 Alexandre Petrescu
- RE: Extending a /64 Da Silva, Saulo
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Templin (US), Fred L
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Alexandre Petrescu
- Re: Extending a /64 Behcet Sarikaya
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Joel M. Halpern
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Templin (US), Fred L
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Templin (US), Fred L
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Tony Whyman
- RE: Extending a /64 Da Silva, Saulo
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 Mark Smith
- Why this is broken [was Re: Extending a /64] Brian E Carpenter
- RE: [EXTERNAL] Why this is broken [was Re: Extend… Templin (US), Fred L
- Re: [EXTERNAL] Why this is broken [was Re: Extend… Matthew Petach
- Re: Why this is broken [was Re: Extending a /64] Tony Whyman
- RE: [EXTERNAL] Re: Extending a /64 Manfredi (US), Albert E
- Re: Why this is broken [was Re: Extending a /64] Brian E Carpenter
- Re: Extending a /64 David Farmer
- Re: Extending a /64 Brian E Carpenter
- Re: Extending a /64 (ATN/IPS worked example) Tony Whyman
- Re: Extending a /64 Tony Whyman
- Re: Why this is broken [was Re: Extending a /64] Tony Whyman
- Re: Extending a /64 (ATN/IPS worked example) Philip Homburg
- Re: Extending a /64 (ATN/IPS worked example) Tony Whyman
- Re: Extending a /64 David Farmer
- Re: Extending a /64 (ATN/IPS worked example) Philip Homburg
- Re: Extending a /64 Tony Whyman
- Re: [EXTERNAL] Why this is broken [was Re: Extend… Behcet Sarikaya
- Re: Extending a /64 Simon Hobson
- Re: Cellphones in aircraft [was: Why this is brok… Simon Hobson
- RE: [EXTERNAL] Why this is broken [was Re: Extend… Templin (US), Fred L
- Re: [EXTERNAL] Why this is broken [was Re: Extend… Behcet Sarikaya
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 (ATN/IPS worked example) Brian E Carpenter
- Re: Why this is broken [was Re: Extending a /64] Matthew Petach
- RE: [EXTERNAL] Re: Why this is broken [was Re: Ex… Templin (US), Fred L
- Re: Extending a /64 (ATN/IPS worked example) Templin (US), Fred L
- Re: Extending a /64 (ATN/IPS worked example) Brian E Carpenter
- Re: Extending a /64 (ATN/IPS worked example) Brian E Carpenter
- RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Templin (US), Fred L
- Re: Extending a /64 (ATN/IPS worked example) Templin (US), Fred L
- Re: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Brian E Carpenter
- Re: Extending a /64 (ATN/IPS worked example) Brian E Carpenter
- RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Templin (US), Fred L
- RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Templin (US), Fred L
- RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Templin (US), Fred L
- RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Manfredi (US), Albert E
- RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Templin (US), Fred L
- Re: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Philip Homburg
- RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Manfredi (US), Albert E
- RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Templin (US), Fred L
- RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worke… Templin (US), Fred L
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 (ATN/IPS worked example) Michael Richardson
- Re: Extending a /64 (ATN/IPS worked example) Michael Richardson
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 (The most welcome comment) Tony Whyman
- Re: Why this is broken [was Re: Extending a /64] Behcet Sarikaya
- Re: Extending a /64 (The most welcome comment) Brian E Carpenter
- RE: [EXTERNAL] Re: Extending a /64 (The most welc… Manfredi (US), Albert E
- Re: Extending a /64 Michael Richardson
- Re: Extending a /64 (The most welcome comment) Templin (US), Fred L
- RE: Extending a /64 (The most welcome comment) Manfredi (US), Albert E
- Re: Extending a /64 (The most welcome comment) Brian E Carpenter
- RE: [EXTERNAL] Re: Extending a /64 (The most welc… Templin (US), Fred L
- Re: Extending a /64 (The most welcome comment) David Farmer
- Re: Extending a /64 Michael Richardson
- Re: Why this is broken [was Re: Extending a /64] Michael Richardson
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 Mark Smith
- Re: [EXTERNAL] Re: Extending a /64 (The most welc… Tony Whyman
- RE: [EXTERNAL] Re: Extending a /64 (The most welc… Pascal Thubert (pthubert)
- Re: [EXTERNAL] Re: Extending a /64 (The most welc… Tony Whyman
- Re: Extending a /64 Nick Hilliard
- Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Tony Whyman
- Re: [**EXTERNAL**] Re: Extending a /64 Mudric, Dusan
- Re: [**EXTERNAL**] Re: Extending a /64 Tony Whyman
- Re: Extending a /64 Nick Hilliard
- Re: Extending a /64 (The most welcome comment) Templin (US), Fred L
- Re: [**EXTERNAL**] Re: Extending a /64 tom petch
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 Nick Hilliard
- RE: [EXTERNAL] Re: Extending a /64 Manfredi (US), Albert E
- Re: Extending a /64 Mark Smith
- Re: Extending a /64 Philip Homburg
- Re: Extending a /64 Nick Hilliard