Spencer Dawkins' No Objection on draft-ietf-6man-maxra-04: (with COMMENT)

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Thu, 30 November 2017 13:30 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 80B511293F4; Thu, 30 Nov 2017 05:30:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-6man-maxra@ietf.org, otroan@employees.org, bob.hinden@gmail.com, 6man-chairs@ietf.org, bob.hinden@gmail.com, ipv6@ietf.org
Subject: Spencer Dawkins' No Objection on draft-ietf-6man-maxra-04: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151204863852.4788.13886631243889351728.idtracker@ietfa.amsl.com>
Date: Thu, 30 Nov 2017 05:30:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vewgTEc1Gwv4FeEBB5hiuOwWw5s>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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, 30 Nov 2017 13:30:38 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-6man-maxra-04: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-6man-maxra/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Everyone likely knows this, but is it worth adding a suggestion to retry
rejected RAs with a Router Lifetime of more than 9000 seconds, with a new RA
that uses 9000 seconds?

5.  Host Behavior

   Legacy hosts on a link with updated routers may have issues with a
   Router Lifetime of more than 9000 seconds.  In the few
   implementations we have tested with general purpose operating
   systems, there does not seem to be any issues with setting this field
   to more than 9000, but there might be implementations that
   incorrectly (since RFC4861 requires receivers to handle any value)
   reject such RAs.

I think this meshes with Mirja's suggestion to state whether 9000 is still the
default ...