Re: [homenet] I-D.ietf-homenet-prefix-assignment (RFC 4193 conformance)
James Woodyatt <jhw@nestlabs.com> Thu, 09 October 2014 19:01 UTC
Return-Path: <jhw@nestlabs.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91B01A1ABF for <homenet@ietfa.amsl.com>; Thu, 9 Oct 2014 12:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 EzL9ieTJCbg5 for <homenet@ietfa.amsl.com>; Thu, 9 Oct 2014 12:01:47 -0700 (PDT)
Received: from mail-vc0-f175.google.com (mail-vc0-f175.google.com [209.85.220.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AD311A1ABB for <homenet@ietf.org>; Thu, 9 Oct 2014 12:01:12 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id id10so1506660vcb.34 for <homenet@ietf.org>; Thu, 09 Oct 2014 12:01:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=mHOnIsju6SQ01v0vmBPTCG6qYHuvHSv2/+Ys65svx9w=; b=fkF2JJGj+7I6wWaoNhLd3thlFG5WIjk6DGL48ZA6XmM+9qID4U6SmOh6AHMaPxTgKS YnYhbLwBWH9+Nnkt+QGSXtp9CFid/oFW7uIycHUtl+mHEQ0MoS9iQNFGjXEL6oN6ft9r eIhs4QRjqEfBIdl7YZrBIqdpEs6jtf9EArRupQkH7ytFn+ZPspYYRQv7O0JzubevYptF VfVYM7qb2XPGfPvnHGQwCR7bW+ex9BTI+u3EaJFmnzrluQTltTCioHhcSsd2Kf5Cnpst Vwryc1ksB/eMk9y4REW3BPXJof0odAZbZTiNNutYt5oK+flBTwY0bgZlpVX8PK9kXD3n AsZw==
X-Gm-Message-State: ALoCoQmyILGQz3ksCe9R9m4QOYD2FIDU6kq5t7YK1JRgFoc7QvCj2B8xVurQ5xuqR1gQhRAurpQu
MIME-Version: 1.0
X-Received: by 10.52.128.104 with SMTP id nn8mr122282vdb.50.1412881271298; Thu, 09 Oct 2014 12:01:11 -0700 (PDT)
Received: by 10.31.10.65 with HTTP; Thu, 9 Oct 2014 12:01:11 -0700 (PDT)
In-Reply-To: <7E7C5904-3F5B-4B1A-A18D-C5C858B820CD@darou.fr>
References: <CADhXe52TRJy0MA861bCnWY8LjLZnGQiPbb=qXQhxCirm_DHQ0Q@mail.gmail.com> <54348606.7010507@gmail.com> <A250131C-6D1B-4054-A8AE-EBC1BD899B7E@darou.fr> <5435D586.20806@gmail.com> <20141009004559.44A9E2106591@rock.dv.isc.org> <7E7C5904-3F5B-4B1A-A18D-C5C858B820CD@darou.fr>
Date: Thu, 09 Oct 2014 12:01:11 -0700
Message-ID: <CADhXe53LfVrznxN0nFyapvO4jCNn+-xAJ77ZKxEMb9MROwSmGg@mail.gmail.com>
From: James Woodyatt <jhw@nestlabs.com>
To: HOMENET Working Group <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="bcaec520f5af4939920505020eb2"
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/lbA17gNpIBeM807DyDXg08JmpW0
Subject: Re: [homenet] I-D.ietf-homenet-prefix-assignment (RFC 4193 conformance)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 09 Oct 2014 19:01:49 -0000
On Thu, Oct 9, 2014 at 2:04 AM, Pierre Pfister <pierre.pfister@darou.fr> wrote: > > What do you think of the following proposal ? > It allows any router to generate a ULA (it adds more complexity because > collisions must be avoided, even though the Backoff was necessary at boot > anyway). > As this is a Standards Track requirements draft, I hope to be excused if I'm seeming to be overly pedantic, but this revision still leaves me concerned that we are setting requirements that do not admit Thread networks into HOMENET routing domains. Here is the excerpt that I find most troubling: ULA prefixes may be provided by DHCPv6-PD or static configuration, as specified in Section 4.3, in which case they are not considered as "spontaneously" generated and MUST NOT be withdrawn if another ULA delegated prefix is observed. My problem is that Thread networks autonomously number themselves with a ULA /64 prefix, i.e. a ULA /48 prefix with a well-known 16-bit subnet identifier. This happens when the first element in a disconnected network commissions itself. Thread networks will keep this /64 prefix as more elements are commissioned with network credentials to join the mesh. In the highly likely event that one or more elements capable of acting as Thread border routers to the HOMENET domain later join the mesh, then each of them would naturally want to advertise into the HOMENET domain this autonomously generated ULA /64 prefix. The language in this proposed revision still seems to admit only ULA delegated prefixes obtained by DHCPv6-PD and by *static* configuration, but neither of those are applicable in the case of Thread networks. I think my concern might be ameliorated by drawing a distinction in the requirements between a single distinguished Home ULA Prefix and any number of other Exterior ULA Prefix delegations. The former prefix is autonomously generated by the HOMENET router in the Leader role, whereas the latter are delegated by exterior numbering authorities outside the HOMENET domain, and they are just like any other globally scoped IPv6 network prefix. Would it be helpful if I tried to write up a proposed set of edits for this? -- james woodyatt <jhw@nestlabs.com> Nest Labs, Communications Engineering
- Re: [homenet] I-D.ietf-homenet-prefix-assignment Brian E Carpenter
- [homenet] I-D.ietf-homenet-prefix-assignment James Woodyatt
- Re: [homenet] I-D.ietf-homenet-prefix-assignment James Woodyatt
- Re: [homenet] I-D.ietf-homenet-prefix-assignment Markus Stenberg
- Re: [homenet] I-D.ietf-homenet-prefix-assignment Pierre Pfister
- Re: [homenet] I-D.ietf-homenet-prefix-assignment Pierre Pfister
- Re: [homenet] I-D.ietf-homenet-prefix-assignment James Woodyatt
- Re: [homenet] I-D.ietf-homenet-prefix-assignment James Woodyatt
- Re: [homenet] I-D.ietf-homenet-prefix-assignment Mark Townsley
- Re: [homenet] I-D.ietf-homenet-prefix-assignment … Brian E Carpenter
- Re: [homenet] I-D.ietf-homenet-prefix-assignment … Mark Andrews
- Re: [homenet] I-D.ietf-homenet-prefix-assignment … Pierre Pfister
- Re: [homenet] I-D.ietf-homenet-prefix-assignment … James Woodyatt
- Re: [homenet] I-D.ietf-homenet-prefix-assignment … Brian E Carpenter
- Re: [homenet] I-D.ietf-homenet-prefix-assignment … Pierre Pfister
- Re: [homenet] I-D.ietf-homenet-prefix-assignment … James Woodyatt
- Re: [homenet] I-D.ietf-homenet-prefix-assignment … Pierre Pfister
- Re: [homenet] I-D.ietf-homenet-prefix-assignment … James Woodyatt