Re: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis

Tassos Chatzithomaoglou <achatz@forthnet.gr> Thu, 17 March 2016 10:55 UTC

Return-Path: <achatz@forthnet.gr>
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 3821A12D887 for <ipv6@ietfa.amsl.com>; Thu, 17 Mar 2016 03:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level:
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forthnet.gr
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 Wx666Sx6dcvo for <ipv6@ietfa.amsl.com>; Thu, 17 Mar 2016 03:55:38 -0700 (PDT)
Received: from zm-out-02.forthnet.gr (zm-out-02.forthnet.gr [194.219.0.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E50212D5D8 for <ipv6@ietf.org>; Thu, 17 Mar 2016 03:55:37 -0700 (PDT)
Received: from zm-in-02.cloud.forthnet.prv (zm-in-02.cloud.forthnet.prv [10.24.31.16]) by zm-out-02.forthnet.gr (Postfix) with ESMTP id 747771207D1 for <ipv6@ietf.org>; Thu, 17 Mar 2016 12:55:34 +0200 (EET)
Received: from localhost (localhost6.localdomain6 [IPv6:::1]) by zm-in-02.cloud.forthnet.prv (Postfix) with ESMTP id 57853120AD2; Thu, 17 Mar 2016 12:55:34 +0200 (EET)
X-DSPAM-Result: Spam
Authentication-Results: zm-in-02.cloud.forthnet.prv (amavisd-new); dkim=pass (1024-bit key) header.d=forthnet.gr
Received: from zm-in-02.cloud.forthnet.prv ([IPv6:::1]) by localhost (zm-in-02.cloud.forthnet.prv [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id 4vzCm7f6tBKl; Thu, 17 Mar 2016 12:55:33 +0200 (EET)
Received: from localhost (localhost6.localdomain6 [IPv6:::1]) by zm-in-02.cloud.forthnet.prv (Postfix) with ESMTP id C07DA120AD8; Thu, 17 Mar 2016 12:55:33 +0200 (EET)
DKIM-Filter: OpenDKIM Filter v2.9.2 zm-in-02.cloud.forthnet.prv C07DA120AD8
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forthnet.gr; s=zm; t=1458212133; bh=Y40Iu34s9ChRQLgIHPBiOkyN9nzneTj+1UiSlHjSgMI=; h=Subject:From:To:Message-ID:Date:MIME-Version:Content-Type: Content-Transfer-Encoding; b=NcJMBY3yJAQtd+AJL0zeaD3dUJHi4RtqSUmw8QXwS10JCoybpfMF+0+fnlUR8jdoQ AbDUVHmt5W/g0MX9oLFbCwH9DZm0ElIr2t9MCsZDTQMma43WJshCMS3VIVArwdnsR3 5fNVBrB14ICWY7eya/maNWE82Wf1n8XSGjHP4bJI=
X-Virus-Scanned: amavisd-new at zm-in-02.cloud.forthnet.prv
Received: from zm-in-02.cloud.forthnet.prv ([IPv6:::1]) by localhost (zm-in-02.cloud.forthnet.prv [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id 9ALOgzUgle-h; Thu, 17 Mar 2016 12:55:33 +0200 (EET)
Received: from [IPv6:2a02:2148:82:6000:604f:94eb:f7e1:7bee] (ip-2a02-2148-0082-6000-604f-94eb-f7e1-7bee.ip6.forthnet.gr [IPv6:2a02:2148:82:6000:604f:94eb:f7e1:7bee]) by zm-in-02.cloud.forthnet.prv (Postfix) with ESMTPA id 9B6ED120AD2; Thu, 17 Mar 2016 12:55:33 +0200 (EET)
Subject: Re: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis
References: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org> <CAJE_bqfvE0jGoRi2X=ohpqsXmGx9AVKnjeGH-P8zWp6=3_kbVA@mail.gmail.com> <CAPK2DewJ0uF9i_uaKLCn5gM_KGm2uv5B0a2VFm7cmNNn5acQPQ@mail.gmail.com> <CAJE_bqcetbtgsje4TqCpUF+zoUL19RHjWj2-xg+N39i8XodDVQ@mail.gmail.com> <517ACBE4-46C3-40C7-86E5-5906309E6BA9@employees.org> <CAJE_bqfeLxURYwMDcjMtSnyb2WBeYu_5Yq_2Yyo_O9sqHRn+og@mail.gmail.com> <73EEC8CE-EDC8-45FC-AE4F-F390F965304F@employees.org> <CAPK2DezV9vKYrHCAJJ_bFQZa02MCJMPdX7=BtL-tPzOj+da6vQ@mail.gmail.com> <CAJE_bqd316puXTvku3hMMGnThOV3JGMbLK_erQJDd6ic-BNJgA@mail.gmail.com> <CAPK2DezfW5khZyW-2wNfZ04=BSV2xq57Z52WDCoeivt4J9tvig@mail.gmail.com> <CAJE_bqfLtPmFBqZXDCfnnxZHUvzQFbicV0dweS23VjL_oEbDVg@mail.gmail.com> <CAPK2Dew4AVuZ9ssQnwSfbGu7vfS1f__8tgNWk9WFhEep7wPdGA@mail.gmail.com>
From: Tassos Chatzithomaoglou <achatz@forthnet.gr>
Organization: Forthnet
To: 6man WG <ipv6@ietf.org>
Message-ID: <56EA8D27.3060704@forthnet.gr>
Date: Thu, 17 Mar 2016 12:55:35 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAPK2Dew4AVuZ9ssQnwSfbGu7vfS1f__8tgNWk9WFhEep7wPdGA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/P2DC55GTDQ6tyVGzL6wo0fSaOyM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 17 Mar 2016 10:55:40 -0000

Just two comments:

>
>    Note:  The addresses for recursive DNS servers in the RDNSS option
>       MAY be link-local addresses.  Such link-local addresses SHOULD be
>       registered into the resolver repository along with the
>       corresponding link zone indices of the links that receive the
>       RDNSS option(s) for them.  The link-local addresses MAY be
>       represented with their link zone indices in the textual format for
>       scoped addresses as described in [RFC4007].  When a resolver sends
>       a DNS query message to an RDNSS with a link-local address, it MUST
>       use the corresponding link.

I guess "The link-local addresses MAY be represented with their link
zone indices in the textual format for scoped addresses as described in
[RFC4007]" refers to the representation on the resolver repository and
not on the RDNSS option. Maybe it should be clarified a bit ("The
link-local addresses MAY be represented in the resolver repository with
their link zone indices".


> The DNS options from Router Advertisements and DHCP
>    SHOULD be stored into the DNS Repository and Resolver Repository so
>    that information from DHCP appears there first and therefore takes
>    precedence.  Thus, the DNS information from DHCP takes precedence
>    over that from RA for DNS queries. 

I do not oppose to the above, but i would like to see an
explanation/justification (trust/security?) there.


--
Tassos