RE: IPv6 Work Group Last Call for "Default Router Preferences and More-Specific Routes"

"Bound, Jim" <jim.bound@hp.com> Sat, 22 May 2004 12:08 UTC

Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02670 for <ipngwg-archive@lists.ietf.org>; Sat, 22 May 2004 08:08:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRV6g-0004R6-PU; Sat, 22 May 2004 07:56:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRUzD-0003J5-A3 for ipv6@optimus.ietf.org; Sat, 22 May 2004 07:48:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01441 for <ipv6@ietf.org>; Sat, 22 May 2004 07:48:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRUzC-00045n-CC for ipv6@ietf.org; Sat, 22 May 2004 07:48:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRUyJ-0003wW-00 for ipv6@ietf.org; Sat, 22 May 2004 07:47:24 -0400
Received: from zmamail05.zma.compaq.com ([161.114.64.105]) by ietf-mx with esmtp (Exim 4.12) id 1BRUxW-0003mW-00 for ipv6@ietf.org; Sat, 22 May 2004 07:46:34 -0400
Received: from tayexg12.americas.cpqcorp.net (tayexg12.americas.cpqcorp.net [16.103.130.103]) by zmamail05.zma.compaq.com (Postfix) with ESMTP id 301CE92B3; Sat, 22 May 2004 07:46:34 -0400 (EDT)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg12.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.0); Sat, 22 May 2004 07:46:33 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: IPv6 Work Group Last Call for "Default Router Preferences and More-Specific Routes"
Date: Sat, 22 May 2004 07:46:29 -0400
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B0644C13B@tayexc13.americas.cpqcorp.net>
Thread-Topic: IPv6 Work Group Last Call for "Default Router Preferences and More-Specific Routes"
Thread-Index: AcQyN/HMm0yKOk7WROSnNVkhzHtGPwNuk8rg
From: "Bound, Jim" <jim.bound@hp.com>
To: Bob Hinden <bob.hinden@nokia.com>, ipv6@ietf.org
X-OriginalArrivalTime: 22 May 2004 11:46:33.0960 (UTC) FILETIME=[6E5F6E80:01C43FF2]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: ipv6-admin@ietf.org
Errors-To: ipv6-admin@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Id: IP Version 6 Working Group (ipv6) <ipv6.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable

Bob and Brian,

I am fine with this and it is good spec.  One question in my mind is do
we want to use up precious RSVD bits in the RA message or make this an
option?  It would also work as option as I see it and save using up the
RA RSVD header bits.

thanks
/jim 

> -----Original Message-----
> From: ipv6-admin@ietf.org [mailto:ipv6-admin@ietf.org] On 
> Behalf Of Bob Hinden
> Sent: Tuesday, May 04, 2004 8:14 PM
> To: ipv6@ietf.org
> Subject: IPv6 Work Group Last Call for "Default Router 
> Preferences and More-Specific Routes"
> 
> This is a IPv6 working group last call for comments on 
> advancing the following document as an Proposed Standard:
> 
> 	Title		: Default Router Preferences and 
> More-Specific Routes
> 	Author(s)	: R. Draves, D. Thaler
> 	Filename	: draft-ietf-ipv6-router-selection-03.txt
> 	Pages		: 13
> 	Date		: 2003-12-18
> 
> This is a two week working group last call that will end on 
> May 18, 2004.
> 
> Please direct substantive comments to the IPv6 mailing list.  
> Editorial comments can be sent directly to the authors.
> 
> Regards,
> Bob & Brian
> IPv6 WG co-chairs
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
> 

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