IETF Logo Mail Archive

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

Fernando Gont <fgont@si6networks.com> Thu, 17 March 2016 13:13 UTC

Return-Path: <fgont@si6networks.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 51F2B12D941 for <ipv6@ietfa.amsl.com>; Thu, 17 Mar 2016 06:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 BBqoftQHJyUx for <ipv6@ietfa.amsl.com>; Thu, 17 Mar 2016 06:13:02 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A15D512D919 for <ipv6@ietf.org>; Thu, 17 Mar 2016 06:12:29 -0700 (PDT)
Received: from [172.20.15.144] (port-213-160-6-163.static.qsc.de [213.160.6.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id E8D3880180; Thu, 17 Mar 2016 14:12:27 +0100 (CET)
Subject: Re: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis
To: Lorenzo Colitti <lorenzo@google.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
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> <56EA8D27.3060704@forthnet.gr> <CAPK2DeyT-K1LR3+dAuLiuS2L=xr7Q4e2N-QZAoWHRC_cQSFKzw@mail.gmail.com> <CAKD1Yr142AT1UKfdQG4D9HaROJKKJN8Zj+ywj3sp9T-qNq7wNQ@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56EAAD36.20901@si6networks.com>
Date: Thu, 17 Mar 2016 10:12:22 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr142AT1UKfdQG4D9HaROJKKJN8Zj+ywj3sp9T-qNq7wNQ@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tI2LFvjRCXtKtnTibXHJEF63SDk>
Cc: 6man WG <ipv6@ietf.org>
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 13:13:13 -0000

On 03/17/2016 10:04 AM, Lorenzo Colitti wrote:
> On Thu, Mar 17, 2016 at 9:37 PM, Mr. Jaehoon Paul Jeong
> <jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>> wrote:
> 
>     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. This is because IPv6 hosts usually prefer DHCP to 
>     RA for their network configuration. Thus, the DNS information 
>     from DHCP takes precedence over that from RA for DNS queries.
> 
> 
> Um... "DHCP should be first because hosts prefer DHCP to be first,
> therefore DHCP should be first"? That's circular reasoning.
> 
> I'm not even sure "IPv6 hosts usually prefer DHCP to RA for their
> network configuration" is a true statement. Do we have data on that?

The v6ops draft that you don't like covers this one.


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email