IETF Logo Mail Archive

RE: <draft-ietf-6man-rfc4291bis-09.txt>

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Sat, 22 July 2017 23:34 UTC

Return-Path: <albert.e.manfredi@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 85F07128AB0 for <ipv6@ietfa.amsl.com>; Sat, 22 Jul 2017 16:34:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 XQjPyncad7H2 for <ipv6@ietfa.amsl.com>; Sat, 22 Jul 2017 16:34:42 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 4E880126BF0 for <ipv6@ietf.org>; Sat, 22 Jul 2017 16:34:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v6MNYecd015152; Sat, 22 Jul 2017 16:34:40 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v6MNYY6R014774 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Sat, 22 Jul 2017 16:34:36 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (137.136.239.220) by XCH15-06-10.nw.nos.boeing.com (137.136.239.219) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Sat, 22 Jul 2017 16:34:33 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1263.000; Sat, 22 Jul 2017 16:34:33 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: <draft-ietf-6man-rfc4291bis-09.txt>
Thread-Topic: <draft-ietf-6man-rfc4291bis-09.txt>
Thread-Index: AQHTAwCAjdXC4YWz5kiBDEudqkiPiqJgfLiQ
Date: Sat, 22 Jul 2017 23:34:33 +0000
Message-ID: <c094a88573474142bd2b41ef47551596@XCH15-06-11.nw.nos.boeing.com>
References: <20150804195752.5065.13523.idtracker@ietfa.amsl.com> <5AB14F48-2799-4A86-830D-E8A89CCADAAC@gmail.com> <CAKD1Yr0Bt4hhBvtSVWrLpns4odzek3U5WJkuQoS1NGsPozW0sg@mail.gmail.com> <CAN-Dau3vVREsYc4Y6AAdDpLKsMjwH_2saS7JTn8P6fRDXRKV7Q@mail.gmail.com> <596F63F4.9010501@foobar.org> <fe7a1def-e656-c6d8-5336-ed5595331b74@gmail.com> <ed0fde09ae2a4a598c9a84eb0df659e8@XCH15-06-11.nw.nos.boeing.com> <69a7f9f2-584e-a2bc-1200-64fad8f9baf7@gmail.com> <652efa7dcb414b7ba6128bb4f93a3d7e@XCH15-06-11.nw.nos.boeing.com> <CAJE_bqfbLzfSYBBuS58CB6EWYkLLoqgGnb==v0CSScfZBFp=HQ@mail.gmail.com> <m1dYUCB-0000F6C@stereo.hq.phicoh.net> <bf2ab8d8-9070-c53f-90bd-831630021749@gmail.com> <m1dYwTM-0000FzC@stereo.hq.phicoh.net>
In-Reply-To: <m1dYwTM-0000FzC@stereo.hq.phicoh.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vvXlr81vN1SyuINAXksAaZL_qa8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 22 Jul 2017 23:34:43 -0000

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Philip Homburg

> So let me call them 'host part'

So we would be renaming IID in every RFC. Quite a change. And it's not "host" anyway, right? Those bits identify an interface, not a host. So call it "interface part," or "interface ID."

> Basically a 'host part' doesn't have any properties.

But that's not a distinction. I can just as easily give a structure to an IID as I can to any non-64-bit IID, if I so choose. Or, use a pseudo random value if I'm worried about privacy or security.

> You can say it identifies an interface, but that is not the case if
> a 'host part' is part of an anycast address.

Not sure why you make this distinction. Even in the anycast address, these last bits identify an interface, even if one of several possible. It's the topologically closest interface, and others would be identified by the same bit pattern. It's still an ID of an interface, as opposed to being a prefix.

I just don't see why IIDs used in SLAAC should be thought of differently. I mean, the anycast example was always a little weird, but those are a tiny minority anyway.

Bert

v2.23.0 | Report a Bug | By Email