Re: [homenet] Loops in DHCP-PD [was: 2nd Working Group Last Call...]

Ralph Droms <rdroms.ietf@gmail.com> Fri, 21 June 2013 13:54 UTC

Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADF4F21E811A for <homenet@ietfa.amsl.com>; Fri, 21 Jun 2013 06:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level:
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xtm1uQx4IQ2v for <homenet@ietfa.amsl.com>; Fri, 21 Jun 2013 06:54:40 -0700 (PDT)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id D68E711E818A for <homenet@ietf.org>; Fri, 21 Jun 2013 06:54:39 -0700 (PDT)
Received: by mail-qa0-f48.google.com with SMTP id cm16so557042qab.7 for <homenet@ietf.org>; Fri, 21 Jun 2013 06:54:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=V9gRRS06RwwnlqJx3bE4mGJylETRFfkVOesy++Kwm+I=; b=WiA2Ji9GQvHa4+oOsL6wG9q0lQRBXYtc4l/Hf6JajCIq/nGlVdI9baNUF1cpTi6417 Imxp2OxPvbeXcguPQPAmKtPPAr4MqEauzK1sf9tcJjNtqkHg1DTvLI6Pdk6rQntcgDil iSMsAGfdSjV3KEEfjiyd2ZSpYLB2yrscntzc/pl9zATzqVuSfvjMtFPE4tYABbKFd4p8 SZ8IET4i3afXlZWgRkuS3I54lTraeg1XN8c51sMCpnTijz8IQZxzC7bRFZPHRrjXGxH8 +qb69PXcqYlKGxRvroASCleO3XBIzSb/XQTiyYyiKxQ8iB7/PA0C0Wg1UFr3Nssi5iHO oxgQ==
X-Received: by 10.224.74.1 with SMTP id s1mr11239938qaj.25.1371822879131; Fri, 21 Jun 2013 06:54:39 -0700 (PDT)
Received: from ?IPv6:2001:420:2481:20:bd33:7c3c:a8e9:6b95? ([2001:420:2481:20:bd33:7c3c:a8e9:6b95]) by mx.google.com with ESMTPSA id 11sm6070104qek.1.2013.06.21.06.54.37 for <homenet@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Jun 2013 06:54:38 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <31343.1371773368@sandelman.ca>
Date: Fri, 21 Jun 2013 09:54:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D664A127-55AB-4C7C-B4BC-4986D496C833@gmail.com>
References: <53F00E5CD8B2E34C81C0C89EB0B4FE732DD5F5BF@wds-exc1.okna.nominet.org.uk> <877ghts5ko.wl%jch@pps.univ-paris-diderot.fr> <101FBDBE-2721-4CE1-B462-984AFB6DB467@employees.org> <8738shdjfc.wl%jch@pps.univ-paris-diderot.fr> <E4FC10BC-B121-4499-90AA-88048031E2C4@employees.org> <87y5a8dit5.wl%jch@pps.univ-paris-diderot.fr> <87zjunnqjw.wl%jch@pps.univ-paris-diderot.fr> <A35D9692-152A-4E21-9626-F2FC23C1C947@employees.org> <CAA93jw72sH+Et5dDHJw4m00gq8ze-uOdybn8waQOHS_j6EM77A@mail.gmail.com> <51C16A12.3030205@openwrt.org> <alpine.DEB.2.00.1306190951130.4696@uplift.swm.pp.se> <51C1789E.2050203@openwrt.org> <7761.1371646603@sandelman.ca> <87vc59ufdf.wl%jch@pps.univ-paris-diderot.fr> <31343.1371773368@sandelman.ca>
To: "homenet@ietf.org Group" <homenet@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: Re: [homenet] Loops in DHCP-PD [was: 2nd Working Group Last Call...]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 13:54:41 -0000

On Jun 20, 2013, at 8:09 PM 6/20/13, Michael Richardson <mcr+ietf@sandelman.ca> wrote:

> 
> Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>    sb> this is also what chained DHCPv6-PD / a hipnet-like solution can do.
> 
>    mcr> It can not deal with loops: I see them regularly in people's small
>    mcr> offices, and given wifi, it's really easy even for experts to create.
> 
>    juliusz> Could you please explain that?
> 
>    juliusz> I was under the impression that a prefix subdelegation is always
>    juliusz> for a longer prefix than the one it was delegated from, so at
>    juliusz> each hop the prefix gets longer.  A loop would imply that a
>    juliusz> prefix is strictly longer than itself.
> 
> Given the scenario:
> 
> ISP1      ISP2
>  \        /
>  CPE1   CPE2___
>   \      /     \
>   ~~~~~~~ wifi  \WIRE
>      |           |
>     CPE3         |
>      |           |
>      \------------
> 
> 
> PD will have CPE3 get a prefix from...?

I'm not sure whether you're asking about hierarchical PD (HIPnet) or centralized PD (draft-baker-homenet-prefix-assignment-01).

Section 3..1.2.2 of the latter addresses this issue.  The idea is that CPE3 detects RAs on wifi and WIRE and concludes it does not need to make any PD requests.

Here are three issues to be refined in draft-baker-homenet-prefix-assignment-01 (not all related to the question Michael raises), if there is interest in further development of the specification.

1) What happens if the CPE(s) don't come up in the "correct" order; e.g., suppose CPE3 comes up before CPE1 and CPE2.
2) How does an interior router (in this example, CPE3) in a multi-homed network detect that it needs some but not all prefixes?  From this example, suppose CPE1 has assigned a prefix to wifi but CPE2 has not (for some reason).  How would CPE3 determine it needs a prefix from CPE2 for wifi but not from CPE1?
3) Do CPE1 and CPE2 each do PD for their respective ISPs (requiring changes to the DHCPv6 protocol to allow multiple sources of PD) or do CPE1 and CPE2 agree that CPE1 will hand out all prefixes, and CPE2 delegates all of its prefixes from ISP2 to CPE1?

- Ralph


> CPE1? CPE2 (via WIFI) and CPE3 (via wired).
> If you look at the wires, it looks like CPE3 is simply plugged into CPE2. But
> the wires you can't see help too.  Why did you buy CPE3?  
> 
> Well, how about so that you'd have wifi coverage in the upstairs.
> (CPE3 can easily see CPE2 and CPE1, but a tablet in your bed can't)
> 
> In order for CableLabsHome to be augmented to support multiple ISPs, CPE3 has
> to get PDs from all possible "uplinks".   
> 
> Should CPE1 now also ask for a prefix (from ISP2) from CPE3, which now looks
> like an uplink to it as well.
> 
> -- 
> ]               Never tell me the odds!                 | ipv6 mesh networks [ 
> ]   Michael Richardson, Sandelman Software Works        | network architect  [ 
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
> 	
> 
> 
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet