Re: Embedding IP information in an IPv6 address (OMNI)

"Templin (US), Fred L" <> Sat, 17 October 2020 15:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 568793A0C9D; Sat, 17 Oct 2020 08:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LD7x1PV-e0cx; Sat, 17 Oct 2020 08:55:47 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4AA473A0C9C; Sat, 17 Oct 2020 08:55:47 -0700 (PDT)
Received: from localhost (localhost []) by (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 09HFtjTw017918; Sat, 17 Oct 2020 11:55:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=boeing-s1912; t=1602950145; bh=BmqtdplwV8dp5tcqX57NWN/O+eMGR9td5B1vAKT0++Q=; h=From:To:CC:Subject:Date:From; b=Fe3xPBRmH5QH6HVroiMTqgT3znsqNg6d4RZhKwgnlHjeB9o5XMFIW4x5eD1qfemiI /0zotJOFn4POhVssSrx27Q82QgtjqC6kCKuHIHFI1273pya0VwW+hQ/TAdeMr/ES7H 8YATj6nqjFLh7Xusp+76K1mQ2JFwmImd0A1iLgn1Z9hFwQAd1x7HAg3obd45Plmyfi HsFQewuv0ZLg+YoUA7pkYhymkCIIipdh733JzF2ug/86FQqAqyjzTwCO7LkrrZaevH /kDlh+3yq4a3EnQ1FCSd6TX05U4LC0Kco1cJLAkpBEN1IbMaGKx2sfuUkyjD6V/Yrj 5k5xBHsveuP4g==
Received: from ( []) by (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09HFtbjn016839 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Sat, 17 Oct 2020 11:55:37 -0400
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Sat, 17 Oct 2020 08:55:36 -0700
Received: from ([fe80::1522:f068:5766:53b5]) by ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Sat, 17 Oct 2020 08:55:36 -0700
From: "Templin (US), Fred L" <>
To: "Manfredi (US), Albert E" <>, Ole Troan <>
CC: "" <>, "" <>
Subject: Re: Embedding IP information in an IPv6 address (OMNI)
Thread-Topic: Embedding IP information in an IPv6 address (OMNI)
Thread-Index: AdaknTaMxD3hGdlTThaXSslc4Lj72w==
Date: Sat, 17 Oct 2020 15:55:35 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-tm-snts-smtp: FAC7956E878E5D1845396FBCBF13825CD3A59431E0A322925EE04B97525C95672000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 17 Oct 2020 15:55:49 -0000

Hi Bert,

> -----Original Message-----
> From: atn [] On Behalf Of Manfredi (US), Albert E
> Sent: Friday, October 16, 2020 2:47 PM
> To: Ole Troan <>
> Cc:;
> Subject: Re: Embedding IP information in an IPv6 address (OMNI)
> From: ipv6 <> On Behalf Of Ole Troan
> > I would challenge you to make OMNI entirely free from semantic addresses. That would also help the working group understand
> what benefits semantic addresses bring to OMNI. And what the tradeoffs would be.
> I think it's a matter of speed and simplicity, no? You avoid that extra protocol, to assign addresses. Same idea as embedding the MAC
> into the IPv6 address.

No, it is very different - OMNI addresses embed only L3 information, whereas MAC
addresses represent L2 information. OMNI addresses do not embed any L2 info.

> But it's true that the IETF likes to stay away from semantic addresses.
> The path of least resistance, from all the back and forth, as of now, seems to be to either use ULAs, or to request a new /10 for this
> new purpose.

We are not in this to take the path of least resistance; we are in it to take
the path or paths that best serve the community even if some early-stage
resistance needs to be overcome.

As I have said, we will want and need all four of LLAs, SLAs, ULAs and GUAs;
all have their purpose in the future mobile Internet architecture.

Thanks - Fred
> Bert
> --
> atn mailing list