Re: Linux & draft-gont-6man-slaac-dns-config-issues
Fernando Gont <fgont@si6networks.com> Tue, 24 March 2015 16:22 UTC
Return-Path: <fgont@si6networks.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 C701F1A9036 for <ipv6@ietfa.amsl.com>; Tue, 24 Mar 2015 09:22:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 nUQ02pcyR_Wh for <ipv6@ietfa.amsl.com>; Tue, 24 Mar 2015 09:22:36 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (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 60C471A6F3F for <6man@ietf.org>; Tue, 24 Mar 2015 09:22:33 -0700 (PDT)
Received: from rrcs-50-84-137-11.sw.biz.rr.com ([50.84.137.11] helo=[192.168.1.21]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.85) (envelope-from <fgont@si6networks.com>) id 1YaRb1-0004vX-8Q; Tue, 24 Mar 2015 17:22:27 +0100
Message-ID: <55118F3B.3000308@si6networks.com>
Date: Tue, 24 Mar 2015 11:22:19 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Jen Linkova <furry13@gmail.com>
Subject: Re: Linux & draft-gont-6man-slaac-dns-config-issues
References: <55102C6B.1060608@si6networks.com> <CAKD1Yr2XfeSuQAj94kN1AF_8cet2L+uEkJnO59NyYgtwyfXu7A@mail.gmail.com> <CAKD1Yr3YBdjSkwgoAzTXs_dvoiRnSFReE5-fAO7RggvVLwDthw@mail.gmail.com> <CAFU7BASXNe6TXWt7R2+tBjiob8n23VpBV5THV5hJxSHV-wKo5A@mail.gmail.com>
In-Reply-To: <CAFU7BASXNe6TXWt7R2+tBjiob8n23VpBV5THV5hJxSHV-wKo5A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/sIJZnSn9DRU22a-CCthbLHPIQZY>
Cc: draft-gont-6man-slaac-dns-config-issues@tools.ietf.org, "6man@ietf.org" <6man@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: <http://www.ietf.org/mail-archive/web/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, 24 Mar 2015 16:22:37 -0000
Hi, Jen, On 03/24/2015 09:20 AM, Jen Linkova wrote: > On Tue, Mar 24, 2015 at 2:26 PM, Lorenzo Colitti <lorenzo@google.com> wrote: >> To clarify: I mean that we should just strike the text that specifies that >> the maximum duration SHOULD be <= 2x the router advertisement interval. That >> doesn't make sense to me. > > +1 > I agree that "<= 2x MaxRtrAdvInterval" limitation is way too strict > and we SHOULD fix this. > However I do not like the idea of sanitizing the received values and > limiting them to 10xMaxRtrAdvInterval. The thing here is that that's the only way (along with the change of the semantics of the Lifetime parameter) in which you can fix the problem on the client side. > It really sounds like a > micromanaging network administrators in how they run their networks. > There might be valid reasons to have RDNSS/DNSSL Lifetime to be close > enough to how often RAs are sent (what if a router is a DNS server > itself? So if a router does down I don't want a client to use it). If that's de goal, then the Lifetime value should be set according to the "Valid Lifetime" of the RA, rather than according to MaxRtrAdvInterval > BTW it is also a reason I'm concerned about changing the Lifetime > field semantic. > > Actually, the wording of Sanitizing section is not accurate. Clients > do not know MaxRtrAdvInterval value as it's something configured on a > router. I assume it should be "the default MaxRtrAdvInterval value of > 600 sec"? Yes. Thanks! Cheers, -- Fernando Gont SI6 Networks e-mail: fgont@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
- Linux & draft-gont-6man-slaac-dns-config-issues Fernando Gont
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Lorenzo Colitti
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Lorenzo Colitti
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Jen Linkova
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Fernando Gont
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Jen Linkova
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Fernando Gont
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Lorenzo Colitti
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Ole Troan
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Dan Lüdtke
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Jen Linkova
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Ole Troan
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Jen Linkova
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Fernando Gont
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Fernando Gont
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Lorenzo Colitti
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Jen Linkova
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Jen Linkova
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Jen Linkova
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Ole Troan
- Re: Linux & draft-gont-6man-slaac-dns-config-issu… Mark ZZZ Smith