RE: 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 17:37 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 D13ED3A14B8; Thu, 18 Feb 2021 09:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, 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 mx0JhpnJcZ_z; Thu, 18 Feb 2021 09:37:15 -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 E96953A14B6; Thu, 18 Feb 2021 09:37:14 -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 11IHb9RX007643; Thu, 18 Feb 2021 12:37:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1613669831; bh=lUfN1sxSJ90Bt/qgmGIwHWfO7o0ivEqntSEpWSHGo1o=; h=From:To:Subject:Date:References:In-Reply-To:From; b=pchSeiwRPcG+r/OCGsbCBqRrtSY/WtrHrbPg/n7gWMubeiYkf/AK4s6ZvkFEaoYlt vXW/hOdRUSM+lCCVd2zMUcJdgi7bz4icD/EndCLJVSHRqKdRt8FscuF14BwklPbXNx OA9+lIHAfMwAREjdWM7CzGRqvVgi9hvFrEsV+qQjLORQD06MtpRbzOKyBxwgm68SAc JEP19RLMZSf1hHoO3Omzl5nUlHFp+OYAudOmf4ENFfOE91/9b7cBJ/T9Nlb5VIK1H6 +cviL0BcDpgSeOObEYZLu0qlVr+eBK4EC+sr9aQHe+O71iW2zsbljaawqOvOeJwz9U bcjXiYCjcHIaQ==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com [144.115.66.112]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 11IHb28k007561 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 18 Feb 2021 12:37:02 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-10.nos.boeing.com (144.115.66.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Thu, 18 Feb 2021 09:37:01 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Thu, 18 Feb 2021 09:37:01 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Subject: RE: Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
Thread-Topic: Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
Thread-Index: AdcGDy7xxNMh8TnnQrKbnV7MBFJ2YwADRsdQ
Date: Thu, 18 Feb 2021 17:37:01 +0000
Message-ID: <255e9e03a5884e82abb6c24da17d81a0@boeing.com>
References: <f96fc064b72c4b2eb63f80c26246c94e@boeing.com>
In-Reply-To: <f96fc064b72c4b2eb63f80c26246c94e@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]
Content-Type: multipart/alternative; boundary="_000_255e9e03a5884e82abb6c24da17d81a0boeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Ggu-xjOQ_q60Yf989zuLyRNkMZM>
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 17:37:17 -0000

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.

Anyone care to comment?

Fred

From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Templin (US), Fred L
Sent: Thursday, February 18, 2021 8:12 AM
To: 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, I have seen the discussion on LLA/ULA/GUA and even think I understand it. But,
I’d like to add another twist to the discussion. There is another “kind” of IPv6 address
called the “HIT” defined in RFC7401, and a variant called the “HHIT” that is defined
in ‘draft-ietf-drip-rid’. These addresses use a common GUA prefix (shorter than /64)
with the remainder of the address containing a cryptographically generated suffix.
They therefore resemble GUAs, but they are not aggregatable so at best could be
used as host routes. The documents are vague on whether the (H)HIT is assigned
to an interface (which is a necessary property of any IPv6 address), but if they were
couldn’t the (H)HIT be used as an IPv6 source/destination address within a limited
scope – perhaps in an edge network that deals only with host routes? If so, then
where would (H)HIT fall in terms of the scoped addressing architecture?

Fred