IETF Logo Mail Archive

Re: on the need for documentation addresses of all types

Tim Chown <Tim.Chown@jisc.ac.uk> Mon, 27 February 2017 14:36 UTC

Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83C6612A069 for <ipv6@ietfa.amsl.com>; Mon, 27 Feb 2017 06:36:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk header.b=ehwI3Now; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=jisc365.onmicrosoft.com header.b=KGygfk97
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 a1Wi2iW-rlql for <ipv6@ietfa.amsl.com>; Mon, 27 Feb 2017 06:36:51 -0800 (PST)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24918129FF2 for <6man@ietf.org>; Mon, 27 Feb 2017 06:36:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1488206209; bh=mOd2t2svDZSRW225/vF/dNA76N8keKo2ppeFAa4PoYQ=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To:Content-ID:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ehwI3Now+VIqlL2YAL6Q1pWIfROxbNcQn18XM4Tt0CcCzSGXT/8B16qttkfiPgqVygOsHMjWaKbCL+x7T3ENJP4wQAIRh7ltNT+EgxA3UbGsZFHhwUsnTJtwMiW1rXQ+M4aRzliS8lD6Ve9Yo+Dac9U7I8OQrEWM0Iwml+goFGs=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=mOd2t2svDZSRW225/vF/dNA76N8keKo2ppeFAa4PoYQ=; b=KGygfk976/z83InkLU5U631h1mb4CoVzIguVHwyOFi/y74UNpKvUHFm369QGqXe5mOtSYe/Mp5kYK4Ksek1U/QClllnXd97SfKlvwfR7sdpCEgn+5HwmBo+pIHpISFCl5pw5Y3NbfJY/+4DAdZggcE59z6x87gUeZLYoK1/WR24=
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01lp0180.outbound.protection.outlook.com [213.199.154.180]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-77-stQGG8XoOeywBzVMFAO2IA-1; Mon, 27 Feb 2017 14:36:43 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1137.eurprd07.prod.outlook.com (10.163.188.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.947.2; Mon, 27 Feb 2017 14:36:43 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::2c80:1ca:49d1:d387]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::2c80:1ca:49d1:d387%15]) with mapi id 15.01.0947.005; Mon, 27 Feb 2017 14:36:42 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: on the need for documentation addresses of all types
Thread-Topic: on the need for documentation addresses of all types
Thread-Index: AQHSkQU188W6O9o2R0mpOCAGFhdhZaF868eA
Date: Mon, 27 Feb 2017 14:36:42 +0000
Message-ID: <16E4F0CD-8B92-4477-B27E-FAB01C39F4E9@jisc.ac.uk>
References: <10130.1488205434@obiwan.sandelman.ca>
In-Reply-To: <10130.1488205434@obiwan.sandelman.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3259)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [212.188.254.49]
x-ms-office365-filtering-correlation-id: c1f38a00-e73c-4dcf-3d03-08d45f1e0c80
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM3PR07MB1137;
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1137; 7:3iTUVZjTCuj0bpDjz606WDBMHTUzyUbQoCDjx55z3RSb31I3mTHI3pt5101RuBRcBLQ8EPe0mmel+sXWh7XrX50y5kWHTQLq3d9Ag4VWvwP7fZAPgRacfQWVQnFzPSC5VrYUc69Qbs0mIcxy+B8MeTQi9qqj8ZMcO98slBxNScxD72OklQdOzIXxezFFzJUCd49afAPMuV5XiBd3f0kJtBU8eAgrCXvP3Bio+ThBndzkajnnpgeKhu2CAMOcgkMpnuhZsTcucNnz9iQ28LnQ5PlFg11MxmKrpQlPOcYrFxOVYtkWX4FjFn7YStQGW+D/daV8Xgfq8cGqvU+QpPw2Ug==; 20:t8xwrkV22GRup9+KXuMc3VnwQef0gYLIZ/WrkxeGIpIDxPLn0AJAY7dQQuf6eFgXSVH8xZGyBNQ8NDIQjAzPgotRnbSx9WmTb1YDHUnHV7AhT5CsbVWJsJiae/YoAl3dC++wP05k+rH8qXLpoap+gUm2CJSEFV+HunGuc9O3+iY=
x-microsoft-antispam-prvs: <AM3PR07MB1137610D8B2D2427EFE34EEAD6570@AM3PR07MB1137.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123562025)(20161123558025)(20161123555025)(20161123564025)(20161123560025)(6072148); SRVR:AM3PR07MB1137; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1137;
x-forefront-prvs: 02318D10FB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(199003)(24454002)(189002)(305945005)(229853002)(101416001)(6116002)(3660700001)(8936002)(76176999)(50986999)(57306001)(3846002)(38730400002)(82746002)(7736002)(102836003)(2906002)(50226002)(189998001)(83716003)(53936002)(3280700002)(8676002)(81166006)(6436002)(6486002)(97736004)(66066001)(81156014)(6506006)(5250100002)(110136004)(106356001)(36756003)(33656002)(6246003)(74482002)(99286003)(6512007)(86362001)(2900100001)(53546006)(4326007)(106116001)(105586002)(42882006)(5660300001)(92566002)(68736007)(2950100002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1137; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <86B2BA155181F04B99B7672625B3F898@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2017 14:36:42.8064 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1137
X-MC-Unique: stQGG8XoOeywBzVMFAO2IA-1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aZgya_g75EhYPxWsgMT8VvnHps4>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 14:36:53 -0000

On 27 Feb 2017, at 14:23, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> rfc3849 gives us 2001:DB8::/32 for use in documentation.
> 
> I find that I am often giving example addresses in fe80:: (Link Local), and
> fd00::/8 (ULA) addresses when those prefixes are appropriate for the
> protocol.   I worry that someone will think the numbers I've chosen are
> special in some way.  There are clearly far less concern about duplication
> since both spaces are designed to be duplicated (LL) and
> not-guaranteed-to-be-unique (ULA).

> I'd still be happier if someone google'ed the prefixes in the document, and
> found that they were documentation examples.

I guess it’s tricky to reserve any documentation range when those could be genuinely used anyway?

> I'd also like to have three additional documentation prefixes from GUA
> space so that examples involving inner and outer addresses, and senders and
> receivers could be better distinguished.  Yes, we currently can carve
> /48 blocks out of 2001:DB8::/32 for this purpose, but it would be nice if
> the pattern was even more unique.
> 
> Would it also be useful to have documentation addresses for the multicast
> ranges, and the like?

There are multicast documentation prefixes - see RFC 6676.

Tim

v2.23.0 | Report a Bug | By Email