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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Wed, 14 October 2020 19:04 UTC

Return-Path: <Fred.L.Templin@boeing.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 B9CD73A0CBB; Wed, 14 Oct 2020 12:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
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: 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 onD95bZn8Cuy; Wed, 14 Oct 2020 12:04:52 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 0D0313A0C99; Wed, 14 Oct 2020 12:04:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 09EJ4nUr007030; Wed, 14 Oct 2020 15:04:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1602702290; bh=hHq6pS5cLMU9/TTneAeDgptOzw/L+Y/FZf4FCVegGYk=; h=From:To:CC:Subject:Date:From; b=PbEvZkQb3f32rsiYoKerz8QdKQQKydIc/ES/pz8slDKMB8lfZMQfEDFXWl6jjuQDz YahKvZaxdpbdjepWw+KD4yP7t14jK9310S9u4x0oLSxzFm4jhSDIYsnW4SuUM11OFA h23wL1FIkoZc9aoeBOrLiWEQx+jY2NDdz7wIvgpN92R5dFECuG9AHYo8D3oFVFTpKY TTxNZe8wRncr9D1Qxf83/S2zOJJ9gVw02pO57Ml/X3fCps7vDSgz8ZINc69w6yP574 l2aNwC6hR7vtNBW4YOIPe42rrRW+mr4841UtP/MEdzZvsLs2sEYEXqSsRWyd5drDNB V1axiZCXfvHwA==
Received: from XCH16-07-11.nos.boeing.com (xch16-07-11.nos.boeing.com [144.115.66.113]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 09EJ4bOU005591 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 14 Oct 2020 15:04:37 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-11.nos.boeing.com (144.115.66.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Wed, 14 Oct 2020 12:04:36 -0700
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; Wed, 14 Oct 2020 12:04:36 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
CC: Robert Moskowitz <rgm@labs.htt-consult.com>, 6man <ipv6@ietf.org>, "atn@ietf.org" <atn@ietf.org>
Subject: Re: Embedding IP information in an IPv6 address (OMNI)
Thread-Topic: Embedding IP information in an IPv6 address (OMNI)
Thread-Index: AdaiXHub6kRDBKobS0SrVaj++JwD+A==
Date: Wed, 14 Oct 2020 19:04:36 +0000
Message-ID: <e3416298088e4fa99e5aceb343af9494@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: E697B699DD66E7E1740B643C241BB261BC8D821E1ACBFE036C33E3CD6AB286F62000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jGcToQLlCLztf4RuYRZXPkvoXnk>
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: Wed, 14 Oct 2020 19:04:54 -0000

See below:

> -----Original Message-----
> From: 神明達哉 [mailto:jinmei@wide.ad.jp]
> Sent: Wednesday, October 14, 2020 11:39 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: Robert Moskowitz <rgm@labs.htt-consult.com>om>; 6man <ipv6@ietf.org>rg>; atn@ietf.org
> Subject: Re: Embedding IP information in an IPv6 address (OMNI)
> 
> At Tue, 13 Oct 2020 23:16:14 +0000,
> "Templin (US), Fred L" <Fred.L.Templin@boeing.com> wrote:
> 
> > > I don't necessarily say such a change is never possible, but if
> > > there's a lesson from that previous discussion, it would be that it's
> > > not as easy/trivial as you might think.
> >
> > What in your opinion would be easier - a) update RFC4291 to allow coding of
> > the link-local address 54 zero bits, or b) update RFC4861 to allow routers to use
> > site-local addresses instead of link-local?
> >
> > We need a good answer for this - either a) or b). The benefit of what is being
> > proposed by OMNI is too great to simply say no to both.
> 
> Both a and b seem to me to be equally fundamental and therefore
> equally challenging.  If the benefit is really so great (which I don't
> know), though, you should be able to persuade the WG to make the
> update - all I can say at this moment is "good luck:-)".

With all wishes for luck greatly appreciated, I will answer myself and say that
what we really want - and what we need - is *both* a) and b). Link-locals and
Site-locals both - we can put both address ranges to good use!

Thanks - Fred

> --
> JINMEI, Tatuya