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

Fred Baker <fredbaker.ietf@gmail.com> Fri, 09 October 2020 21:27 UTC

Return-Path: <fredbaker.ietf@gmail.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 C54B93A159E; Fri, 9 Oct 2020 14:27:45 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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=gmail.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 fRISGcKZS4PT; Fri, 9 Oct 2020 14:27:43 -0700 (PDT)
Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A340C3A1575; Fri, 9 Oct 2020 14:27:43 -0700 (PDT)
Received: by mail-oi1-x234.google.com with SMTP id c13so11637522oiy.6; Fri, 09 Oct 2020 14:27:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:in-reply-to :date:cc:message-id:references:to; bh=zGVZGcdJx9viBak7Zee916vvfByHepIptU18/ZanaVw=; b=ivzHlfScqxjsdTVlr/a+0WKWYs78d2O0OvduV9D2p573H385jr/rHCgvQt4Wj3X1Tu 1qFA7WwhpS4pHifK1Aq1laOoIBf02sYC+4EzZPAYx7bFqoYWpkMKhxYhM87L5toWWfj/ wjpBx8S7uIqgN0InlipKeQdGZlMLpz2vRh8uza0/pBbfBr93Edxbjegg3meubOnkuxD7 NkCyPQNS6rz3h8FGvYKaS0p7ADy1HuT+HonAlznVKFuPENGUWXvIg30qkr+5M8xV92Ix /thSuRRX5WhKGDflb5aINXLUff71HX7k6qOrxAx7auCDHhshwD9fGwssMNT7k3sNjxzS LZEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:in-reply-to:date:cc:message-id:references:to; bh=zGVZGcdJx9viBak7Zee916vvfByHepIptU18/ZanaVw=; b=Jw7+a1jkT0wa64rLLGvta9CnWqNntLDCKrzbcUAxBBKELjg2Gpc3T/xI8eLwxzmE+6 ikXIhB/63kn9auo2p0a3CcoFULKPjliR0Wt4I/EWRInWJPJDQXj0m1A7HAISegCMuioR yrf1sqX6FutmgsPNySVmYpjPi/3k9nP85ED7DXJMlks+KcH7qlsCWW1rgL2EIGBnHRci UZOp0ALZ0BAQIXwwWtr9fsvx19pdULP8Egqw4/4gZRRSp8lcScIMn65mc1jwm0R87r6B LVXD5+pMnD4ZEpa0ztcg28HpuowHY3IUNRb0eR86FiqgSCS2d6pVBARBrHBZE/pHFvL5 WC2g==
X-Gm-Message-State: AOAM533rJxvuD8fH0NSGoKj9LvqxVu3ZUyOPn+x+8ru+waclwSzpP6R7 A+xvY50Ky1hZw5FtQf+cVMcLsA6/rK0=
X-Google-Smtp-Source: ABdhPJwa9OWZU8EyPqc1QgJlRnrCx2Q4gilOfUPxyjV4BiAz8eMXG5I41Tpzejlzk7bHLHmj/0x/1w==
X-Received: by 2002:aca:ef03:: with SMTP id n3mr3741621oih.67.1602278862544; Fri, 09 Oct 2020 14:27:42 -0700 (PDT)
Received: from ?IPv6:2600:1702:290:6530:2dce:ba1f:4847:2cfd? ([2600:1702:290:6530:2dce:ba1f:4847:2cfd]) by smtp.gmail.com with ESMTPSA id 189sm7451516oid.40.2020.10.09.14.27.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 09 Oct 2020 14:27:41 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
X-Google-Original-From: Fred Baker <FredBaker.IETF@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-A348CF6E-4469-4474-B884-26E5D96517AC
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: Re: [atn] Embedding IP information in an IPv6 address (OMNI)
In-Reply-To: <7af0ab36-4a6b-cb44-609c-6e81b364a01c@labs.htt-consult.com>
Date: Fri, 9 Oct 2020 14:27:41 -0700
Cc: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, 6man <ipv6@ietf.org>, atn@ietf.org
Message-Id: <8009C8E3-E654-4623-BDC8-F794346C33B1@gmail.com>
References: <7af0ab36-4a6b-cb44-609c-6e81b364a01c@labs.htt-consult.com>
To: Robert Moskowitz <rgm@labs.htt-consult.com>
X-Mailer: iPhone Mail (18B5061e)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qyVeYZ_ARIzl5DufQkVZZTOJnrU>
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: Fri, 09 Oct 2020 21:27:52 -0000

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 <rgm@labs.htt-consult.com> 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:atn-bounces@ietf.org] On Behalf Of Templin (US), Fred L
>>> Sent: Friday, October 09, 2020 10:46 AM
>>> To: 6man <ipv6@ietf.org>rg>; atn@ietf.org
>>> 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
>>> atn@ietf.org
>>> https://www.ietf.org/mailman/listinfo/atn
> 
> -- 
> Robert Moskowitz
> Owner
> HTT Consulting
> C:      248-219-2059
> F:      248-968-2824
> E:      rgm@labs.htt-consult.com
> 
> There's no limit to what can be accomplished if it doesn't matter who gets the credit
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------