Re: draft-bourbaki-6man-classless-ipv6-00

james woodyatt <jhw@google.com> Wed, 14 June 2017 18:09 UTC

Return-Path: <jhw@google.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 68906129408 for <ipv6@ietfa.amsl.com>; Wed, 14 Jun 2017 11:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 uwxGxMoHRT6O for <ipv6@ietfa.amsl.com>; Wed, 14 Jun 2017 11:09:55 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 A323D1293EE for <ipv6@ietf.org>; Wed, 14 Jun 2017 11:09:55 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id l89so3980355pfi.2 for <ipv6@ietf.org>; Wed, 14 Jun 2017 11:09:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=55NT8dh28vI+cWcoRg5aREIqB+JLGC5e8DLM9T4ZoGc=; b=OA9tb59aC7snELcauO4+BFHxdu8Kp0dLxe1fy2D2WjAG/98mLTo4M1X5mtVYgafeoF T7kCFV0x4l3W0WcmF3MzYXJZNx7YftzbXl7KSJ92wxI5jaPqHB5i22Ue62rK+284eWXZ WxgLOGO5gPj9CoxzTX2v0F0hJTbVjwn5b6SN6JYeKf6bnEbOWNymFeWSmKx8o3IrOVgi 9pcbmcrf4oCsXRAad+Gqnpr4DK5PoiJJpbQO+USZiK7itt9vsOyygRDN8iw4RUC+6dbk f86/LbLiBABkNXvp8lMtVsTUlLs3Lr++mX99eeRS2im2xuhR0kCxxtkPUwcK/MbmN53C YBDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=55NT8dh28vI+cWcoRg5aREIqB+JLGC5e8DLM9T4ZoGc=; b=KkkkEFmdq0y1bd7vnmFNMORMSy/bIZaKV402m9UxbQI2B8vWu/vr1HPtbRoYT1zIHe WfEd6+e28oVvftamTqp8k10dX1JK9tpK/0s5lH7kbfzBMZ4zjkN0oa61U9+0P89drepK Famzi/wN8nvTGKjp0OgnT25XMgemriKSaeYeOVZR1JrhE/W9+bglHJTCNMF+GyLcoNnd KLECvCloij8CX0EZfTyc1WQZptXNOgJu8/PpvMpln7Qeqt+Ztr5jR907CrpF5r968iP3 ToV+NkGCQ//8NZjcUjQIHOeZ3IBUzzVGV3pn/gn7Dzo+vsiGSKBqrCjFncCQaDPNLdWI 2LDA==
X-Gm-Message-State: AKS2vOxzUrwFtMwdRm8VFJsI6l2zOqmeou8QqoxqPdymDG2vyWuN6w/P 6du+lz5lrlXr8AgE+/t9tQ==
X-Received: by 10.84.197.3 with SMTP id m3mr1476861pld.40.1497463794865; Wed, 14 Jun 2017 11:09:54 -0700 (PDT)
Received: from ?IPv6:2620::10e7:10:170:a37a:4a61:ea80? ([2620:0:10e7:10:170:a37a:4a61:ea80]) by smtp.gmail.com with ESMTPSA id e124sm1011482pgc.17.2017.06.14.11.09.53 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Jun 2017 11:09:53 -0700 (PDT)
From: james woodyatt <jhw@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_478C920F-8353-4567-B55E-64CBDDD93037"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
Date: Wed, 14 Jun 2017 11:09:58 -0700
References: <E02C4C99-155A-4358-A845-F00F8BB071C1@employees.org> <b3ca5271-21b1-ab33-2dff-82735ebe9128@gmail.com> <235143da452c4ff4aec39a26ba918e7e@XCH15-06-11.nw.nos.boeing.com> <1489a50a-2616-f9ac-4109-16c595e15f90@gmail.com> <FA3032F9-F44B-45B4-9AFF-01EBC84F1448@employees.org> <b1c5c13d-ef69-ef30-546c-9178a2655caf@si6networks.com> <391c730c-fa75-7596-bb6b-383ea6583131@gmail.com> <0b57c999-b5df-8a44-e3fd-55cee628f3f3@si6networks.com> <20170614092327.GB30896@gir.theapt.org> <E61AFFF1-0354-41EE-8E11-50433B26BAF7@employees.org> <20170614094034.GC30896@gir.theapt.org> <A7502902-245B-499B-916B-28630CD5A824@employees.org> <6c4157da7039438981db0f4ba46df916@XCH15-06-11.nw.nos.boeing.com>
To: 6man WG <ipv6@ietf.org>
In-Reply-To: <6c4157da7039438981db0f4ba46df916@XCH15-06-11.nw.nos.boeing.com>
Message-Id: <EB6160E5-0FB3-427E-BBE0-486A58FD0D82@google.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ZfZ3chm1S1WYpfKS9ILl_RxJ66Q>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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, 14 Jun 2017 18:09:57 -0000

On Jun 14, 2017, at 10:36, Manfredi, Albert E <albert.e.manfredi@boeing.com> wrote:
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of otroan@employees.org
>> 
>> What _problem_ does changing the 64 bit boundary solve for _you_?
> 
> A category of problems, such as creating hotspots with smartphones that have been allocated a single /64. A real-world situation, in which there's no conceivable reason to have to go hat in hand to service provider, asking for more /64s. […]

This category of problem is about connecting *routers* (not hosts) to the Internet via RFC 7278.

If all you’re connecting at the hotspot are hosts, then why would you need more than one subnet? And if you need more than one subnet— for some premium mobile hotspot thingie I guess— why not use more than one UE?

"What is the killer app for connecting *routers* to the Internet using a /64 subnet sharing scheme?” I ask, bearing in mind that you can’t be talking about 6LBR, because RFC 4944 fixes the subnet prefix length at 64 bits for all 6LO-over-link specifications. And why isn’t simply using IPv6/NAT the simpler and more straightforward solution to your category of problems?

Shorter james: I’m not ready to believe you have any problems in this category. Please provide a clear example.


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>