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

Ole Troan <otroan@employees.org> Tue, 11 August 2015 17:18 UTC

Return-Path: <otroan@employees.org>
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 D11741ACDE9 for <ipv6@ietfa.amsl.com>; Tue, 11 Aug 2015 10:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.711
X-Spam-Level:
X-Spam-Status: No, score=-1.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 MHEjkGAtrvrV for <ipv6@ietfa.amsl.com>; Tue, 11 Aug 2015 10:18:50 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1AC21ACDE0 for <ipv6@ietf.org>; Tue, 11 Aug 2015 10:18:50 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id BF4D56164; Tue, 11 Aug 2015 10:18:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=0MHxInI+EpH4e5G4/B/bQrRKOZw=; b= Dd3QLJpyLfdrSYaXcQpbDDzRgwN2VzsGWkqLRLSPil1v4kbraAo5wy/PWOnIbEW3 +3Re9RJN5KWv0evHGonLSSNSjCuD4h19QDG1d+stZJ0lNXK/BG2X4fmiCapsW6bd PaOWeJXGRMdVqhygxYG739psOxCX2Riwor4kgNCjdmA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=lVi2agWSvZ4TGf5S9U7ZQeZ276 UWFpuM+2ZnxbPlmq1kwZK9GSsIfsy08Bj3QyeL91J5CYel2+Su5G15vobDIwrQ/6 BcnmbvcW6YftbeDghvEx+YYfIat1A4arQsvW/0MmDXY+GLRWskFH3Wcvbl7uPIVf l7N5taP2sybHslu3o=
Received: from gomlefisk.localdomain (cm-84.215.10.233.getinternet.no [84.215.10.233]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 8E7F960FF; Tue, 11 Aug 2015 10:18:49 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by gomlefisk.localdomain (Postfix) with ESMTP id A99424A8B73D; Tue, 11 Aug 2015 19:18:49 +0200 (CEST)
Subject: Re: 6MAN WG Adoption call : draft-jeong-6man-rdnss-rfc6106-bis
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_04ACCD63-DA55-4AF2-A085-3933CA1AF3F7"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAJE_bqfb-8SBc0_f+tBfSST7-StQp_ug27r=ntRAmfjPwj=rmA@mail.gmail.com>
Date: Tue, 11 Aug 2015 19:18:49 +0200
Message-Id: <B2E1EDB4-8581-4160-BC5C-827FAEFD86F9@employees.org>
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>
To: 神明達哉 <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6CAmvrB-_2AUJ_Mvkkg0-tEZ_lY>
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: Tue, 11 Aug 2015 17:18:52 -0000

> 
>>> 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).

it can’t possibly apply to a different link as there wouldn’t be any way to signal that.
3646 is silent on the issue of link-locals, my preference would be to stay silent in 6106bis too.
it isn’t obvious to me that common resolver libraries support link-local addresses?

cheers,
Ole