Re: Update to <draft-ietf-ipv6-router-selection-07.txt>

Pekka Savola <pekkas@netcore.fi> Sun, 29 May 2005 18:48 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DcSq8-00055j-4u; Sun, 29 May 2005 14:48:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DcSq6-00055e-Gn for ipv6@megatron.ietf.org; Sun, 29 May 2005 14:48:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03313 for <ipv6@ietf.org>; Sun, 29 May 2005 14:48:45 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DcT9L-0002p0-E6 for ipv6@ietf.org; Sun, 29 May 2005 15:08:40 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id j4TImIk28399; Sun, 29 May 2005 21:48:20 +0300
Date: Sun, 29 May 2005 21:48:18 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Bob Hinden <bob.hinden@nokia.com>
In-Reply-To: <6.2.1.2.2.20050520095504.02c65808@mailhost.iprg.nokia.com>
Message-ID: <Pine.LNX.4.61.0505292143330.27653@netcore.fi>
References: <6.2.1.2.2.20050520095504.02c65808@mailhost.iprg.nokia.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Brian Haberman <brian@innovationslab.net>, IPv6 WG <ipv6@ietf.org>
Subject: Re: Update to <draft-ietf-ipv6-router-selection-07.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

On Fri, 20 May 2005, Bob Hinden wrote:
> To clear what we hope is the last IESG "Discuss" comment on this document, 
> the AD's plan to add a note after the third paragraph in the Introduction 
> section (that starts with "This document describes an optional extension to 
> Neighbor Discovery Router Advertisement messages.....") as an RFC-Editor 
> note.  The text is:
>
>  Note that since these procedures are applicable to hosts only,
>  the forwarding algorithm used by the routers (including hosts
>  with enabled IP forwarding) is not affected.
>
> We wanted to pass this by the working group to see if any objects to this 
> change.  We think the additional text is fine.

This seems like a good clarification in general, but it wouldn't hurt 
if it was grounded more strongly on how it follows that routers don't 
use these procedures.

AFAICS, the routers don't use this stuff simply because they're not 
supposed to listen to RAs (but having exact quote & reference would 
be good).

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------