IETF Logo Mail Archive

RE: OMNI Interface - the OMNI Address

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 20 February 2020 18:19 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 02D5F12004F for <ipv6@ietfa.amsl.com>; Thu, 20 Feb 2020 10:19:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level:
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GUARANTEED_100_PERCENT=2.699, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 vkLTx7Nv0kHi for <ipv6@ietfa.amsl.com>; Thu, 20 Feb 2020 10:19:04 -0800 (PST)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 E5C4F12004E for <ipv6@ietf.org>; Thu, 20 Feb 2020 10:19:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 01KIJ1Bl008858; Thu, 20 Feb 2020 13:19:02 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1582222742; bh=SxIpj28WATh1+VBWOoSlh7a7R9PpiHqDEytFmbCNRNM=; h=From:To:Subject:Date:References:In-Reply-To:From; b=mQwFXhXj6eXHpCXZHSJQNuY6ycc9z5npG5t7H4U/M9hv2qjGAqGjD6SX7fmBIirAj COpRpT2fnu4cncM7oRXUBntAmIqnveUXIKvY6HQUouVZ3m1qhuM931m7M13soDGwhK v3/VkH3ls+9JU7/wHR239/ks2Fx9wW6nXrgIE6W7Acii29p/GVeJPPxFSOpyK2s3jQ 7vHORIC4JST2LdKv58Pbdv/+YJX66q9IZJceBlYfmwRkMy1kCdR5jHl9oF0QPhYEQ/ JTutoGMlRSroadUNxOXNaBJSPsZf+6Ru0aApoCST1lw8lr4yfZkvqVVs81jDB79liL C1k19JOvM6FIg==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 01KIIjcA007333 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Thu, 20 Feb 2020 13:18:45 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1913.5; Thu, 20 Feb 2020 10:18:44 -0800
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.1913.005; Thu, 20 Feb 2020 10:18:44 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Simon Hobson <linux@thehobsons.co.uk>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: OMNI Interface - the OMNI Address
Thread-Topic: OMNI Interface - the OMNI Address
Thread-Index: AdXme45KhfFdBlhCSUSG3aqjay+FCwBNfZ4AABnmv8A=
Date: Thu, 20 Feb 2020 18:18:44 +0000
Message-ID: <e7a76a0afce4453fb25def3f67c5257d@boeing.com>
References: <f337f97906a74677a9fa8841d076f046@boeing.com> <042D9868-690C-422A-BBD6-A618CE1EF9F0@thehobsons.co.uk>
In-Reply-To: <042D9868-690C-422A-BBD6-A618CE1EF9F0@thehobsons.co.uk>
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: DDE4157D0AE65F97DBBEC153109A201365D31F68EC4FCA890E6262E5FBECEC112000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/UqobPJBftkEqVMdmBA4lgnea1GM>
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: Thu, 20 Feb 2020 18:19:06 -0000

Hi Simon, the expectation is the same as for IPv6 prefix delegation in that the prefix delegation
service (e.g., DHCPv6) uniquely delegates a prefix to a requesting client, and does not delegate
the same prefix to multiple clients. RFC 7084 is an example where this expectation is assumed.

Can there be a case of the same prefix being delegated to multiple clients? I don't know, but
we would not intend to support that case.

Thanks - Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Simon Hobson
> Sent: Wednesday, February 19, 2020 1:50 PM
> To: ipv6@ietf.org
> Subject: Re: OMNI Interface - the OMNI Address
> 
> Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote:
> 
> > Care must be taken to form link-local addresses that are assured to be
> > unique among all nodes on the OMNI link, but without requiring Duplicate Address Detection
> > (since link-scoped multicast on the OMNI link may be intractable, and since the extra traffic
> > required for DAD on some OMNI links may be undesirable). For this reason, the OMNI spec
> > defines a simple link-local address format and construction algorithm. Namely, a Mobile Node
> > (MN) that has been assigned a Mobile Network Prefix (e.g., 2001:db8:1:2::/64) constructs its
> > OMNI address by writing the most significant 64 bits o the MNP into the least significant 64
> > bits of the IPv6 link-local prefix, i.e., as fe80::2001:db8:1:2. The uniqueness properties of the
> > link local address are therefore the same as the uniqueness properties of the MNPs assigned
> > to the MNs.
> 
> Is it guaranteed that the MNP is unique to each device - e.g., is it 100% guaranteed that there will never be two nodes sharing a
> network ?
> 
> I can see that on a typical mobile phone network, each device will have it's own /64 - but is it guaranteed that all nodes will always be
> located on networks with similar characteristics ? Could mobile nodes find themselves (even if only during development or testing) on
> (for example) an ethernet network sharing a /64 ?
> 
> Simon
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email