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

Ole Troan <otroan@employees.org> Wed, 22 July 2015 07:36 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 A7F811AD08F for <ipv6@ietfa.amsl.com>; Wed, 22 Jul 2015 00:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 laFs29Hj1Ttv for <ipv6@ietfa.amsl.com>; Wed, 22 Jul 2015 00:36:32 -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 0A5341ACDF0 for <ipv6@ietf.org>; Wed, 22 Jul 2015 00:36:32 -0700 (PDT)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id BD2D561CE; Wed, 22 Jul 2015 00:36:30 -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=0En0EB+MgYz+PI/VTRC1aHjfm+A=; b= JdGKPC+mlIm346xfGKARTXz70Bu+t2G6RHTKOwFe1/bvDqRZF/BxhyolC393E5Ql tOhF5q/w0pfhaYT7OWPWiCHswCccc18fj8Tc290jrKl9aA1y3tCmUHMXDQkH2E6E vvGzAAE/xLKbOcsRCHEtsXGhAdz823Cwa0cvU+Kmhpo=
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=aVDNMTCmfMCyKtA6ST2wknVMQP yHE9rAEOpY+roiebfRGtpvYQKHB2l6TM0oHFeh57RXVt9SenQGMJrkiY+UB1exXu Wcqb/TFYM53AWgHwNBDivz+7FpXGup8wRinp/0YaEYe6L3X+xxxdBsWmQEDqZl9N OOn2kc6ee5m1m0G/Y=
Received: from gomlefisk.localdomain (dhcp-aa75.meeting.ietf.org [31.133.170.117]) (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 339F8616C; Wed, 22 Jul 2015 00:36:30 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by gomlefisk.localdomain (Postfix) with ESMTP id D1F614975691; Wed, 22 Jul 2015 09:36: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 \(2102\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C92E6C7D-F2A0-49DA-8E99-BE04CE005800"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5
From: Ole Troan <otroan@employees.org>
In-Reply-To: <1563711943.88070.1437528123676.JavaMail.yahoo@mail.yahoo.com>
Date: Wed, 22 Jul 2015 09:36:48 +0200
Message-Id: <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>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/e_wWxnQSIywIGS1lpiFQv8bUQyk>
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:36:33 -0000

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.

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

cheers,
Ole