Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-update-00.txt
Nick Buraglio <buraglio@forwardingplane.net> Tue, 07 November 2023 13:33 UTC
Return-Path: <buraglio@forwardingplane.net>
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 4F139C1FB864 for <v6ops@ietfa.amsl.com>; Tue, 7 Nov 2023 05:33:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forwardingplane.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVLw16xI0K4x for <v6ops@ietfa.amsl.com>; Tue, 7 Nov 2023 05:33:36 -0800 (PST)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE41EC1E4E5F for <v6ops@ietf.org>; Tue, 7 Nov 2023 05:33:36 -0800 (PST)
Received: by mail-qt1-x831.google.com with SMTP id d75a77b69052e-41cb76f3cf0so35844121cf.2 for <v6ops@ietf.org>; Tue, 07 Nov 2023 05:33:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forwardingplane.net; s=google; t=1699364015; x=1699968815; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=b6QUliqW3YZrvapRdq64J7dv/hOgoloLsGmSRy601+M=; b=cVfTOrVlFwg8HHQQ8eZ+u2jLP6MWSL69GB999H1XBbmOLofq2CWsxVwvi4NNk8JCa7 jTaTnNld6tUCQlrlXrbKq+wM9yHPLP0UPIF4LO1ysth+RTXsDfXgRBVcJuLfbC1fgsex 12b9pm7Hg1PQ/ScncY6NCZp0QEuvjrc1pdCCQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699364015; x=1699968815; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=b6QUliqW3YZrvapRdq64J7dv/hOgoloLsGmSRy601+M=; b=wz9mmbGmlaelRt9+OugEMFLw0KYujQro5P4q3hgChQaNjznk1uKffMDebBkV1u8vN7 2IrTzmHSQ/oQtsQQrrKETOJ6Hk909LgL/fkoJRD+QWxg+KCQdpI4112MJ78WywCOwW+2 6M4Mu6xSe7HOzgEn4yyLUjoOluNz9Ytj55Yl+VQ2SR6p6mA2f4L4C/c1MEFm9tJshRH1 Hfw0stBkpOGSHKAXs1jt0XdbVTQ4XZViMmLQ5GF6t5SBLQGgTUWqBa6FZH6Ep6IgixYr nLDTiqL20xQa3kcVgHNewH2EvQkPcHI26UXoHGr8tUg9+Y69LA2drxgu6n4NJwc0Mw9w SM+Q==
X-Gm-Message-State: AOJu0YyR5pI4iUeVdq+cgYP35aWADmwVRt1gbb9aSZuVjsJZNczaP4AF gBeHu9EG9GsWLsWYRtkhHy6pUezF4S4S4x04yj2Nrg==
X-Google-Smtp-Source: AGHT+IFDchZ1SMIGfY8P540CgWZgl4Ze2MrETcf+nt723C2G+g/oGgMf6PB5nsz3n/l2P/a5hBnfc6bx4lDVDGtWIwY=
X-Received: by 2002:a05:622a:2cd:b0:41c:bbbc:2ede with SMTP id a13-20020a05622a02cd00b0041cbbbc2edemr34997361qtx.14.1699364015301; Tue, 07 Nov 2023 05:33:35 -0800 (PST)
MIME-Version: 1.0
References: <169805098816.26116.8446506358091275400@ietfa.amsl.com> <CAKC-DJjVp68PjrjqEYKdMT0q9yAf4N=vBFy1cPG63CLTVr6TYQ@mail.gmail.com>
In-Reply-To: <CAKC-DJjVp68PjrjqEYKdMT0q9yAf4N=vBFy1cPG63CLTVr6TYQ@mail.gmail.com>
From: Nick Buraglio <buraglio@forwardingplane.net>
Date: Tue, 07 Nov 2023 07:33:23 -0600
Message-ID: <CACMsEX9s=g_Pgvv3dOJb1WDPM0WQmnT9rpPS9+Hg1Qo=Eynrhw@mail.gmail.com>
To: Erik Nygren <erik+ietf@nygren.org>
Cc: v6ops@ietf.org, gih@apnic.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/o4DioeTRPCzfFBXtjmiG3qNTPrs>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-update-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 07 Nov 2023 13:33:40 -0000
On Tue, Nov 7, 2023 at 6:21 AM Erik Nygren <erik+ietf@nygren.org> wrote: > > Should we ask for multiple prefixes while we're doing this? > Both a small prefix (eg, another /32) in addition to the /20, trying to make sure that there is enough visual difference between them? > It would be good if neither was in 2001::/16. > Having a few that are clearly distinct helps with readability of documents talking about distinct entities. > Similar to the multiple IPv4 documentation prefixes that are visually different, it would be more readable. > (Some other people made this same comment at the mic while I was writing this.) > > Regardless, we should also have a clear statement in the draft that documentation prefixes > MUST NOT be used for actual traffic , MUST NOT be advertised, and SHOULD NOT be routed? > (There was a comment in some other thread about ULA with someone talking about using > 2001:db8::/32 in production rather than ULA because it had higher preference in source address selection.) Thanks, Erik. I think this would be good to add the guidance on advertisement and routing. We will work on some verbiage that provides the guidance. > > Thanks for pulling this together! I keep wishing there was more than one IPv6 doc prefix. > > Erik > > > > On Mon, Oct 23, 2023 at 10:49 AM <internet-drafts@ietf.org> wrote: >> >> Internet-Draft draft-ietf-v6ops-rfc3849-update-00.txt is now available. It is >> a work item of the IPv6 Operations (V6OPS) WG of the IETF. >> >> Title: Expanding the IPv6 Documentation Space >> Authors: Geoff Huston >> Nick Buraglio >> Name: draft-ietf-v6ops-rfc3849-update-00.txt >> Pages: 4 >> Dates: 2023-10-20 >> >> Abstract: >> >> The document describes the reservation of an additional IPv6 address >> prefix for use in documentation. The reservation of a /20 prefix >> allows documented examples to reflect a broader range of realistic >> current deployment scenarios. >> >> The IETF datatracker status page for this Internet-Draft is: >> https://datatracker.ietf.org/doc/draft-ietf-v6ops-rfc3849-update/ >> >> There is also an HTML version available at: >> https://www.ietf.org/archive/id/draft-ietf-v6ops-rfc3849-update-00.html >> >> Internet-Drafts are also available by rsync at: >> rsync.ietf.org::internet-drafts >> >> >> _______________________________________________ >> I-D-Announce mailing list >> I-D-Announce@ietf.org >> https://www.ietf.org/mailman/listinfo/i-d-announce >>
- [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-upda… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… Eric Vyncke (evyncke)
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… Nick Buraglio
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… Erik Nygren
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… Geoff Huston
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… Owen DeLong
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… Ed Horley
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… Owen DeLong
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… waldemar
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… Nick Buraglio
- Re: [v6ops] I-D Action: draft-ietf-v6ops-rfc3849-… Nick Buraglio