Re: [v6ops] Documentation Prefixes for ULA

Owen DeLong <owen@delong.com> Sat, 30 March 2013 05:56 UTC

Return-Path: <owen@delong.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 E3F6E21F8F08 for <v6ops@ietfa.amsl.com>; Fri, 29 Mar 2013 22:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.463
X-Spam-Level:
X-Spam-Status: No, score=-2.463 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sd-dk68WwKBk for <v6ops@ietfa.amsl.com>; Fri, 29 Mar 2013 22:56:34 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7C321F8E3C for <v6ops@ietf.org>; Fri, 29 Mar 2013 22:56:33 -0700 (PDT)
Received: from [IPv6:2620::930:0:ca2a:14ff:fe3e:d024] ([IPv6:2620:0:930:0:ca2a:14ff:fe3e:d024]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.1) with ESMTP id r2U5qgdQ011795 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 29 Mar 2013 22:52:42 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com r2U5qgdQ011795
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1364622762; bh=ebOmLwIL6MnY82XR2ohKG+IkXTQ=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=SKW7hcTXMKU0HUXcnYHt5Sb2pbcJthcEQEqNgUZqU590pxe+MPyl144uRUcd+sulz 3VuVeGXfWyc5bb50FadAO/TrktKIwIgOyFdFWKsm73Es+kZ/0IxfpNANjbmNdwkkE3 1tPQBDhjTtpiEDWu8j8xeaITqqtBNSmAnrJmlufU=
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <51563599.2040808@umn.edu>
Date: Fri, 29 Mar 2013 22:51:53 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <031BFC1A-0A5E-488A-A070-7B0CE53FC387@delong.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6EC275@nkgeml506-mbx.china.huawei.com> <51534B90.9040102@gmail.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6EC98F@nkgeml506-mbx.china.huawei.com> <B3504D2C-05C0-4B5D-9882-F02FA6FFD5BF@delong.com> <51547A5C.8030409@gmail.com> <895761CC-A25C-4FE4-84AD-76325ED8095A@delong.com> <B43DED58-886C-4096-895B-0CE698ED873C@muada.com> <5A1AF2E3-728F-467D-BE05-914C11CF220C@delong.com> <CAEF08F8-9468-4C4D-A3B3-4C772EC288C7@muada.com> <DFA8BFA4-2086-40B8-9F35-9155990E14B0@delong.com> <51563599.2040808@umn.edu>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.1499)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [IPv6:2620:0:930::200:2]); Fri, 29 Mar 2013 22:52:42 -0700 (PDT)
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Documentation Prefixes for ULA
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 30 Mar 2013 05:56:35 -0000

On Mar 29, 2013, at 17:45 , David Farmer <farmer@umn.edu> wrote:

> On 3/29/13 17:35 , Owen DeLong wrote:
>> This is now an ID available at:
>> 
>> http://www.ietf.org/id/draft-delong-ula-example-00.txt
>> 
>> Unless there is objection, the next version will incorporate the changes suggested by Iljitsch.
> 
> fd00:2001:db8::/48 should remain a valid ULA prefix as defined in RFC 4193, but you might want to suggest it may be reasonable to establish local policy not to use it, even though it remains valid ULA prefix.
> 
>> Are there any other changes people would like to see?
> 
> As for fc00:2001:db8::/48, I would add something like the follow to what you said;
> 
>   If fc00::/8 were defined similar to contemplated in
>   [draft-ietf-ipv6-ula-central] or [draft-hain-ipv6-ulac],
>   fc00:2001:db8::/48 should be reserved in such a registry, if such a
>   registry were ever created for fc00::/8.
> 

Actually, I would rather leave it as is. If the travesty of ULA-C ever comes to be, then
I would not want to limit the authors options with this older document. Instead, I would
expect them to consider this reservation and make a decision whether a documentation
prefix within that space is desirable. If so, then it has already been set aside for their
convenience. If not, then this becomes yet another piece of road kill on the information
super highway.

> Where draft-ietf-ipv6-ula-central and draft-hain-ipv6-ulac would be Informative References.

I'd rather not make informative references to expired drafts if I can avoid it.

> Since it has come up, is there any interest in moving forward some from of ULA-C?

Not from me there isn't.

> Owen, has your views on the utility of registered ULA softened?

Not in the least. Personally, I'd rather eliminate ULA altogether, but given the current bad
situation, not having a documentation prefix is likely to make it worse. As such, this seeks
to use the art of the possible to minimize the damage.

Owen