IETF Logo Mail Archive

Re: [v6ops] About draft-horley-v6ops-expand-doc

Fred Baker <fredbaker.ietf@gmail.com> Thu, 03 June 2021 06:09 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 BFB8A3A2B9F; Wed, 2 Jun 2021 23:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 xVROI306AgH3; Wed, 2 Jun 2021 23:09:01 -0700 (PDT)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 1F31F3A2BC1; Wed, 2 Jun 2021 23:09:00 -0700 (PDT)
Received: by mail-pf1-x42f.google.com with SMTP id t28so4080246pfg.10; Wed, 02 Jun 2021 23:09:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=e7wLpN0ikQHRPrp9k0ZbdjL2bJkjlCe7IB3LNqkDxNk=; b=m0HvvUKtGJn8qFC8DxpdDIr9zfvJarmhU9D2mWUyzti1Pdr3AFoiTJwG2DvB0m4SCa G43vujhx/hEhTYRelMI/Hiz9v7Z7xEFf7kKVwRVZsfh2lwoshcSMnHMFX6xjIOg2fBRh +hpUDEuEZ8XTSqTCd5Co77vpmpFpXfLET/EAK1JQ9d44I8z8UflqzoSkQr2v9KrzRYNH 1ug1r3XrKI/IFecE53/7FFVT685smekX5XjHhS2iV6s85Cvode9NlUBEMRUcIyLOOO3R cP1WqH47GH64r6Hlidtvrnb/RoDb7bB5tMf3QT5J7P7VLa7u5TlRAQL1bsFKiet6ujnL dfng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=e7wLpN0ikQHRPrp9k0ZbdjL2bJkjlCe7IB3LNqkDxNk=; b=SuS1zdvuxdNYUJluvexkGLH8L/0swCDVip7is6eZ87F3M9FNs5ZkJN4DDk2DCORGW2 Tr4pc2B9HiUwr26VYHAKmXYot7Sb/roHDgi5SdApW92FIIsuspTJneedTQ3MSP1KDDmd nK1E67lCbM3bxGPdORwHhbQ3ArqW9dqPi5Wqwa0ifkH0otyZWXrN5R+nJ8Wjzey4iI55 NHuS8PtfEjw6pPfGFkzjwqYl8wYWimr5PAoZWKeFEPQafzo+PPRyAgCLn7K5sH8ErlJ+ 27Bs/1ZspYGbkuMlR/xnoYKPn7a9/cQ8gQua1fgOuLXNpp/CP0PErbvaIsjz9plUxOuk t27g==
X-Gm-Message-State: AOAM5317g+R6LHsJcEgeiSxnfkCt6iu/oDFhj73C6EpUd9rROqtWU0Tz mZEzWoUdzGw8MDuhtxk01ArxNwfrLRo=
X-Google-Smtp-Source: ABdhPJzVrgNuHowNtBHFwEWAaNurns24RApNfo12YI9Re+h330LeFSIvzZUEIvgcieBc5AbGghLOyA==
X-Received: by 2002:a63:6343:: with SMTP id x64mr22428639pgb.130.1622700538890; Wed, 02 Jun 2021 23:08:58 -0700 (PDT)
Received: from smtpclient.apple ([2600:8802:5b00:bc1::1032]) by smtp.gmail.com with ESMTPSA id d15sm1075235pjr.47.2021.06.02.23.08.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 Jun 2021 23:08:58 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <09F5100B-5448-4A71-92E9-472E1AC7B811@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C6E50F8B-B449-4D5D-849C-3FFEBA636E53"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Date: Wed, 02 Jun 2021 23:08:56 -0700
In-Reply-To: <CAMGpriXFeRsjtOVFKLRhGMGLHE_m=DEAsb67nR=JrKwrtWFuGQ@mail.gmail.com>
Cc: Ed Horley <ed@hexabuild.io>, IPv6 Operations <v6ops@ietf.org>, "draft-horley-v6ops-expand-doc.all@ietf.org" <draft-horley-v6ops-expand-doc.all@ietf.org>
To: Erik Kline <ek.ietf@gmail.com>
References: <84C5D303-07C7-4E7B-8DB2-0593F9159831@cisco.com> <CAE=N4xcuA6-9t_TJCU0GBVZbci06z0f8S40a2aKu3Fh0MeyGOg@mail.gmail.com> <5722CD63-7039-4235-B064-53884FDE16F5@gmail.com> <CAMGpriXFeRsjtOVFKLRhGMGLHE_m=DEAsb67nR=JrKwrtWFuGQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/vTqMroGH2f4RIhpzfg3OVNq9K14>
Subject: Re: [v6ops] About draft-horley-v6ops-expand-doc
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 03 Jun 2021 06:09:16 -0000

There was a previous proposal to enlarge the documentation prefix; I don't recall the I-D. One of the arguments was that it needed to be useful to describe BGP exchanges in a multi-provider network, which would mean at minimum having something larger than a /32 for each of several networks in a worked example. I won't argue the case, but I note that it was raised.

> On Jun 2, 2021, at 4:31 PM, Erik Kline <ek.ietf@gmail.com> wrote:
> 
> On Wed, Jun 2, 2021 at 3:43 PM Fred Baker <fredbaker.ietf@gmail.com> wrote:
> 
> 
> > On May 24, 2021, at 8:01 AM, Ed Horley <ed@hexabuild.io> wrote:
> >
> > Am I don't this right?
> >       • unsure whether re-using the 6bone prefix is the best choice, any unicast prefix out of 2000::/3 could be used
> 
> I would strongly suggest using one in the IPv6 documentation prefix (2001:db8::/32 RFC3849) unless you have an excellent reason to do otherwise.
> 
> This was why I was interested in "just how big do we need".  For example, if 256 /32s are sufficient then a case might be made for expanding the doc prefix to 2001:d00::/24 ("dee hundred is the doc block", kind of thing =).
> 
> But, again, that requires knowing how much is *really* necessary.  (In the absurd case, we obviously can't allocate a 2nd IPv6 Internet just to document the workings of the 1st IPv6 Internet.  :-)

v2.23.0 | Report a Bug | By Email