Re: I-D Action: draft-ietf-6man-resilient-rs-02.txt

Erik Nordmark <> Wed, 22 January 2014 21:54 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id AC7791A0383 for <>; Wed, 22 Jan 2014 13:54:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zMD44dICIdps for <>; Wed, 22 Jan 2014 13:54:33 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 447B01A02F0 for <>; Wed, 22 Jan 2014 13:54:33 -0800 (PST)
Received: from [] ( []) (authenticated bits=0) by (8.14.4/8.14.4) with ESMTP id s0MLsRF6004117 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 22 Jan 2014 13:54:28 -0800
Message-ID: <>
Date: Wed, 22 Jan 2014 13:54:27 -0800
From: Erik Nordmark <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ralph Droms <>, Lorenzo Colitti <>
Subject: Re: I-D Action: draft-ietf-6man-resilient-rs-02.txt
References: <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Sonic-ID: C;SM7Bw6+D4xGUEvMsIE/FGg== M;/LDzw6+D4xGUEvMsIE/FGg==
Cc:, IETF IPv6 Mailing List <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 22 Jan 2014 21:54:34 -0000

On 1/22/14 12:05 PM, Ralph Droms wrote:
> On Jan 22, 2014, at 11:55 AM 1/22/14, Lorenzo Colitti <> wrote:
>> [Resending with hopefully correct author mailing list]
>> On Wed, Jan 22, 2014 at 11:46 AM, Lorenzo Colitti <> wrote:
>> On Mon, Oct 21, 2013 at 4:38 PM, <> wrote:
>>     When an interface on a host is initialized, the host transmits Router
>>     Solicitations in order to minimize the amount of time it needs to
>>     wait until the next unsolicited multicast Router Advertisement is
>>     received.  In certain scenarios, these router solicitations
>>     transmitted by the host might be lost.  This document specifies a
>>     mechanism for hosts to cope with the loss of the initial Router
>>     Solicitations.  Furthermore, on some links, unsolicited multicast
>>     Router Advertisements are never sent and the mechanism in this
>>     document is intended to work even in such scenarios.
>> Authors,
>> One comment here.
>> If the intent is that we should be able to run networks that do not send periodic RAs at all, then this document will need to require that hosts send router solicitations when their RAs (or whatever is in the RA contents, including lifetimes of PIOs, RIOs, RDNSS options, etc.) are about to expire - otherwise the hosts will lose connectivity.
> I think it's worse than that.
> A host on a multicast-capable link on which "unsolicited multicast Router Advertisements are never sent" will have to use the same transmission behavior as a host on a non-multicast-capable link, so that the host can learn of changes in the link prefixes in a timely fashion.
> Furthermore, a host on a multicast-capable link won't know if multicast RAs are being sent on the link, so all hosts will have to send periodic RSs.

Even if you jump to a period RS from every host approach, there would 
still be operational questions on what timer to use, and whether there 
is a way for the operator to quickly introduce a new prefix (and retire 
an old prefix).

With multicast RAs the operator can change the list of prefixes (to 
handle some problem) quite quickly. To accomplish the same thing without 
the multicast RA option would imply either
  - frequent periodic RSs from all the hosts, or
  - robustly tracking the set of hosts in the routers so that unicast 
RAs can be used for such changes.


> - Ralph
>> This may be difficult to specify correctly. Specifically, it may be hard to distinguish something that is being deprecated by the network (e.g., an RA whose lifetime is counting down because it comes from a PD) from an RA that is about to expire.
>> If the intent is not that we should be able to run networks without periodic RAs, then at least the text in 2b needs to change.
>> Cheers,
>> Lorenzo
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> Administrative Requests:
>> --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> Administrative Requests:
> --------------------------------------------------------------------