Re: a draft about on-link and submit prefixes

神明達哉 <jinmei@wide.ad.jp> Tue, 14 March 2017 18:26 UTC

Return-Path: <jinmei.tatuya@gmail.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 94EA912998F for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 11:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.402
X-Spam-Level:
X-Spam-Status: No, score=-2.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 UOO9cYsM_56B for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 11:26:43 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AAFB126CE3 for <ipv6@ietf.org>; Tue, 14 Mar 2017 11:26:43 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id p64so255081026qke.1 for <ipv6@ietf.org>; Tue, 14 Mar 2017 11:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=r1DanXygxeL7VrnRiEqXqt/tRqamu0OLz8LJI91K8ic=; b=DLhVHV6IqGtquWD+JKTCuOplrpIASK7z28KTWGgp/T8QMiTPhk3HTYJ6DTW2V4uzC3 QMHM5tvBUR1+FzpcYt0PIx9FyqH3W5NwUZpaJyogb3Tsu1U/VNfKC+XUzydZFAIEUOOs I46m5DmJZ6XRWzpXlZrplBx6C2BnzThQa5DKiK/KG9zu8Cimi5zNuaqo4ago9CwMVodv ni+2I8ZkrPdcKRBjNhFiGtU554FkpxCHdnppO3oH6T0AoVwrQ3Mk4GYt1MAOzjOPgpqf g4YpLWM+z31Csbe2eX444X+rxDLytwd354VNJQX2enRo0OjerJeRYui2GiShHhXOx//S dQIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=r1DanXygxeL7VrnRiEqXqt/tRqamu0OLz8LJI91K8ic=; b=c2xsYTIYvFgfkmIdAVQsPhJ6moNhQTD5xhTy6ddnmer9nWjIb8H5FXP8WW2NqZ5zzM X6AtlIeP14KYVwbrCd8+BXrg21sVgbtIruo4IZjOkzYr7UeL4tjiFt1W40FFXvCl8TnQ X/qIAW6DhZy0bx5mxU32YVRYEEbVBhNEDIRNwjNmVz6RQSnp3ImAwkHECW6VEiXCq9eo 4skcv8pWw86NYbpa2js1UGQpUV9/Cy/5WjfSJVV/1nO0lCZNZiA1KTz5Fma4mqy4cw7X Hm3r2y3K0b1IpZ+TzdZgyos1SwESKT4JqBgfBRcrjAvUT6EGOsJktIspm4Kg2MWZLmDv VyBg==
X-Gm-Message-State: AFeK/H24R3TupYnQPRbPs6p4k4ABbtXzDcFDv/XBdq+cKVDFgLv4/AoNL9Fn7pO1T+K0vilsKf64fQzpZD9dBw==
X-Received: by 10.55.146.135 with SMTP id u129mr37153259qkd.219.1489516002197; Tue, 14 Mar 2017 11:26:42 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.61.204 with HTTP; Tue, 14 Mar 2017 11:26:41 -0700 (PDT)
In-Reply-To: <CAKD1Yr3ncJkNwZgpWpr049K497iLAQ3dCzJ6dCHM1VsrC8UHog@mail.gmail.com>
References: <CAJE_bqdd9OXOi+SZ8_OfGWXxEoKSfoR6=Lp3-_=vEaWbjx4udw@mail.gmail.com> <CAKD1Yr3ncJkNwZgpWpr049K497iLAQ3dCzJ6dCHM1VsrC8UHog@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Tue, 14 Mar 2017 11:26:41 -0700
X-Google-Sender-Auth: JKs5-A6YKrSUJuk0eNQVBDxLvrU
Message-ID: <CAJE_bqeXEmq4e3v_Dqut602dpdWHCXrgj2Dn+oNpWn6g4LL7hA@mail.gmail.com>
Subject: Re: a draft about on-link and submit prefixes
To: Lorenzo Colitti <lorenzo@google.com>
Cc: IPv6 IPv6 List <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vUBOR8n8eBruLvcgK_4iPJEy44A>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.21
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: Tue, 14 Mar 2017 18:26:46 -0000

At Tue, 14 Mar 2017 13:06:50 +0900,
Lorenzo Colitti <lorenzo@google.com> wrote:

> > I've submitted a new individual draft on the separation between
> > on-link and (SLAAC) subnet prefixes, at the risk of stating the
> > obvious: https://datatracker.ietf.org/doc/draft-jinmei-6man-prefix-
> > clarify/
>
>
> Thanks for attempting to clarify the topic. I think it is useful to do so,
> since the distinctions here are very subtle and even many in the WG (not to
> mention in the IETF or in the industry) are not fully aware of their
> implications.

Thanks for reading the draft and for the prompt feedback.

> If possible, I would suggest making this document even more general. It's
> mostly geared to how implementations treat PIOs, and refers to RFC 4861 and
> RFC 4862, but really I think the clarifications it makes have much broader
> impact. As I see it, the core issues here are:

I see the possibility of generalization.  In particular, we could
generalize the term/concept of "subnet prefix" so that it doesn't
limit the context to SLAAC.  At least in the initial version of the
draft, however, I intentionally focused on the prefixes advertised via
PIOs in order to avoid distraction or unnecessary controversy from the
primary clarification I wanted to make first (which itself was deemed
to be sufficiently subtle).  If others also think it helpful to
generalize the discussion as a continuation of this draft, I'm happy
to revise the draft that way.

A few quick comments on the specific points:

>    - IPv6 addresses don't specify any on-link information

This one actually seems to be covered by RFC5942 (although it's a
different question whether it's well understood and/or whether a
further clarification attempts help).

>    - For most (but not all) unicast addresses, subnet prefixes are 64 bits
>    per RFC 4291.

I'm not sure if this is directly relevant to the separation of on-link
and subnet prefixes.

>    - A given subnet prefix can be spread across multiple links, and a given
>    link can support multiple subnet prefixes.

Same for the latter.  I see the former is related to the fact that
on-link prefixes are independent from subnet prefixes, but I'm not so
sure if this will be in the scope of "generalized clarification".

--
JINMEI, Tatuya