Re: 6MAN WG Adoption call : draft-jeong-6man-rdnss-rfc6106-bis

Mark Smith <markzzzsmith@gmail.com> Wed, 12 August 2015 01:14 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40C811B2B20 for <ipv6@ietfa.amsl.com>; Tue, 11 Aug 2015 18:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 N2fQbX3wYrD3 for <ipv6@ietfa.amsl.com>; Tue, 11 Aug 2015 18:14:53 -0700 (PDT)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (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 303BA1B2B1F for <ipv6@ietf.org>; Tue, 11 Aug 2015 18:14:53 -0700 (PDT)
Received: by igbpg9 with SMTP id pg9so102935681igb.0 for <ipv6@ietf.org>; Tue, 11 Aug 2015 18:14:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=D/zngY3YdDS62+Yn8Dq0QlFNW5OuB3Ma9wlcLbQJXi4=; b=b7xbUSlI7Trd+uHvQBVOPaeTjkONZp62t63YG0+6/DtcUHpGQu9VmnkgUOEj3lsrtG y63qQYhEBUcR1FP+66823NSCdu0CzkF93pnK/uOYpDgT9R0gMNoERFao0WJQDhcT0rR9 U1A5UPAxE5EtncrJVD6HJ0MeDwLb9UTvIB48UKkBcqQLLJg6tQiJals9Bz6PltHfMuL5 Y4Re5K6IZWw8fKkGmkEoWTK6IhXyu1VG7HB39JifAwIikC7jX5kD/k35uk4Kic0Vd+hu KYlB1VXUGEPukvqbX2fXXSSF/Ff34GJYP9Lt+djW+vNdLQ3tUzLrpQiveXepz1fTl8Mr /nXw==
X-Received: by 10.50.112.73 with SMTP id io9mr21289691igb.18.1439342092661; Tue, 11 Aug 2015 18:14:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.169.143 with HTTP; Tue, 11 Aug 2015 18:14:23 -0700 (PDT)
In-Reply-To: <CAJE_bqfb-8SBc0_f+tBfSST7-StQp_ug27r=ntRAmfjPwj=rmA@mail.gmail.com>
References: <20CE2629-7D40-4B5B-833E-4A401308027F@employees.org> <CAKD1Yr0aQ8yQR+2GyuVXJS0DrJasmqFz6RLQcodrCW982pNVGA@mail.gmail.com> <CAO42Z2wMNuPe5mmjDx5xG+3GmN-k47gsabiMQX56fiT+Kk-QcA@mail.gmail.com> <CAKD1Yr2AJ4+cvPk-XDzuxehCP+Pw-nUngxhaVMYwUvQJDK8ExA@mail.gmail.com> <CAJE_bqfb-8SBc0_f+tBfSST7-StQp_ug27r=ntRAmfjPwj=rmA@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 12 Aug 2015 11:14:23 +1000
Message-ID: <CAO42Z2wHGNhbC9+Zg3DDO_FCNxY5JxJoe2i0PK1yjF4=JgrGnA@mail.gmail.com>
Subject: Re: 6MAN WG Adoption call : draft-jeong-6man-rdnss-rfc6106-bis
To: 神明達哉 <jinmei@wide.ad.jp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/uamTh_op80rv3ChTy6xiwyftDBY>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 12 Aug 2015 01:14:54 -0000

On 12 August 2015 at 02:05, 神明達哉 <jinmei@wide.ad.jp> wrote:
> At Tue, 11 Aug 2015 21:05:29 +0900,
> Lorenzo Colitti <lorenzo@google.com> wrote:
>
>> > I think link-local addresses should be valid for RDNSS options.
>> > They're valid for applications to use (as per RFC4007), and mean that
>> > an on-link resolver service would not be impacted by GUA or ULA
>> > renumbering events.
>>
>> Saying that link-local addresses are valid seems like a reasonable position
>> to take, yes. I'd like us to note it explicitly in the document, though.
>
> I don't have a strong opinion on whether to allow link-local
> addresses per se, but if we allow that, I think we should clarify
> which link (or link zone, in RFC4007 terminology) that link-local
> address belongs to.
>  In the case of router advertisements, I guess it
> makes most sense if it's the link over which the RA is sent out and
> received.  It might even look trivial, but I still think it's better
> to clarify that explicitly.  (And, I wouldn't be surprised if someone
> disagrees with this interpretation that makes most sense to me quite
> obviously.  In that case it's even a stronger reason why this should
> better be clarified explicitly).

I don't disagree with clarifying it, however RAs themselves are
link-local scope or local to the link. With exception to these
options' possible values, the other parameter values that RAs provide
are all specific to the link the RA arrived over.

So I think any link-local address received in an RA could only be
interpreted as being on the link over which the RA arrived, as the
context of an RA is the link it was sent over.

Regards,
Mark.


>
> --
> JINMEI, Tatuya