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

Mark Smith <markzzzsmith@gmail.com> Wed, 22 July 2015 07:51 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 CC09A1B2D47 for <ipv6@ietfa.amsl.com>; Wed, 22 Jul 2015 00:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 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, 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 BheC63h_H1_f for <ipv6@ietfa.amsl.com>; Wed, 22 Jul 2015 00:51:36 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (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 67F551B2F7B for <ipv6@ietf.org>; Wed, 22 Jul 2015 00:50:50 -0700 (PDT)
Received: by igr7 with SMTP id 7so61487487igr.0 for <ipv6@ietf.org>; Wed, 22 Jul 2015 00:50:49 -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=wZXfTH7rIMTFYqYuWNXBpa1g7xvbaWwOSLskUmnkN38=; b=ppS9BcvOACZ6vKA0imCXSns5cTbRi5NqM15njqel7RHNIK/+jd2ptN59a5ELNUatI2 l+V3uUY68m9EhU/0TkNo/nA50hh4GxpGo+wveinE7s2qTmO0fmeF/985HJCGMqLKcgm7 TBJpN3UyKfKSnGbHC+QX+1Bgmx7V3PIYjgS7Avr6M0oTU7bjojEo9hdiZz8zKGm3ah+w LGYWppamKA/7D3T1JxdsODJsfofYCp/Kd45an5OIb2XrndHc2tKYC2+aErc5nTHls9cx +GySJtHr5n6JtRKwACUknoJMrkbII47mwHDCnZkCbkB5ysSrxVbg27e7HDnD+x5W98nL iJMA==
X-Received: by 10.107.29.209 with SMTP id d200mr1952079iod.94.1437551449832; Wed, 22 Jul 2015 00:50:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.169.143 with HTTP; Wed, 22 Jul 2015 00:50:20 -0700 (PDT)
In-Reply-To: <E117C8C5-5D16-415E-BADD-210C791A7F95@employees.org>
References: <CAAedzxodZ_NBhH5HCVR29Ff_K_th=RBWHvbucQs6sqSpxoA1bw@mail.gmail.com> <73503897.2035558.1434700763863.JavaMail.yahoo@mail.yahoo.com> <1563711943.88070.1437528123676.JavaMail.yahoo@mail.yahoo.com> <E117C8C5-5D16-415E-BADD-210C791A7F95@employees.org>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 22 Jul 2015 17:50:20 +1000
Message-ID: <CAO42Z2yctYfQWh_+r3ove-OFo2mHS82yON7fibvv5br=bWk+hA@mail.gmail.com>
Subject: Re: 6MAN WG Adoption call : draft-jeong-6man-rdnss-rfc6106-bis
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5lEt50ELC8GI7Np8GFtKDrpfriI>
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, 22 Jul 2015 07:51:38 -0000

Hi Ole,

On 22 July 2015 at 17:36, Ole Troan <otroan@employees.org> wrote:
> Mark,
>
>> My comments below in part on this draft and Fernando's earlier one seem to have been ignored again.
>
> it wasn’t our intention to ignore your comments. I don’t see them as blocking for adoption, and we wanted that done first.

Ok. It is only that I've posted them a couple of times over the last
few months (once in feedback to Fernando's ID, once to this one) and
nothing in the draft seemed to have changed.

>
>> The advice to consider RDNSS and DNSSL option values to be invalid if RA lifetime has expired is inconsistent with RFC4861's advice on the use of Router Lifetimes. A RA Lifetime of zero is valid, and should not cause options within the RA to be considered invalid - that is why they have their on lifetime values. Again quoting from RFC4861,
>>
>> "The Router Lifetime applies only to
>>                     the router's usefulness as a default router; it
>>                     does not apply to information contained in other
>>                     message fields or options. "
>>
>> For example, RDNSS addresses could be link-local addresses, so the expiry of the default router information (specifically and only indicated by the Router Lifetime) would not impact the ability to use the on-link DNS resolvers. NUD and/or the DNS resolver's failure detection methods would determine if link-local addressed resolvers are still valid to send requests to.
>
> let me try to answer the point on lifetime first.
> I’m a little confused why you say the RDNSS lifetime is tied to the Router Lifetime, that certainly wasn’t the intention.
>
> the RDNSS Lifetime text is:
>                    The value of Lifetime SHOULD by
>                    default be at least 3 * MaxRtrAdvInterval where
>                    MaxRtrAdvInterval is the Maximum RA Interval defined
>                    in [RFC4861].  A value of all one bits (0xffffffff)
>                    represents infinity.  A value of zero means that the
>                    RDNSS address MUST no longer be used.
>
> the text states that the should be larger than lifetime > 3 RA advertisement interval.
> that’s to ensure that a network that runs with very short lifetimes would survive even if a few RAs are lost.
> that’s independent of those RAs having Router Lifetime of 0.
>

Here's the text that says Router Lifetime is a constraint on the
use/validity of the RDNSS and DNSSL option values:


"Note:  An RDNSS address or a DNSSL domain name MUST be used only as
      long as both the RA router Lifetime (advertised by a Router
      Advertisement message [RFC4861]) and the corresponding option
      Lifetime have not expired."



Regards,
Mark.


> cheers,
> Ole
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>