RE: draft-pioxfolks-6man-pio-exclusive-bit-02.txt

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 25 January 2018 16:20 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 E6EAD129966 for <ipv6@ietfa.amsl.com>; Thu, 25 Jan 2018 08:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 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, URIBL_BLOCKED=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 Vne1Nwsa-LuM for <ipv6@ietfa.amsl.com>; Thu, 25 Jan 2018 08:20:49 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 6B1A8126CD6 for <ipv6@ietf.org>; Thu, 25 Jan 2018 08:20:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id w0PGKm6Y049542; Thu, 25 Jan 2018 09:20:49 -0700
Received: from XCH15-06-09.nw.nos.boeing.com (xch15-06-09.nw.nos.boeing.com [137.136.239.172]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w0PGKjNR049531 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 25 Jan 2018 09:20:45 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-09.nw.nos.boeing.com (2002:8988:efac::8988:efac) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 25 Jan 2018 08:20:44 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1347.000; Thu, 25 Jan 2018 08:20:44 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>, Ole Trøan <otroan@employees.org>
CC: james woodyatt <jhw@google.com>, IPv6 List <ipv6@ietf.org>
Subject: RE: draft-pioxfolks-6man-pio-exclusive-bit-02.txt
Thread-Topic: draft-pioxfolks-6man-pio-exclusive-bit-02.txt
Thread-Index: AQHTlfR4DZ3oQiE4PE+rmu7pRLHdeaOEwxvw
Date: Thu, 25 Jan 2018 16:20:44 +0000
Message-ID: <ace794410ef645019d8fceb4dbddc044@XCH15-06-08.nw.nos.boeing.com>
References: <91953634-9B4A-405B-AB36-FBB2079A0A40@gmail.com> <CAKD1Yr3KzTQKR8kPxiMTArU1HQfn-WSZqZaBXi_vatZsf5mtvA@mail.gmail.com> <CAAedzxrts_EBhc8A6OVHAOqBB7vPhLtgPTeUwutCfYsXLbcGSw@mail.gmail.com> <CAN-Dau0RqYcRUKyFS7-Z+a3Us3Np=K_0YcuLrmg1jnxcqmN69Q@mail.gmail.com> <CAAedzxoURms4VbhxDMrnA2TdePYmBwc0Jqm6PZ7+t8kY_iS3iA@mail.gmail.com> <CAN-Dau3Ycd31AU2KbgOH-UbaQPQgq4Coo4mhEWr_x+5tHZHsmQ@mail.gmail.com> <alpine.DEB.2.20.1801111639420.8884@uplift.swm.pp.se> <CAN-Dau3aG1yxX61nH2OMeeFY+8QR649k7012n9LXVxcZs=vOHA@mail.gmail.com> <alpine.DEB.2.20.1801120848100.8884@uplift.swm.pp.se> <7AA2C836-3DC8-4402-9FE2-266B8D581308@google.com> <CEBFFA45-5334-41DC-8583-CE1F41994049@employees.org> <alpine.DEB.2.20.1801151716350.8884@uplift.swm.pp.se> <2DB23C1E-CF3B-480E-83C3-A8957A4CF32A@google.com> <alpine.DEB.2.20.1801201058170.8884@uplift.swm.pp.se> <91BF9798-BA07-4D10-AC18-79DDAE4021CF@google.com> <824c003b-38e7-284c-fa6c-a52aa84dbd8a@gmail.com> <76DD37E9-778A-4D6D-8E1C-915879F7EC00@google.com> <264a41d9-7222-8bdb-79fb-1fad2b5d2947@gmail.com> <49C7F721-D752-4D09-AF86-5A73EC41A41D@employees.org> <4A0981F5-2C52-4671-88EF-7C4DC52A751A@gmail.com>
In-Reply-To: <4A0981F5-2C52-4671-88EF-7C4DC52A751A@gmail.com>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Dl1t-nkrVEfSL0n02WoyJ8joLzU>
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: Thu, 25 Jan 2018 16:20:51 -0000

Hi Bob,

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Bob Hinden
> Sent: Thursday, January 25, 2018 7:52 AM
> To: Ole Trøan <otroan@employees.org>
> Cc: james woodyatt <jhw@google.com>; Bob Hinden <bob.hinden@gmail.com>; IPv6 List <ipv6@ietf.org>
> Subject: Re: draft-pioxfolks-6man-pio-exclusive-bit-02.txt
> 
> Ole,
> 
> > On Jan 25, 2018, at 12:22 AM, Ole Troan <otroan@employees.org> wrote:
> >
> > Brian,
> >
> >>>> But "L2 isolation is in effect" and "you are the only host in this
> >>>> prefix" are orthogonal; one, both or neither could be true. So
> >>>> two bits are needed.
> >>>
> >>>
> >>> They are not orthogonal.
> >>
> >> Well, that's a matter of definition. Neither one implies the state of the
> >> other, which is what I meant by "orthogonal".
> >>
> >>> They are entangled because the latter is not easy to do unless the former is done as well.
> >>>
> >>> Consider the specification complexity of each of the following three possible combinations.
> >>>
> >>> * Shared link + Shared prefix: status quo, already specified.
> >>>
> >>> * Isolated link + Shared prefix: very nearly status quo; host MAY safely ignore all ND Redirect, which is pretty much a trivial
> refinement of what hosts are already doing today. They still MUST perform DAD and address defense.
> >>>
> >>> * Isolated link + Exclusive prefix: not too different from Isolated link + Shared prefix, above, except hosts could also dispense with
> DAD and address defense.
> >>>
> >>> Unfortunately, the expired PIO-X draft presents the remaining combination:
> >>>
> >>> * Shared link + Exclusive prefix: we need to define rules for how hosts behave in the face of conflicting X-bits on matching PIO
> advertisements from multiple routers; including how to behave when routers send ND redirects that conflict with other routers PIO-X
> advertisements, we need a better way to redirect whole prefixes and not just addresses, e.g., the also expired I-D.templin-6man-rio-
> redirect. This is a huge mess compared to the other combinations.
> >>
> >> Exactly. There are four combinations, and each has to work. We agree on that.
> >
> > I don't think we agree on "each has to work".
> > We could very well define an initial version of PIO-X that is restricted to P2P links (or something that is made to appear to look like
> one).
> 
> Right.  I think it makes sense to focus on the Isolated link cases.

PIO-X currently defines an *unsolicited* mode of operation where the
router provides the host with an exclusive prefix that the host did not
ask for. There should also be a *solicited* mode where the host can
ask for an exclusive prefix, e.g., by including a PIO in its RS messages
to the router. In that case, it would begin to look like DHCPv6 PD.

> As you noted, it’s easy to create isolated links on shared media.  As
> stated the “shared-link + exclusive prefix” gets complex very fast, and overlaps with other solutions such as using routing protocols.

Very large shared links may not be candidates for using routing protocols.
Some NBMA links may connect thousands of nodes or more, for example.

> IMHO, better to focus on things that we can make work.

DHCPv6 PD falls under the scope of things that can work.

Thanks - Fred

> Bob