RE: ULA clashes don't matter [Re: ULA Registration]

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Fri, 24 March 2017 18:45 UTC

Return-Path: <albert.e.manfredi@boeing.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 6A49B120727 for <ipv6@ietfa.amsl.com>; Fri, 24 Mar 2017 11:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 DX2eM-zyB7TH for <ipv6@ietfa.amsl.com>; Fri, 24 Mar 2017 11:45:27 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 D923E126C2F for <ipv6@ietf.org>; Fri, 24 Mar 2017 11:45:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v2OIjQBi043530; Fri, 24 Mar 2017 11:45:26 -0700
Received: from XCH15-06-09.nw.nos.boeing.com (xch15-06-09.nw.nos.boeing.com [137.136.239.172]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v2OIjK5h043503 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 24 Mar 2017 11:45:20 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-09.nw.nos.boeing.com (2002:8988:efac::8988:efac) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 24 Mar 2017 11:45:19 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1263.000; Fri, 24 Mar 2017 11:45:19 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: ULA clashes don't matter [Re: ULA Registration]
Thread-Topic: ULA clashes don't matter [Re: ULA Registration]
Thread-Index: AQHSpM3A/iJHQdoIe0W/pkEm96rrv6GkU96g
Date: Fri, 24 Mar 2017 18:45:19 +0000
Message-ID: <a0d4aff56a71429589dfd488216b29d4@XCH15-06-11.nw.nos.boeing.com>
References: <CAN-Dau132Jg0SsRjgcrxzGfbUEx_KPES9wMgDMg_++-zwY+0dw@mail.gmail.com> <7c4412a4-6494-961d-165b-9c5d267015a7@gmail.com> <39db830bd4d04faca308c01d0d39b8ae@XCH15-06-11.nw.nos.boeing.com> <bc58c4d5-68b9-9651-1c4e-657c6d07c61d@gmail.com>
In-Reply-To: <bc58c4d5-68b9-9651-1c4e-657c6d07c61d@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6Ko-nQRNnwLuf8mw4dhusS6i64I>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 24 Mar 2017 18:45:30 -0000

+1


-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Brian E Carpenter
Sent: Friday, March 24, 2017 14:38
To: ipv6@ietf.org
Subject: ULA clashes don't matter [Re: ULA Registration]

Do I need to justify that? Oh, OK:

1. In the highly unlikely event of two networks merging (i.e. installing
round-the-back private routing between them) and discovering that they
are using the same pseudo-random ULA prefix: yes, they will be put to
a little bother. But this is so unlikely that it really isn't worth any
overhead to avoid it - and it would only be avoidable if at least of the
two networks had bothered to register their prefix.

2. In the rather more likely event of two networks merging and discovering
that they are using the same non-random ULA prefix (fd00::/48 probably),
it's their own silly fault.

3. In the somewhat likely event of a ULA prefix being announced in BGP4,
we will know who's announcing it, so we don't need a registry. And everybody
else will filter it anyway.

Regards
   Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------