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 16:13 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C9A13A1404; Thu, 18 Feb 2021 08:13:35 -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 ZmSD-bPx5477; Thu, 18 Feb 2021 08:13:32 -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 AD2BE3A17DF; Thu, 18 Feb 2021 08:12:24 -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 11IGCId0015171; Thu, 18 Feb 2021 11:12:21 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1613664741; bh=WhDep4y3kLBI/4CG3BBIgcPZKC3Lg6Cmkl6Rb0Twg/U=; h=From:To:Subject:Date:From; b=mF2qFqXIB9PBADw1tdEM6J/0rMwCoXcMSCo3DxAvBUfNj3xlPizjo+4g9MtzgEAzz VH7A/pO+qJW6DLshluLTeOzAXHUTDTgeb/YcD6fuDbvNjLzcTb4mNXqpuDCl67FIZU +F1dzbpgNZesQoA/FjJI+aeku8ppmHE+qpeEp+SUCL7yomfTP/P9gCYV/C/szxn7qV HFJ6+O9r0l/KMZlPVwLlnCYtvi+ShOGTh9MEYOsg6w2B9cE2bdsptQ65/+lNyJ5LMQ VgCE96cRDXJMOzuaPx/bwTbziKcnMWlbPWi9JFTdWChHn7FDymB+3pRNlHlsOWtAR3 woebRpYR4IIug==
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 11IGCGWJ015155 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 18 Feb 2021 11:12:17 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) 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 08:12:15 -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 08:12:15 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Thread-Topic: Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
Thread-Index: AdcGDy7xxNMh8TnnQrKbnV7MBFJ2Yw==
Date: Thu, 18 Feb 2021 16:12:15 +0000
Message-ID: <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]
x-tm-snts-smtp: 4DB4A3D19DF03F3227CB48CD41B15A8625550E55E2551C389FDD3FC476AEB1DE2000:8
Content-Type: multipart/alternative; boundary="_000_f96fc064b72c4b2eb63f80c26246c94eboeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/wTHoMgA5yG48fyVpHpWTxBLOFhY>
Subject: Re: [v6ops] Scope of Unique Local IPv6 Unicast Addresses (Fwd: New Version Notification for draft-gont-6man-ipv6-ula-scope-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2021 16:13:35 -0000

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