Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 18 February 2021 19:46 UTC

Return-Path: <Fred.L.Templin@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 DF0B13A1640; Thu, 18 Feb 2021 11:46:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 UA2RDK-1ZiKA; Thu, 18 Feb 2021 11:46:13 -0800 (PST)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 CEC2F3A163D; Thu, 18 Feb 2021 11:46:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 11IJk7VM011553; Thu, 18 Feb 2021 14:46:10 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1613677570; bh=HjDNUiJmdm26ehfZqTyu0qxD3+oniXXAImDPzMwQibA=; h=From:To:Subject:Date:From; b=pedLHNpssuMd1HwayVOb9rGQmT6KRrT6SASfKkqDeGr2AtVvYTK9bJPOIcIXekEqV aTz4gWksDZomH0spxwD9xhVYgi1oQK/g61MTD02CtfMq5ywaIYqq2zPm7lJ0ijV2/q 6Qk1KKjubUBimmx7jQVYEH3GJZjo24cEWojT3UZgb3nHLJ2HbUyhpsY+wiSVTKSiuy hMJAByQN+AbCS9nfa4LsQ40Xk41WtW8TGsxcAQDVZn7uJ1J/SZOmCEvZ0xsFpE847d wIgviiBs2uXOSS7URwg720BbxZVC5nKF91X8stRMzGpsqglyZMvwQPNP7qgUQ0z2ep 8XNRbeCpkJNjQ==
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 11IJk4II011522 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 18 Feb 2021 14:46:05 -0500
Received: from XCH16-07-07.nos.boeing.com (144.115.66.109) by XCH16-07-08.nos.boeing.com (144.115.66.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2176.2; Thu, 18 Feb 2021 11:46:03 -0800
Received: from XCH16-07-07.nos.boeing.com ([fe80::7897:2974:6af3:208e]) by XCH16-07-07.nos.boeing.com ([fe80::7897:2974:6af3:208e%6]) with mapi id 15.01.2176.002; Thu, 18 Feb 2021 11:46:03 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
Thread-Topic: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
Thread-Index: AdcGLI37+r0GkdjfRh2Wxz2Xkmwigg==
Date: Thu, 18 Feb 2021 19:46:03 +0000
Message-ID: <7aa2337f8d1b4036a64b3d0d40374eb1@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 13E4D8A079F4BBFD457FEB05D2F9C621ACB48247CEF3D8D91ACE38EB323D7F7D2000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/dToVrM127rLMDVjM7anw3Wr2IQM>
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: Thu, 18 Feb 2021 19:46:15 -0000

Fernando,

Intending to answer both your message and the previous from David together:

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Thursday, February 18, 2021 11:28 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>om>; IPv6 Operations <v6ops@ietf.org>rg>; 6man@ietf.org
> Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-
> 6man-ipv6-ula-scope-00.txt)
>
> Hi, Fred,
> 
> On 18/2/21 16:11, Templin (US), Fred L wrote:
> [...]
> >> On 18/2/21 14:37, Templin (US), Fred L wrote:
> >>> Another aspect I failed to mention is that the use of (H)HITs does not
> >>> necessarily  mean that all aspects of the HIP protocol must be used. (H)HITs could be
> >>> used with the AERO/OMNI services instead, for example.
> >>
> >> Questions: Are these addresses globally-unique?
> >
> > Yes - global uniqueness is a key objective of (H)HIT. Aggregation is not within
> > scope, however.
> 
> If that's the case, then, according to RFC4007, they are global addresses.

I actually think HITs are a bit of a gray area. According to RFC7343, they are
formed from the GUA prefix 2001:20::/28 but the remaining bits following
the ::/28 prefix are cryptographically generated and hence non-aggregatable.
That means that there is no way to represent a group of them in the routing
system using any other prefix length than /128.
 
> (I'd argue that if they cannot be aggregated, that's because they
> resulting "addresses" are not really topologically-dependent, in which
> case you might probably argue that they are not addresses in the first
> place :-) )

Not in terms of routing across the global Internet, no, because it would not
scale to inject large numbers of /128's into the global Internet routing system.
But, on a limited scale, that may not be so much of a concern - for example,
in a small Mobile Ad-hoc Network (MANET) where there may be some small
numbers of 10's of nodes each wanting to inject their own /128 into the
MANET routing protocol.

In that case, the node might be able to use its HIT for MANET-local addressing,
i.e., use it as the source/destination address of IPv6 packets within the scope
of the MANET as long as they do not leak out into the public Internet. That is
not to say that the node might not want to get a true GUA for itself as well;
for example, via DHCPv6 from an infrastructure node that the MANET
connects to.

So, then the node could get two different types of GUAs; a HIT for MANET-local
(infrastructure-less) communications and a true GUA for communications with
Internet nodes. So, two different types of GUAs - each with a different scope.

Fred

> 
> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> 
> 
>