Additional Documentation Prefixes (was Re: AD Evaluation : draft-ietf-6man-ra-pref64-06)

Suresh Krishnan <Suresh@kaloom.com> Sat, 02 November 2019 23:02 UTC

Return-Path: <Suresh@kaloom.com>
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 61A7D120071 for <ipv6@ietfa.amsl.com>; Sat, 2 Nov 2019 16:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001, 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=kaloom.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 vgqY4Reyhk6W for <ipv6@ietfa.amsl.com>; Sat, 2 Nov 2019 16:02:53 -0700 (PDT)
Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660108.outbound.protection.outlook.com [40.107.66.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3846F120020 for <ipv6@ietf.org>; Sat, 2 Nov 2019 16:02:53 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fyOPVWzutk3q2X7/mpb+8j+RkVbIxYopepEWyFlQ4TTnllGXSYJom12yfUEg+1M133fca7W4cYRZ/J+i8+vdQySEqz7Eca4Io3qRuAh5ZgtanKjc7PiupytBrnzTp+Es3jByxLft1UFYbG3OT18TLc3dHPG99NlJIzN9dVOTJrKd+J/pB2aehJARYOG1ZHRdpwRZcBMTUPbJ5EiSDpNx1UmejBtp5mqV6RuJpeuhQsnkbJ+ysp0aHg/6hPeoIIV85mNFDmw75pN1cDN0QeK1Fuz4tXgcqkFsbrvBm4ShlQ9mAFhIp1scLTOjiMPXuib1h6YJ+JLso1sDWLUtYGaTrw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OXiUlE96qD7wrm/FBgq7jeDdN8J8IV4/KuzQu0NG2X8=; b=I9M1h7ntieuX9gexurhgJlr0uHv1dHZOHzaP4XrmSTfBAUuW73/3vYxFN+sz1jp9pMXpxdeKZyFRIkR7i4cMxqeuPW0cMhQxivR6GbT5Aa34edDpbAkN61ZILCTG3m15UaLpv319hFslvnHpMqcr+HJU1LAOTBhzIyNhRxwLK4Y6ml3IIn14zlXgz0dCx76a0bKBcRGIb59r5UYmgRKbKcHU42/7yFEdvw7P+P1aA4KjTGaTYBuCf/T8XhgxeMuWyXDU1YqELYTAbE1YinGfGrXbJi90ZEvsgh0PGNVTFyEcUJ2Km4Tgv9cRcj+fd4/M+OPi4mr+RO6mbXdoqAf7FQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=kaloom.com; dmarc=pass action=none header.from=kaloom.com; dkim=pass header.d=kaloom.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kaloom.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OXiUlE96qD7wrm/FBgq7jeDdN8J8IV4/KuzQu0NG2X8=; b=IP6/GShgff5fATojzZUX7dr8ZkdQhBNYIyFBGx8uEReLHNPwb6/ScYgZZc/HKmpFwZmV7cG3cGqOgBaIBN1cKxuN56upRT+wTRWIxmrkQ6ZMiFLgAuO8GlK/O3z/EZ90ENzPC9B2F4EZxxPP4yeQYq4kWXGQ5k86ZlObeZIJaBg=
Received: from YT1PR01MB3642.CANPRD01.PROD.OUTLOOK.COM (10.255.42.27) by YT1PR01MB3417.CANPRD01.PROD.OUTLOOK.COM (10.255.41.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Sat, 2 Nov 2019 23:02:50 +0000
Received: from YT1PR01MB3642.CANPRD01.PROD.OUTLOOK.COM ([fe80::c00b:23f0:4c61:f412]) by YT1PR01MB3642.CANPRD01.PROD.OUTLOOK.COM ([fe80::c00b:23f0:4c61:f412%6]) with mapi id 15.20.2387.030; Sat, 2 Nov 2019 23:02:49 +0000
From: Suresh Krishnan <Suresh@kaloom.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: Lorenzo Colitti <lorenzo@google.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Additional Documentation Prefixes (was Re: AD Evaluation : draft-ietf-6man-ra-pref64-06)
Thread-Topic: Additional Documentation Prefixes (was Re: AD Evaluation : draft-ietf-6man-ra-pref64-06)
Thread-Index: AQHVkdGmhQIAay5mEUG7JYHS3OVEpA==
Date: Sat, 2 Nov 2019 23:02:49 +0000
Message-ID: <F95A29A5-CEAF-4A23-A678-C5465B248E42@kaloom.com>
References: <F1B31C38-7CDB-4057-A573-D6AF76B264D3@kaloom.com> <CAKD1Yr1vOqTvEsv0oCm+bu7CkFwiyFv8_G1XM+4JAKYLoA21aA@mail.gmail.com> <27802.1572732078@localhost>
In-Reply-To: <27802.1572732078@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Suresh@kaloom.com;
x-originating-ip: [45.19.110.76]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ecd78cd4-c04b-4c59-e9de-08d75fe8c8a5
x-ms-traffictypediagnostic: YT1PR01MB3417:
x-microsoft-antispam-prvs: <YT1PR01MB341799838FC10FDF733D889BB47D0@YT1PR01MB3417.CANPRD01.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0209425D0A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(39850400004)(366004)(376002)(136003)(189003)(199004)(6486002)(305945005)(8936002)(446003)(7736002)(81156014)(81166006)(11346002)(486006)(476003)(2616005)(66066001)(2906002)(8676002)(80792005)(33656002)(25786009)(71200400001)(6116002)(3846002)(508600001)(71190400001)(4326008)(86362001)(14454004)(5660300002)(6506007)(256004)(14444005)(36756003)(66476007)(64756008)(66446008)(66556008)(6512007)(99286004)(66946007)(91956017)(76116006)(53546011)(76176011)(316002)(54906003)(26005)(102836004)(186003)(6436002); DIR:OUT; SFP:1102; SCL:1; SRVR:YT1PR01MB3417; H:YT1PR01MB3642.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: kaloom.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: qOx16c63ZWJWUksJiWHQk4AmlJzdTTQ5fB8HOXZGB/5eOzkA7zqGmsc3q1RMRSs3urou6jpaJ4QjuUZx/gRZn4ysMV21b2wDXfIuyVNVEIWnnhEgBQQr4fFMNswOzHV40TGuNk+5T6uEJCIaaIsf7mvjJOO9UvISIGXcm4/9Oa7rwZkKQAbHC4bu6UOx2fSxDo/ALwZzjvop5ao4p8hlSnqwRQebCyrBOauJxnUJTLQeRBuMG+Qa9lfBdYO+CiHhbSQD43xsDpHXkX0QLrwK2cmttI9ZFPW7tavf6Z/iP2w66Z8LSwzpWfYqdhyoSyBA5LL1hua4yp5IGL/ZS2lPfM/DjEqgnOY5dSlKAReQ8h16NNyvqj5xIVKVy8AmB6MajwnwHp+CJ2oLP69GRRhAVarbgMMWJUDGMhcFAUQGtX3kJHPMdrGOF8IsxYMl0Emq
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <CCDCC46E66D91146B38434562D78C9AE@CANPRD01.PROD.OUTLOOK.COM>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: kaloom.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ecd78cd4-c04b-4c59-e9de-08d75fe8c8a5
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Nov 2019 23:02:49.8882 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 47d58e26-f796-48e8-ac40-1c365c204513
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 9C1XEfaYl/1jhBb5Eb6WB34a1Z2XMpCjRe0u6SzyN/R1C3SiaKFQ4ZzkpCrfsWXqx8o1g2Om76gjCmDr5XnioA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YT1PR01MB3417
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/HKBOnO8cTKmdD08AAyMyRdNcMDQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 02 Nov 2019 23:02:55 -0000

Hi Michael/Lorenzo,

> On Nov 2, 2019, at 6:01 PM, Michael Richardson <mcr+ietf@sandelman.ca>; wrote:
> 
> 
> Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>; wrote:
>>> Please use a documentation prefix, say 192.0.2.0/24, instead of the
>>> RFC1918 address currently used in the example.
> 
>> Are you sure this would be an improvement? The example would become less
>> realistic because 1) 192.0.2.0/24 is a /24 and subnetting a /24 is
>> unusual,
>> and 2) it's seems like a reasonable thing to do to route private space
>> to a different NAT.
> 
> I agree with you.
> 
>> Is there a larger documentation prefix than 192.0.2.0/24?
> 
> I wish that there was.

Me too. I also think a larger prefix could be useful. Similarly a block that would differentiate it as an example of private space to be used.

> Maybe we could carve out of class E space as a /20 of documentation space.

Sounds like a plan. If you write something up, I would be willing to AD sponsor something like this. The biggest issue with repurposing E space was that it would hit a lot of bogon filters. In this case that is a desirable feature.

> I'd also like to have three or four additional IPv6 documentation prefixes,
> plus some documentation space from ULA-R and ULA-C.

What is ULA-R? Did you mean ULA-L? If so, it would be a pain to reserve something now since we also need to update RFC4193 to make sure that the Random “Global ID”s will not collide with the reserved prefixes. If ULA-C does take off, this would be a good idea to do something like this.

> 
> I'd like the IPv6 documentation prefixes to have a pretty high Hamming
> Distance from each other to maximize the visual distinction.

We have a /32 for this. Plenty of ways to be visually distinct including some of the common ones I have used :-)

2001:db8:abba::/48
2001:db8:beef::/48
2001:db8:cafe::/48
2001:db8:dead::/48
2001:db8:face::/48
2001:db8:c001::/48

Cheers
Suresh