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

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

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24982 for <ipv6-archive@odin.ietf.org>; Wed, 26 Nov 2003 15:07:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AP5wf-0005Em-FN for ipv6-archive@odin.ietf.org; Wed, 26 Nov 2003 15:07:29 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAQK7Tii020126 for ipv6-archive@odin.ietf.org; Wed, 26 Nov 2003 15:07:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AP5wf-0005EX-60 for ipv6-web-archive@optimus.ietf.org; Wed, 26 Nov 2003 15:07:29 -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 PAA24905 for <ipv6-web-archive@ietf.org>; Wed, 26 Nov 2003 15:07:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AP5wc-0003tZ-00 for ipv6-web-archive@ietf.org; Wed, 26 Nov 2003 15:07:26 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AP5wb-0003tW-00 for ipv6-web-archive@ietf.org; Wed, 26 Nov 2003 15:07:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AP5wD-00054U-M6; Wed, 26 Nov 2003 15:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AP5vm-00053f-CA for ipv6@optimus.ietf.org; Wed, 26 Nov 2003 15:06:34 -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 PAA24809 for <ipv6@ietf.org>; Wed, 26 Nov 2003 15:06:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AP5vj-0003t0-00 for ipv6@ietf.org; Wed, 26 Nov 2003 15:06:31 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AP5vh-0003sj-00 for ipv6@ietf.org; Wed, 26 Nov 2003 15:06:30 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id hAQK5iT02632; Wed, 26 Nov 2003 12:05:44 -0800
X-mProtect: <200311262005> 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 smtpdROv78o; Wed, 26 Nov 2003 12:05:43 PST
Message-ID: <3FC5097B.6090304@iprg.nokia.com>
Date: Wed, 26 Nov 2003 12:13:47 -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: Pekka Savola <pekkas@netcore.fi>
CC: Nick 'Sharkey' Moore <sharkey@zoic.org>, ipv6@ietf.org
Subject: Re: routers - (was: Re: "ROUTERS" vs. "routers")
References: <Pine.LNX.4.44.0311262139430.16739-100000@netcore.fi>
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

Pekka,

I meant only what I said - nodes should be able to selectively solicit
at least two different classes of information from routers. (Perhaps
there will be even more classes of information in the future; I
don't know).

Some routers might advertise only prefix/autoconfig information,
so they might not respond to the "Type II Router Solicitation" I
alluded to below. Other routers might advertise only route
information, so they might not respond to an ordinary IPv6
Router Solicitation. Still other routers might advertise both
classes of information, so they might happily respond to
either type of solicitation.

I'm not necessarily trying to write the MAY/SHOULD/MUSTs
here; I'm simply identifying the need and soliciting input from
the wg; thanks for providing yours.

Fred
ftempling@iprg.nokia.com
 

Pekka Savola wrote:

>On Wed, 26 Nov 2003, Fred Templin wrote:
>  
>
>>However, the message that must not be lost in the terminology shuffle
>>is that it very much *does* matter that nodes be able to selectively
>>solicit at least two different classes of information from routers:
>>
>>  1) Classical prefix/autoconfig information as specified in RFC 2461
>>  2) Route Information Options as specified in:
>>    
>>http://www.ietf.org/internet-drafts/draft-ietf-ipv6-router-selection-02.txt
>>
>>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.
>>    
>>
>
>I do not see the issue you describe.  You can solicit exactly this
>kind of information from any node you wish, right?
>
>Naturally, the hosts won't answer; some routers might not either
>(e.g., if they aren't configured to advertise such information) -- but
>that's not really relevant -- anyone can elect to be silent if they
>wish!
>
>Are you suggesting that all routers be somehow "forced" to return this
>kind of information (when asked explicitly in some defined manner)
>whether they advertise it or not?
>
>That probably would not fly.  
>
>Or are you suggesting that routers should be able to advertise (or 
>tell, when asked explicitly) about the information they know about 
>prefixes/autoconfig/routes, without the hosts implying they would act 
>as a default router as well?  Not sure I'd see a point for something 
>like that..
>
>If you meant something else, I didn't understand ..
>
>  
>



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