Re: [v6ops] draft-moreiras-v6ops-rfc3849bis-00

"Fred Baker (fred)" <> Wed, 21 August 2013 16:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8B5CB11E825B for <>; Wed, 21 Aug 2013 09:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -109.249
X-Spam-Status: No, score=-109.249 tagged_above=-999 required=5 tests=[AWL=-1.115, BAYES_00=-2.599, FRT_LOLITA1=1.865, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AvcVRZcRYl+s for <>; Wed, 21 Aug 2013 09:35:15 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id F3D4E11E8250 for <>; Wed, 21 Aug 2013 09:35:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=8112; q=dns/txt; s=iport; t=1377102915; x=1378312515; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=bnn+1/nwtCczDtUYClNYMAicGYCtvwl6aGifwJiydoQ=; b=cEgNQj0skbWoBk5kTsoBapIxwiTHmke5K60Cw2nPmY4XW3T6AYJQpoE7 xiYG/BD6OXj47POgjsGfruDPFl79sPwyK3Pndgjr3AA4GYi0nNP9/Eaf7 zGf2KC4iBKiv68bsGVJaFWQLHTaAGHgJui2Sk2H0IXVTn/67xPTRJ2eaw k=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="4.89,929,1367971200"; d="asc'?scan'208"; a="250071278"
Received: from ([]) by with ESMTP; 21 Aug 2013 16:35:12 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id r7LGZCev028439 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 21 Aug 2013 16:35:12 GMT
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Wed, 21 Aug 2013 11:35:12 -0500
From: "Fred Baker (fred)" <>
To: "George, Wes" <>
Thread-Topic: [v6ops] draft-moreiras-v6ops-rfc3849bis-00
Thread-Index: AQHOnoxnJQHdXvZNRkyDsJ3Wlb23ag==
Date: Wed, 21 Aug 2013 16:35:11 +0000
Message-ID: <>
References: <> <> <> <20130819123450.GY65295@Space.Net> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/signed; boundary="Apple-Mail=_22CD4DC3-4F26-41B7-AE04-CF3396348765"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Alejandro Acosta <>, "" <>, " WG" <>
Subject: Re: [v6ops] draft-moreiras-v6ops-rfc3849bis-00
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 21 Aug 2013 16:35:20 -0000


On Aug 21, 2013, at 6:33 AM, "George, Wes" <>

> The main problem with extending 2001:db8::/32 to a /29, or allocating 2xxx:db8::/xx is that it requires everyone to make changes to their Martian routing and packet filters, unlike pulling something from outside of 2000::/3. I don't view that as "less expensive", at least operationally.

> Also, if we're talking about your heartburn with a fairly large requested prefix (e.g. a /20 or /27 or whatever), that lends support to the idea of reusing space that otherwise is likely to become the IPv6 version of IPv4 Class E space (e.g. 6bone space, or 0200::) - formerly reserved, now reclaimable, but unusable as "normal" space on account of currently existing filters (and probably some dumb implementation hardcoding of "invalid" space).

Well, that is how we came up with; that was the ARPANET's allocation. He could include that in the IANA section of the 6man draft as another alternative, and come to that conclusion in 6man.

Understand my heartburn, please. To my mind, there are two arguments for IPv6 deployment: more addresses, and operational simplicity. When Axel Clauberg talks about his Terastream architecture, he shows an interesting slide in which he identifies the set of technologies in use in his network and which he has to manage, and he observes that there is nothing in it that can't be replaced by one of four protocol technologies - IPv6, optical communications, a management architecture (for which he selects NetConf), and an overlay architecture (for which he selects L2TPv3/IPv6). He figures he is saving operational expense by converting his network to exactly that set of technologies. When I talk about heartburn, I'm talking about things that chew up address space unnecessarily (the difference between "need" and "want") or which add complexity - of which the random filters you comment on are an example.

> Thanks,
> Wes
>> -----Original Message-----
>> From: [] On Behalf
>> Of Owen DeLong
>> Sent: Monday, August 19, 2013 1:52 PM
>> To: Fred Baker (fred)
>> Cc: Alejandro Acosta;; WG
>> Subject: Re: [v6ops] draft-moreiras-v6ops-rfc3849bis-00
>> I think all of Fred's recommendations below are spot on. I support the
>> changes and I like the idea of 2001:db0::/28.
>> In such a case, should we stick with fc00:db8::/44 or should we consider
>> fc00:db0::/28 for parity? I'm OK either way, just looking to minimize
>> potential confusion and wondering if the tradeoff in space is worth
>> while or not. What do others think?
>> Owen
>> On Aug 19, 2013, at 10:38 , "Fred Baker (fred)" <> wrote:
>>> On Aug 19, 2013, at 5:34 AM, Gert Doering <> wrote:
>>>> 2001:db8 came from APNIC, that's why :-) - their delegated file lists
>>>> apnic|AU|ipv6|2001:db0::|32|20031112|allocated
>>>> apnic|AU|ipv6|2001:dc0::|32|20030124|assigned
>>>> so an extention to /29 would technically be possible, to a /28 won't.
>>> Hmm. Tell me about 2001:da0:: and 2001:d80::? Per
>> latest
>>>> apnic|AU|ipv6|2001:7fa:b::|48|20050922
>>>> apnic|AU|ipv6|2001:7fa:c::|48|20050922
>>>> apnic|AU|ipv6|2001:7fa:d::|48|20050922
>>>> apnic|AU|ipv6|2001:7fa:e::|48|20050922
>>>> apnic|ID|ipv6|2001:7fa:f::|48|20050929
>>>> apnic|CN|ipv6|2001:7fa:10::|48|20060531
>>>> apnic|AU|ipv6|2001:7fa:11::|48|20061031
>>>> apnic|AU|ipv6|2001:dc0::|32|20030124
>>>> apnic|TW|ipv6|2001:dc1::|32|20030331
>>>> apnic|JP|ipv6|2001:dc2::|32|20030529
>>>> apnic|JP|ipv6|2001:dc3::|32|20030619
>>> To my small mind, that suggests 2001:d80::/26 (64 prefixes),
>> 2001:da0::/27 (32), 2001:db0::/28 (16), or 2001:db8::/29 (8). Shorter
>> than /26 includes 2001:dc0:: and 2001:de0::, which have been allocated.
>> The neighborhood, however, includes 2001:db8::, which we already use. I,
>> for one, would like to see one documentation range, at least for the
>> global unicast address space, which is to say a prefix shorter than and
>> including 2001:db8::/32.
>> trends/apnic-resource-range#IPv6Allocation notes that 2001:DB8::/29 is
>> reserved and by definition available.
>>> I note that we are not discussing the recommendation per se; we are
>> narrowing in on the length of the prefix. Unless someone disagrees, I
>> think we have pretty much agreed that something shorter than /32 makes
>> sense.
>>> Here's my suggestion. The 6man chairs tell me that RFC 3489 was their
>> work group product, so it's replacement should be. I'd suggest
>> respinning the draft as draft-moreiras-6man-rfc3849bis (and tell
>> that it replaces this one). You want to do two
>> separate things:
>>> a) argue for a shorter prefix in 2000::/3, and make a separate-but-
>> analogous argument for a prefix in fc00::/8.
>>> In those, focus on need, not want. "We designed a lab that has 2^128
>> different addresses in it, we obviously need the entire IPv6 address
>> space" doesn't follow. Say what you *need* and why you *need* it. While
>> the request was for a /20, I have not heard a cogent argument for a /26
>> or shorter, I heard that there was a training lab somewhere that
>> required a /27 (32 /32s) but have not heard that the intent of the lab
>> could not have been done with 16 /32s, and observe that a nibble
>> boundary would suggest a /28 (16 /32s).
>>> b) in the IANA considerations section, note:
>>> b.1) the availability of 2001:d80::/26, 2001:da0::/27, 2001:db0::/28,
>> or 2001:db8::/29
>>> b.2) the suggestion of fc00:db8:?::/44, which I think we more or less
>> agreed to in the thread
>>> b.3) the fact that this would also affect
>> special-registry.xhtml#iana-ipv6-special-registry-1
>>> _______________________________________________
>>> v6ops mailing list
>> _______________________________________________
>> v6ops mailing list
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.

	• Make things as simple as possible, but not simpler.
Albert Einstein