IETF Logo Mail Archive

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

Tim Chown <Tim.Chown@jisc.ac.uk> Mon, 19 June 2017 09:43 UTC

Return-Path: <tim.chown@jisc.ac.uk>
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 3F164124E15 for <v6ops@ietfa.amsl.com>; Mon, 19 Jun 2017 02:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 kWZzc6utUK1e for <v6ops@ietfa.amsl.com>; Mon, 19 Jun 2017 02:43:33 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EB22126DED for <v6ops@ietf.org>; Mon, 19 Jun 2017 02:43:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1497865410; h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=hdhy/pKUOr9uNVbmpMLCYBr8utDiMnGzRLFhuES9Vik=; b=XmhcJjAmS+vZap66B6MpNOGXaJ57QLRuG/QHbLyTkLRJrBf8jcORc4uC1aeT4HVIOyJ0O3mQZMTmsSsK60chzQObaJ5RcceK+XZTiIDwUzHCuS8I0ax448I/pf28IHtzLkcY/OGWUVQTGaN6YaI43TgiVFohBqZxjJIr8wVerW0=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0244.outbound.protection.outlook.com [213.199.154.244]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-65-L7jFh1N9MWWBgmI5AcBXjA-1; Mon, 19 Jun 2017 10:43:24 +0100
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1137.eurprd07.prod.outlook.com (10.163.188.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.6; Mon, 19 Jun 2017 09:43:22 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::a0d2:23ea:f4eb:e7bd]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::a0d2:23ea:f4eb:e7bd%14]) with mapi id 15.01.1199.007; Mon, 19 Jun 2017 09:43:22 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Fred Baker <FredBaker.IETF@gmail.com>
CC: IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] New Version Notification for draft-baker-v6ops-cpe-autoconfigure-00.txt
Thread-Index: AQHS56+2wt4mzGA7yUeFvbr0tMKFnKIr8ZqA
Date: Mon, 19 Jun 2017 09:43:22 +0000
Message-ID: <555ACC46-7A71-4CA7-82AA-BDB8B02233F1@jisc.ac.uk>
References: <149773408722.14141.1243099989313191246.idtracker@ietfa.amsl.com> <334ACBB6-C438-410B-81D7-49269AC51004@gmail.com>
In-Reply-To: <334ACBB6-C438-410B-81D7-49269AC51004@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3273)
x-originating-ip: [2001:a88:d510:1101:d525:b649:6674:a33c]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1137; 20:xQoN6Tq+S4cwj5IvKooxl+Ldts1z+zLfzuEr5OY3/96J6xyf2gVkTypRedSFAwp4Daj49tBnVSPXwBD7P6CEc8JVTKzDwHzz86j/4AP50OIfxc6CR9pcTpElJwH9sui7A9yoi1aF9uNZcl196F8JHoTyjZkDUe2CmbK9p6KPACw=
x-ms-office365-filtering-correlation-id: ba4a3ed0-38fe-4ccd-5360-08d4b6f7a032
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:AM3PR07MB1137;
x-ms-traffictypediagnostic: AM3PR07MB1137:
x-microsoft-antispam-prvs: <AM3PR07MB11371A286330BC79B7F711C2D6C40@AM3PR07MB1137.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(10201501046)(3002001)(93006095)(93001095)(6041248)(20161123564025)(20161123560025)(20161123555025)(20161123558100)(20161123562025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM3PR07MB1137; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM3PR07MB1137;
x-forefront-prvs: 0343AC1D30
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39840400002)(39450400003)(39400400002)(39410400002)(377424004)(377454003)(57704003)(24454002)(36756003)(6512007)(6916009)(2950100002)(42882006)(5660300001)(86362001)(6506006)(50986999)(76176999)(99286003)(6436002)(6306002)(38730400002)(74482002)(966005)(14454004)(53936002)(478600001)(2900100001)(305945005)(72206003)(7736002)(6246003)(110136004)(230783001)(57306001)(3660700001)(8676002)(50226002)(2906002)(25786009)(53546009)(81166006)(3280700002)(8936002)(81156014)(5250100002)(6486002)(82746002)(102836003)(189998001)(6116002)(83716003)(33656002)(4326008)(229853002)(39060400002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1137; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <D78DA20C6885BF41B660A0A41C7F47C8@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jun 2017 09:43:22.5818 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1137
X-MC-Unique: L7jFh1N9MWWBgmI5AcBXjA-1
Content-Type: text/plain; charset="WINDOWS-1252"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/U1kQfvJHLK1MtLYQBCudZQy4yqQ>
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: Mon, 19 Jun 2017 09:43:36 -0000

Hi,

> On 17 Jun 2017, at 22:21, Fred Baker <FredBaker.IETF@gmail.com> wrote:
> 
> 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?

It would be great if a document like this were not needed, but anecdotal evidence suggests that it is. 

Tim

>> 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
>> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email