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

[Fred Baker <[e-mail]>]

The concept of embedding information in the 54 “must be zero” bits of the link local address is enticing, but may not prove interoperable, given the “must be zero” definition of a link local address.

Sent using a machine that autocorrects in interesting ways...

> On Oct 9, 2020, at 12:53 PM, Robert Moskowitz <[e-mail]> wrote:
> 
>  RFC 8064 updates all recommendations on content of the 64 bit Interface portion of IPv6.
> 
> Lots of old bad practices in old RFCs.
> 
> On 10/9/20 3:10 PM, Templin (US), Fred L wrote:
>> I forgot to mention RFC4380 which also embeds a *lot* of additional IP information
>> within the IPv6 address. There may be others I am also forgetting.
>> 
>> Fred
>> 
>>> -----Original Message-----
>>> From: atn [mailto:[e-mail]] On Behalf Of Templin (US), Fred L
>>> Sent: Friday, October 09, 2020 10:46 AM
>>> To: 6man <[e-mail]>; [e-mail]
>>> Subject: [atn] Embedding IP information in an IPv6 address (OMNI)
>>> 
>>> Hi, the OMNI spec defines an IPv6 link-local address format that embeds another
>>> IP address/prefix inside the least significant bits:
>>> 
>>> https://datatracker.ietf.org/doc/draft-templin-6man-omni-interface/
>>> 
>>> The idea behind embedding IP information inside an IPv6 address was first published
>>>  in RFC1884 (December 1995) where the "IPv4-compatible" and "IPv4-mapped" IPv6
>>> addresses were defined. (This was the first edition of the IPv6 addressing architecture,
>>> with the latest edition now as RFC4291.) Later, RFC4214 and RFC5214 put a more formal
>>> structuring around embedded IP addresses and RFC5969 even went further to move
>>> the embedded information up into the upper 64 bits of the IPv6 address.
>>> 
>>> The genesis of the OMNI concept of embedding additional IP information in the IPv6
>>> address was introduced in the "AERO(bis)" draft following the publication of RFC6706.
>>> This format was later cited in RFC7421. Now in the present OMNI draft, we have an
>>> IPv6 link-local address format where embedded IP information begins immediately
>>> after the fe80::/10 prefix thereby utilizing up to 112 available bits for encoding useful
>>> information.
>>> 
>>> It has come to my attention that some are skeptical about embedded IP information
>>> inside an IPv6 address. But, the OMNI draft shows clear benefits for making use of
>>> these otherwise-wasted bits and follows on from decades-old examples that are
>>> still in use today. Would love to hear everyone's thoughts on this.
>>> 
>>> Thanks - Fred
>>> 
>>> 
>>> --
>>> atn mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/atn
> 
> -- 
> Robert Moskowitz
> Owner
> HTT Consulting
> C:      248-219-2059
> F:      248-968-2824
> E:      [e-mail]
> 
> There's no limit to what can be accomplished if it doesn't matter who gets the credit
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [e-mail]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------