Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01

神明達哉 <jinmei@wide.ad.jp> Tue, 21 April 2015 18:51 UTC

Return-Path: <jinmei.tatuya@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 C72271A8931 for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 11:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, 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 mJMH44ycPWYD for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (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 A9C6A1A1B3E for <ipv6@ietf.org>; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
Received: by iget9 with SMTP id t9so90918500ige.1 for <ipv6@ietf.org>; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=D1RjKc20ktana1M3Cwu9XQTCs6cgdiG697R2w+xodcw=; b=PVMAI1HxuaWuvFxIiaZYpqt2uYPjwsrz+nQacba0JO124GOJC0NQ4zgeWJ116qNmqD /5ehvJvKaqNWpZXMGfM5f8JblPmK6Sw+660UFlyOrKZmwCmCC12Ri8UTZD6URWLL9s3a PqKhHi77VEtIpGU0ojPFHjo7nGYTH7tb0g6fwBZiby/zJXyfxwR3qWNGdxb/kEWagOzM pIzdEajGrI7VpmFxOTt1ufKCxRNfQI568Y0OI2Rj8WGhiEjavoQfmUEnjbHtdxOztobG 05ALTwOdpt3ruQK/aSOQqhH66eN4hsLOX//mGP+YpiBxgfVWawb1e9/fwewMxk1/8okJ QDEw==
MIME-Version: 1.0
X-Received: by 10.42.128.84 with SMTP id l20mr5316216ics.21.1429642276213; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.50.80 with HTTP; Tue, 21 Apr 2015 11:51:16 -0700 (PDT)
In-Reply-To: <5536951D.60102@acm.org>
References: <16407124-2B19-4B8F-AEAC-F04D3C7E5C3A@gmail.com> <1FCBCC7C-A334-47AD-A22F-7685D1045A65@gmail.com> <CAJE_bqdh8aUzmF7UkBgicMNAM_YHBLQ5DYyuimbu9EY=d6T0Sg@mail.gmail.com> <5536951D.60102@acm.org>
Date: Tue, 21 Apr 2015 11:51:16 -0700
X-Google-Sender-Auth: TsYcYv3m8cJMhfIvpilUdgDE4ds
Message-ID: <CAJE_bqdDYFVuBSB6OVSpiOo1CW8PM+ajzcAuqo78gnP82pn3xw@mail.gmail.com>
Subject: Re: 6MAN WG Adoption Call: draft-nordmark-6man-rs-refresh-01
From: 神明達哉 <jinmei@wide.ad.jp>
To: Erik Nordmark <nordmark@acm.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TCygcBsmQL7kQL9dyJX3Tpmzmys>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
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, 21 Apr 2015 18:51:17 -0000

At Tue, 21 Apr 2015 11:21:17 -0700,
Erik Nordmark <nordmark@acm.org> wrote:

> > - Section 5:
> >     Refresh Time:  16-bit unsigned integer.  Units is seconds.  The all-
> >                    ones value (65535) means infinite.
> >
> > What should the host do if this is 0?  Should it just keep sending
> > RSes? (I'm joking).
> Good catch. I'm inclined to just make zero be reserved, and state that
> hosts should ignore an RTO if the Refresh Time is zero - i.e. treat the
> RA as if the RTO was not present.
> Is that sufficient?

I think so.

> We could pick some arbitrary number (10 seconds?) and say that it is a
> lower bound, but I don't know how to pick such a number.

Some more conservative lower bound may also help, but I don't know how
to pick one either.  It's probably enough if you add a note that care
should be taken if this field is set to some small value so it won't
cause unexpected RS storm.

> > - Section 8.2: s/be be/may be/ (?)
> >
> >     [...]  That be be performed at deployment time (e.g., only
> >     hosts which are known to support RTO are configured with the layer 2
> >     security keys), or the routers detect any RSs which do not include
> I think "could be" is better since it avoids potential confusion with
> uppercase MAY.

I'm fine with 'could be'.

--
JINMEI, Tatuya