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

Owen DeLong <> Tue, 13 August 2013 20:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C3BBB21E810A for <>; Tue, 13 Aug 2013 13:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id k8auyM2zRhBw for <>; Tue, 13 Aug 2013 13:51:22 -0700 (PDT)
Received: from ( [IPv6:2620:0:930::200:2]) by (Postfix) with ESMTP id 893E721E80EE for <>; Tue, 13 Aug 2013 13:51:22 -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 (8.14.2/8.14.1) with ESMTP id r7DKmUcX020965 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 13 Aug 2013 13:48:30 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 r7DKmUcX020965
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple;; s=mail; t=1376426910; bh=f+XZBawdIMjuZ2FZgS64MDiKHiI=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=r4MPWFboEckgYkEkBJhSiCLEckdRAvV1+wK2KY+CtuT9xaB+qKyagVQQKPvW0VUqp OE1uc8l4CkguNf+EpfYIsUBNQRjTwrEBw2UKkIijQqewpl0PRwRaar9DKoY9utKlI3 vMGYlauow7XexW2kzHedvsfkwsiiOrsq+11xg5Bk=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Owen DeLong <>
In-Reply-To: <>
Date: Tue, 13 Aug 2013 13:48:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <> <> <> <>
To: "George, Wes" <>
X-Mailer: Apple Mail (2.1508)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 ( [IPv6:2620:0:930::200:2]); Tue, 13 Aug 2013 13:48:30 -0700 (PDT)
Cc: "" <>
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: Tue, 13 Aug 2013 20:51:24 -0000

On Aug 13, 2013, at 12:58 , "George, Wes" <> wrote:

>> -----Original Message-----
>> From: Owen DeLong []
>> Sent: Tuesday, August 13, 2013 2:29 PM
>> To: George, Wes
>> Cc: Antonio M. Moreiras;
>> Subject: Re: [v6ops] draft-moreiras-v6ops-rfc3849bis-00
>> The original proposal for a larger doc prefix is all about being able to
>> write books and training scenarios that use a doc prefix and talk about
>> carving up larger chunks of address space.
> [WEG] The thing I don't understand about that is how carving x subnet blocks out of a /32 is different from carving x blocks out of a /48 or x blocks out of a /20 or whatever you start with as it concerns documentation. Other than the prefix lengths being somewhat longer, the examples of how to subnet, how to configure routing, etc still hold, don't they? AFAICT, as long as you don't end up subnetting below /64, there's really no issue. Yes, real routing policy likely won't pass a bunch of /64s, but for a lab such as what you detailed, and the subtending documentation that should work just fine, no? Especially given that the goal is to teach someone how to do something, instead of simply giving them something to copy with no understanding of what it's doing.

You and I know that it isn't. For the ab initio student, it's one more difference in the overwhelming pile of things being poured into their brain.

Trust me, while it isn't different for someone with experience, in my experience, it drives students crazy and they get wrapped around the axle on the differences in the examples and lose sight of what is being taught.

> For ab initio training,
>> trying to teach students that these ULA examples are not really
>> applicable to ULA, but should be used with GUA is very confusing and it
>> really does break their brains. Allocating a larger doc prefix would
>> help with this scenario a lot.
> [WEG] A point I'll concede, and one that should make it into the draft. :-)
>> Secondarily, I mentioned that while we were considering an additional
>> doc prefix, it might make sense to also look at allocating a third doc
>> prefix for creating ULA examples. I think this should come from the
>> fc00::/8 space which is currently unusable  anyway, and which would
>> allow examples describing the use of (and reasons not to use) ULA with a
>> prefix that would be easily identified if the examples were erroneously
>> copied into the real world.
>>>> I would prefer to choose an arbitrary prefix, inside or outside
>>>> 2000::/3, but that "looks like" a GUA, than use ULAs in the classes.
>>> [WEG] Might I suggest repurposing all or part of 0200::/7? (RFC4048).
>> Even if we don't officially allocate it as additional documentation
>> space, that seems a safe squat point for things like training, likely to
>> already be filtered by SPs as bogon space, etc.
>> Works for me.
>> I would suggest 0200:2000::/20 to fit with the other requestors' desire
>> for a /20. For my needs, even 0200:2200::/24 would be adequate.
> [WEG] at the risk of debating bikeshed colors, I would suggest perhaps using :db8:: for both the proposed GUA and ULA doc prefixes so that it serves as a visual cue.

I have no problem with that.

How about 02db:8000::/20 and fc00:0db8::/32?


P.S. love the disclaimer disclaimer.