IETF Logo Mail Archive

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

Ralph Droms <rdroms.ietf@gmail.com> Thu, 23 January 2014 17:48 UTC

Return-Path: <rdroms.ietf@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 D78621A0131 for <ipv6@ietfa.amsl.com>; Thu, 23 Jan 2014 09:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] 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 uej11AXfvl6K for <ipv6@ietfa.amsl.com>; Thu, 23 Jan 2014 09:48:13 -0800 (PST)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 00A301A004C for <ipv6@ietf.org>; Thu, 23 Jan 2014 09:48:12 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id rq2so2116846pbb.17 for <multiple recipients>; Thu, 23 Jan 2014 09:48:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GpJE3CDiab8cagA5ylVZgAQK70et9NgpeI/RZLlbeg8=; b=0PB88rOt2CJcCYv6bFq/DBG4QapGOwsP/KycjhE2qhiMHNqUACxYniURHToQcnH4cq 1z/kFlrQ+rcCU6LBzjP/bTvtTikiJcgdlAYaTRoEk/AFEZgHQS19x9P/EdV7RVEkGXLx mojM/TPz0McMxI6Xj8CsqeJqs4+mEKzShxwMzS8oYYDUFOGIlXKij91s4s2917knxwfk pAcEOGbeoVwyFRD/odOMQfp1tYvIdyEsqaq8dBN3LlBpQTwRXomzClmT8WlRs918X150 ZBdtydQR8YrCWQ6d3Fe/gIZibzO+cXjZdH+hiD9JKZcGamnbztkN9BJ+EADeIlt4wWa8 1pcg==
X-Received: by 10.68.114.99 with SMTP id jf3mr9260177pbb.67.1390499292179; Thu, 23 Jan 2014 09:48:12 -0800 (PST)
Received: from sjc-vpn7-223.cisco.com (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPSA id xv2sm39279076pbb.39.2014.01.23.09.48.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 Jan 2014 09:48:11 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: I-D Action: draft-ietf-6man-resilient-rs-02.txt
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CAKD1Yr2eBffHBA-xSepNaJQ-az56F01pgry5sdRbTRC0VMhf_w@mail.gmail.com>
Date: Thu, 23 Jan 2014 09:48:08 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F98F9B03-C3C3-43DD-961A-7B3D41548806@gmail.com>
References: <20131021233827.32495.34424.idtracker@ietfa.amsl.com> <CAKD1Yr2eBffHBA-xSepNaJQ-az56F01pgry5sdRbTRC0VMhf_w@mail.gmail.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-6man-resilient-rs@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: <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: Thu, 23 Jan 2014 17:48:15 -0000

On Jan 22, 2014, at 11:46 AM 1/22/14, Lorenzo Colitti <lorenzo@google.com> wrote:

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

Might not be necessary to differentiate.  Regardless of why the prefix lifetime expired and whether the host has configured other , the host will likely want to send periodic RSs in case a new prefix becomes available and "unsolicited multicast Router Advertisements are never sent" implies no RA to announce new prefixes.

- Ralph

> 
> 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
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email