Re: [v6ops] [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-09.txt

Lee Howard <lee@asgard.org> Thu, 17 August 2017 15:41 UTC

Return-Path: <lee@asgard.org>
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 E39871323AE for <v6ops@ietfa.amsl.com>; Thu, 17 Aug 2017 08:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.418
X-Spam-Level:
X-Spam-Status: No, score=-1.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 gnaghPPM2Vpr for <v6ops@ietfa.amsl.com>; Thu, 17 Aug 2017 08:41:16 -0700 (PDT)
Received: from atl4mhob20.registeredsite.com (atl4mhob20.registeredsite.com [209.17.115.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE2841321C7 for <v6ops@ietf.org>; Thu, 17 Aug 2017 08:41:14 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob20.registeredsite.com (8.14.4/8.14.4) with ESMTP id v7HFf9sg033784 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <v6ops@ietf.org>; Thu, 17 Aug 2017 11:41:09 -0400
Received: (qmail 21538 invoked by uid 0); 17 Aug 2017 15:41:09 -0000
X-TCPREMOTEIP: 68.100.68.25
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.1.160?) (lee@asgard.org@68.100.68.25) by 0 with ESMTPA; 17 Aug 2017 15:41:09 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Thu, 17 Aug 2017 11:41:03 -0400
From: Lee Howard <lee@asgard.org>
To: "STARK, BARBARA H" <bs7652@att.com>, Fred Baker <fredbaker.ietf@gmail.com>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>
Message-ID: <D5BB3045.8138C%lee@asgard.org>
Thread-Topic: [v6ops] [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-09.txt
References: <150158713179.9574.7767168468574012763@ietfa.amsl.com> <C9B5F12337F6F841B35C404CF0554ACB8AD0B6CC@dggeml509-mbx.china.huawei.com> <D5B9D8F6.811AD%lee@asgard.org> <B5B97D89-D2FF-4A6D-BE11-E1C1DC62EA16@consulintel.es> <0E0D8D4F-A487-4572-A7D2-C77635280329@gmail.com> <2D09D61DDFA73D4C884805CC7865E6114DC00555@GAALPA1MSGUSRBF.ITServices.sbc.com>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DC00555@GAALPA1MSGUSRBF.ITServices.sbc.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/NdxXVfFOa4fwTAHmbRjAY-UuKtg>
Subject: Re: [v6ops] [sunset4] I-D Action: draft-ietf-sunset4-gapanalysis-09.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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, 17 Aug 2017 15:41:18 -0000


On 8/17/17, 10:00 AM, "v6ops on behalf of STARK, BARBARA H"
<v6ops-bounces@ietf.org on behalf of bs7652@att.com> wrote:

>> The question I would ask is whether on-demand IPv4 makes sense.

>
>I think "on-demand IPv4" would be rather easy with PPPoE. Many (telco)
>ISPs are still using PPPoE, and there's still a lot of equipment and
>routers that support it.

That’s exactly how it reads in the gapanalysis draft: it makes sense for
PPPoE.

However, I will argue to both working groups that we should find an
operator who thinks this is a good idea. I hope we can get them to write
it up. If there is no such operator, we should remove the section (or at
most, footnote it as an idea somebody once thought of).


Lee