Re: routers - (was: Re: "ROUTERS" vs. "routers")

Fred Templin <ftemplin@iprg.nokia.com> Wed, 26 November 2003 22:44 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01270 for <ipv6-archive@odin.ietf.org>; Wed, 26 Nov 2003 17:44:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AP8Oe-0007vS-Up for ipv6-archive@odin.ietf.org; Wed, 26 Nov 2003 17:44:34 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQMiWcu030465 for ipv6-archive@odin.ietf.org; Wed, 26 Nov 2003 17:44:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AP8Oe-0007vI-Q7 for ipv6-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 17:44:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01225 for <ipv6-web-archive@ietf.org>; Wed, 26 Nov 2003 17:44:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AP8Oc-00060G-00 for ipv6-web-archive@ietf.org; Wed, 26 Nov 2003 17:44:30 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AP8Ob-00060C-00 for ipv6-web-archive@ietf.org; Wed, 26 Nov 2003 17:44:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AP8OA-0007ph-BY; Wed, 26 Nov 2003 17:44:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AP8NK-0007oj-Ac for ipv6@optimus.ietf.org; Wed, 26 Nov 2003 17:43:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01180 for <ipv6@ietf.org>; Wed, 26 Nov 2003 17:42:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AP8NH-0005zI-00 for ipv6@ietf.org; Wed, 26 Nov 2003 17:43:07 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AP8NH-0005yk-00 for ipv6@ietf.org; Wed, 26 Nov 2003 17:43:07 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id hAQMgMN31936; Wed, 26 Nov 2003 14:42:22 -0800
X-mProtect: <200311262242> Nokia Silicon Valley Messaging Protection
Received: from ftemplin.iprg.nokia.com (205.226.2.67, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdfmo7Ht; Wed, 26 Nov 2003 14:42:21 PST
Message-ID: <3FC52E31.8050008@iprg.nokia.com>
Date: Wed, 26 Nov 2003 14:50:25 -0800
From: Fred Templin <ftemplin@iprg.nokia.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ipv6@ietf.org
CC: crawdad@fnal.gov, ftemplin@iprg.nokia.com
Subject: Re: routers - (was: Re: "ROUTERS" vs. "routers")
References: <Pine.LNX.4.44.0311261223240.6104-100000@netcore.fi> <3FC4FB34.7050909@iprg.nokia.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: 7bit
Content-Transfer-Encoding: 7bit


Fred Templin wrote:

> The two ways I see to do this are to either specify a new IPv6 ND option
> (call it a "Type II Router Solicitation" for lack of a better name) or 
> to add
> bits to the existing IPv6 Router Soliciation message (e.g., in the 
> "Reserved"
> field) that indicate the type of information being solicited. 


To respond to my own post, it just occurred to me there may be
a  least one other possibility (and probably countless others) to
get the needed message types. Maybe we could hijack an unused
ICMPv6 Type code from the IANA registries?

A quick look at the 'icmpv6-parameters' registry shows:

 138  Router Renumbering                               [Crawford]
 139  ICMP Node Information Query                      [Crawford]
 140  ICMP Node Information Response                   [Crawford]

I see that the Router Renumbering option is used by RFC 2894,
but does anyone know if the other options are used anywhere?

If not, the "Node Information Query" would be a perfect fit
for the "Type II Router Solicitation" I've been asking about,
and the "Node Information Response" could be used to carry
the Route Information Options needed by:

  
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-router-selection-02.txt

instead of hacking the IPv6 Router Advertisment message format.
Sounds like a win-win, doesn't it?

Matt, can you comment as to the availability of the Type codes?

Thanks - Fred
ftemplin@iprg.nokia.com





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