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

Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 16 October 2020 14:40 UTC

Return-Path: <sarikaya2012@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 522383A0A42; Fri, 16 Oct 2020 07:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 8dBCHeePm6xt; Fri, 16 Oct 2020 07:40:31 -0700 (PDT)
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (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 B7E3B3A09F0; Fri, 16 Oct 2020 07:40:31 -0700 (PDT)
Received: by mail-yb1-xb34.google.com with SMTP id n142so2110229ybf.7; Fri, 16 Oct 2020 07:40:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=T3MmqdOOtdXg/7IxjQfnPYYjhodGL2dHtI/wXNQmlZE=; b=iydnN/gdFzinEeZY1aIbl4iOAem3ZFlB0iR6bjwg9jWNZ0Ed13Ml2cr4SqnqQrzXKj 0p5mZnMdrNSqMVsq3DZPS978V6JYKky5d4bV2F5BnkRWJJoqbV4p9FOxhWr4HExKLLMB NRAmZ5cE97RxDsN6DexVGN2Sytbfr1UXAT6rPR85UmErH0afjM5Q/W121Hx48q6ghJeL SX6foJ1d5RUL1zF/uDGa47uupQle7V1obFVwmz0h4x4ydhCwNWODd7EX1IWzI9Elj7ee nR02vfFmhIjlOq9HcGkvZLA+4YY/nSpK+yUn02f6kharQBRlJpPiDNU8U2iRjdxvcATl rB1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=T3MmqdOOtdXg/7IxjQfnPYYjhodGL2dHtI/wXNQmlZE=; b=h+L6vl/tXs2X16sPFHdZfQSkxR02ohaCdoC+Rgskx2dy/W3IXTfxA5gZXCqCxcBM5H FPUUV2X0ki+fXuycs2Pwq7USXIcxm5nD5JLlqna9daquyDdJovw0fF6X1OQGCgbe+Utz u/TDY3tEvNzSGRKvwA4pAahT9b3SdzPJHBSGSrE/KjppRLm2BTNohPfFVBJWvz2QXAoN J8ETEXCXurCYiW2aprbpNgvDZqS9esruYyBZSK3XMUOVAOb/xgbSic4DoGUkxWG581yU 8oLI78nM1pZ548RnviZSg4IJwG0hRyO5GMeTKVDCMG2bwhrpFEahR8GnT4F2/amjtUyK MIMg==
X-Gm-Message-State: AOAM533NmryEJqp5ppCUPgEoueu7HiJIMMrBKn6wj5lnkxS3GcDAEwLe igWZSs6TmgZ/dc59ZOAlltQhqLFfx600mINjZgQ=
X-Google-Smtp-Source: ABdhPJwdMtjgRPRUuncOoLQC5v1zYOmScxPdciCjhPCJ5tO7DRZGmOcbRW/rRyvdbib8FvcV4bb0LufHIPkMinvicj0=
X-Received: by 2002:a25:3a46:: with SMTP id h67mr5647816yba.175.1602859230999; Fri, 16 Oct 2020 07:40:30 -0700 (PDT)
MIME-Version: 1.0
References: <c068f71229404b3693b977ca7cde828f@boeing.com>
In-Reply-To: <c068f71229404b3693b977ca7cde828f@boeing.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Fri, 16 Oct 2020 09:40:20 -0500
Message-ID: <CAC8QAcc3ye7Pbb8FUgDG8+9e-TurVc3cUSsC8b+27UtkEUDeeA@mail.gmail.com>
Subject: Re: Embedding IP information in an IPv6 address (OMNI)
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: 6man <ipv6@ietf.org>, "atn@ietf.org" <atn@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000016bdce05b1cabf84"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/eZAF4hw58OzQh_z4zmIUh9ZOO-s>
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, 16 Oct 2020 14:40:33 -0000

Hi Fred,

I am curious whether OMNI is designed with LEO satellite links like
StarLink which is being deployed worldwide and
operational partially in North America in mind?

Behcet

On Fri, Oct 9, 2020 at 12:46 PM Templin (US), Fred L <
Fred.L.Templin@boeing.com> wrote:

> 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
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>