IETF Logo Mail Archive

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

Suresh Krishnan <Suresh@kaloom.com> Mon, 04 November 2019 02:49 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 7EC6512002E for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 18:49:29 -0800 (PST)
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 NrLHC1iwFOoj for <ipv6@ietfa.amsl.com>; Sun, 3 Nov 2019 18:49:27 -0800 (PST)
Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670131.outbound.protection.outlook.com [40.107.67.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DD7C12001E for <ipv6@ietf.org>; Sun, 3 Nov 2019 18:49:27 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=j0In7dvSW2cCJcHVU/fxmPqCxIfdEo1ter0uX4ZqGZZl4/S+OMw7wiKWFBZYFFPtbLPnuKJ2/L/Rd1Brehtu6wf1JOBFE60mGMqRlIcK7qpp1QSO9h6jbGx04cehqQ6cxllN2JnI6S49MmYZe1ywt6/jhjhWYURxhzyUWxQcb6Ydawzvv6YSwF1aG9bSP9iu/ydJwC1gwloh+8v1hOGd/WwWBlHbeQ/fzWBW67zRYe0dvw2UZsvRVOKPDYpMRsGSF3PMzgdaVgXM5VnTEvRzWpCR8ZZ4et5/9Q44tYX68isWtRXCuTaeIxGb/7ekkNGeGm2H1cI9O/oBCJeNGojmhg==
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=O5vv5sSY21AROOJ48z1ZtQ0kRA94brKyLu9I3zxd2gs=; b=I8dcAYo+DsUBgh0FztuSeUd9ePrSBOtCFyPTjpGD63KdiswQReD/Ao+HKhZf1bLEEvxS+0wKBkEKgTlbQI0JvH9c2drN4JigbvyAL4jdFM9C9mo5EXy0UXmmk6ugndFan0fzbDIo8Mh6Vm9q1L4F0rMQ/h7NFCsxOoa2CN6BjLqXO/pGwLo38auSax1wrKnmfVZNzdbY0mrn43la0V8E6TuaSgkp/JvwPbkELkIMjwPFpIzz7gGfXt9yR6EbqsVCN0SBcvaPExbJXkDsElpDb6ogb3iH/xFEVmLtYKnj+TmmPHWe3bxeKKIoQs/9uFgJN9ns82VjBSQE1gck1Y0gsg==
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=O5vv5sSY21AROOJ48z1ZtQ0kRA94brKyLu9I3zxd2gs=; b=nurHbj4mEvuenpyMNzmz8S9m/CaA2NS0DbKECVFDtbYhAjC39wIh86NAxZvUM77lpnhhuN/IuBp0QTMsoanDP5ZtpTj4GZBC8bwszUlYy9ZS2FrvAe7VAvSHGjT5xeKRsgD6zieRyUEGt4UhfQ+DYAJHdGHBSGUzWHHVGGf0XdE=
Received: from YT1PR01MB3642.CANPRD01.PROD.OUTLOOK.COM (10.255.42.27) by YT1PR01MB3930.CANPRD01.PROD.OUTLOOK.COM (10.255.44.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Mon, 4 Nov 2019 02:49:25 +0000
Received: from YT1PR01MB3642.CANPRD01.PROD.OUTLOOK.COM ([fe80::df4:b056:1a3d:94fb]) by YT1PR01MB3642.CANPRD01.PROD.OUTLOOK.COM ([fe80::df4:b056:1a3d:94fb%4]) with mapi id 15.20.2408.024; Mon, 4 Nov 2019 02:49:25 +0000
From: Suresh Krishnan <Suresh@kaloom.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Michael Richardson <mcr+ietf@sandelman.ca>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: 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: AQHVkdGmbpEIAXTBR06W8NLDQ1uxdKd5scWAgAAlf4CAAHoHAA==
Date: Mon, 04 Nov 2019 02:49:25 +0000
Message-ID: <47FE7A8C-7917-4D8B-A838-CB201B489902@kaloom.com>
References: <F1B31C38-7CDB-4057-A573-D6AF76B264D3@kaloom.com> <CAKD1Yr1vOqTvEsv0oCm+bu7CkFwiyFv8_G1XM+4JAKYLoA21aA@mail.gmail.com> <27802.1572732078@localhost> <F95A29A5-CEAF-4A23-A678-C5465B248E42@kaloom.com> <24180.1572801507@localhost> <7fd283ed-2328-6a9e-eb86-c5c155ebfd84@gmail.com>
In-Reply-To: <7fd283ed-2328-6a9e-eb86-c5c155ebfd84@gmail.com>
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: 68033ffc-5a6d-4a37-89fa-08d760d19a7a
x-ms-traffictypediagnostic: YT1PR01MB3930:
x-microsoft-antispam-prvs: <YT1PR01MB393077EDE419C320FAFDA6F0B47F0@YT1PR01MB3930.CANPRD01.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(346002)(376002)(396003)(39840400004)(136003)(189003)(199004)(102836004)(26005)(36756003)(66066001)(6916009)(8936002)(25786009)(66574012)(71190400001)(186003)(14444005)(256004)(80792005)(8676002)(86362001)(81156014)(81166006)(71200400001)(76116006)(508600001)(66476007)(66556008)(64756008)(66446008)(91956017)(66946007)(14454004)(5660300002)(7736002)(305945005)(11346002)(2906002)(3846002)(476003)(316002)(2616005)(6116002)(446003)(486006)(6512007)(6246003)(99286004)(4326008)(6436002)(6486002)(229853002)(33656002)(54906003)(76176011)(53546011)(6506007); DIR:OUT; SFP:1102; SCL:1; SRVR:YT1PR01MB3930; 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: ecqHCc8jtApW1I41NZhlZgqdcuq3yRvLrDxvBybOAlDspFwLWVC8QnHFRMTuIrTDY8g+PH6rp1mBFcAotk2RyDhOaOLB/xzPwypIk1/88+9dksBcI7zV2a+l8OKijTh4RC3minkiH+OjKdGFNQtSMe5cjoICtIsJCNBVcjGXpOqDLnhOfTvsohI6fgYu0b6Ysi+oNkV7SkZmuutR1raiOGnSoFBLTTsrFMsxW01d1W/2PWw8s6sHfphmhpLr296Qrxk2DxEHDHaXprhN44HlSWkjNvJkZCpvWZ6jtSM7MY5scnNQxC+FbACrsUp8TRzJQmEdcM57dHYMTHRx9VcTvQsWp8hUqCdd/zJH0KbhE8BlBI4JbHWAIgh+ntxTRfAN6pF4PecuqBAd6BPGldjm7hrLjJS5l61mep508/0xZoSVeLO439joGrOGa80sOTO3
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <27F1128A54C3414E906B9C69BF642F17@CANPRD01.PROD.OUTLOOK.COM>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: kaloom.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 68033ffc-5a6d-4a37-89fa-08d760d19a7a
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Nov 2019 02:49:25.0478 (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: wF3nZC1BxcoBG6AAAHZ0tksyw4Ni2GCF2f8PgvIwo0USllQynLbMYZsCcl0HYXZB7rhtfkVSa1UasDjmdH3PyA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YT1PR01MB3930
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0OMe6kXAbh1Mkg4iV-GFv73z4uM>
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: Mon, 04 Nov 2019 02:49:30 -0000


> On Nov 3, 2019, at 2:32 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> On 04-Nov-19 06:18, Michael Richardson wrote:
>> 
>> Suresh Krishnan <Suresh@kaloom.com> wrote:
> ...
>>>> 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 guess L=1 is why you call it ULA-L. I have known it as ULA-Random.
>> We are both talking about RFC4193 though.  So such a document would need to
>> update RFC4193.
> 
> I think this is a bad and pointless idea. Pointless because it is 100% OK
> to use any RFC4193 prefix as an example, since by definition it will never
> be used on the Internet, and the chance of collision on a given ULA site
> is 1 in 2**40 (and who cares anyway?). Bad because it means that millions
> of existing boxes that can generate ULA prefixes would be non-conformant
> and, seriously, is any vendor going to update date their firmware for this?

Agree with you Brian. That is why I called out the collision issue above.

Regards
Suresh

v2.23.0 | Report a Bug | By Email