Re: [v6ops] New Version Notification for draft-baker-v6ops-cpe-autoconfigure-00.txt

Fred Baker <fredbaker.ietf@gmail.com> Sat, 17 June 2017 21:21 UTC

Return-Path: <fredbaker.ietf@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 4522D129C1C for <v6ops@ietfa.amsl.com>; Sat, 17 Jun 2017 14:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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 ONnLh_gljtWC for <v6ops@ietfa.amsl.com>; Sat, 17 Jun 2017 14:21:12 -0700 (PDT)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (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 4626D129C1A for <v6ops@ietf.org>; Sat, 17 Jun 2017 14:21:12 -0700 (PDT)
Received: by mail-ot0-x230.google.com with SMTP id y47so26556280oty.0 for <v6ops@ietf.org>; Sat, 17 Jun 2017 14:21:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kR6cmrm6Y5eZM6NxtmkNest0wWCHdGyIjJDbi6uj80g=; b=uAJbFO9yfI071DCGXvTFmyVx4A/YarEGLWXZ1E2RDKUw9XKtJO6rT1gOcxuZf39Aan QASzDbCammsxXPoUbpjJf4QWUTzGYHPNj4Yk7C77Hk5lt9CUaOPAHrK+JpuqDpfU0DMX f+7kyjwPAqJ6260dW/coec37jdufDvSID0c4kT29dw1N/5P/E2e/hf9P26gXYy4fGmuc DjJitKeDeQqjQMX6IzdPDAvDVw09+zX10QkQwTyEvAys+1RrNv/Pbh8s+08oT1TggYUf Z1x0TPJt53uqfWglg9myvDohDlrtZD29HpUHax+lSyTU5EhsAJER7T6Zm4Rl1c3eZGXg Oilw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kR6cmrm6Y5eZM6NxtmkNest0wWCHdGyIjJDbi6uj80g=; b=etJy/uvHRzmCG5eUWKX5hTQl5UyufvkTrTJl/+O30QQWpcVPMUqtdhajcIlsWfRU/n +XQT1aC1/KW/6VSAP505js+CYc/PKx9Oqtl29Kz+GBeopFRbqX2LYbWER8a7d3aN/ywb JRguCAYOxxqZhiUNSoCoZHwb2PnnzomGcOdbEkQzLJUBm62M8XVQJNfSBAkhbHl5+LXk x2GltB7jKi45N/n7IO5L37qUyxZxKGE+HFSRX1cpDAecbLkXltJA2cr2+AEIFQT6itC5 YJ0LXboBih9THp634/s0vZHABsbFZCkF9qBl3XpFmM84dzTBRz+Xk8ScMJelp5k9cPEo NM4w==
X-Gm-Message-State: AKS2vOwOa58MVv7mxpLT1chpwr9Bi3OVTln58fOaepDKLPsGIdeEAYBU OpiAnehduNBXXcjxcMg=
X-Received: by 10.157.11.115 with SMTP id p48mr140620otd.165.1497734471485; Sat, 17 Jun 2017 14:21:11 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1e::16e5? ([2600:8802:5600:1e::16e5]) by smtp.gmail.com with ESMTPSA id j62sm3306440otc.50.2017.06.17.14.21.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Jun 2017 14:21:10 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <149773408722.14141.1243099989313191246.idtracker@ietfa.amsl.com>
Date: Sat, 17 Jun 2017 14:21:09 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <334ACBB6-C438-410B-81D7-49269AC51004@gmail.com>
References: <149773408722.14141.1243099989313191246.idtracker@ietfa.amsl.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CZr3xFSsgX3iByJhrTD8hnSoNk8>
Subject: Re: [v6ops] New Version Notification for draft-baker-v6ops-cpe-autoconfigure-00.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: Sat, 17 Jun 2017 21:21:14 -0000

In discussion with John Brzozowski, he expressed a concern that CPEs don't come "out of the box preconfigured for IPv6" as they often do for IPv4. I had a recent experience with a new router at my home that made the point in my mind; IPv6 was an "advanced configuration", and the difference between "auto-configure" and "auto-detect" was a little lost on me. 

So I have a question. Do we need to spell this out for CPE vendors? I have spliced together a draft on the topic. I'd welcome comments that might improve it, especially if I have something egregiously wrong. Second, I'm curious whether the working group thinks we need this.

Your thoughts?


> On Jun 17, 2017, at 2:14 PM, internet-drafts@ietf.org wrote:
> 
> 
> A new version of I-D, draft-baker-v6ops-cpe-autoconfigure-00.txt
> has been successfully submitted by Fred Baker and posted to the
> IETF repository.
> 
> Name:		draft-baker-v6ops-cpe-autoconfigure
> Revision:	00
> Title:		Requirements for a Zero-Configuration IPv6 CPE
> Document date:	2017-06-17
> Group:		Individual Submission
> Pages:		6
> URL:            https://www.ietf.org/internet-drafts/draft-baker-v6ops-cpe-autoconfigure-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-baker-v6ops-cpe-autoconfigure/
> Htmlized:       https://tools.ietf.org/html/draft-baker-v6ops-cpe-autoconfigure-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-baker-v6ops-cpe-autoconfigure-00
> 
> 
> Abstract:
>   This note is a breif exploration of what is required for a CPE to be
>   auto-configurable from the perspective on an ISP or other upstream
>   network.  It assumes that the CPE may also be IPv4-capable (probably
>   using NAPT), but that the requirements for that are well understood
>   and need no further specification.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>