IETF Logo Mail Archive

Re: [NDP] Router autoconfiguration with RS/RA

Remi Denis-Courmont <rdenis@simphalempin.com> Fri, 06 June 2008 13:02 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E97A128C1A9; Fri, 6 Jun 2008 06:02:27 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1201728C1A9 for <ipv6@core3.amsl.com>; Fri, 6 Jun 2008 06:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDrfvrsxtQRj for <ipv6@core3.amsl.com>; Fri, 6 Jun 2008 06:02:27 -0700 (PDT)
Received: from yop.chewa.net (unknown [IPv6:2001:41d0:1:a0d6::401:1983]) by core3.amsl.com (Postfix) with ESMTP id C7AC628C17A for <ipv6@ietf.org>; Fri, 6 Jun 2008 06:02:26 -0700 (PDT)
Received: by yop.chewa.net (Postfix, from userid 33) id 10B23586; Fri, 6 Jun 2008 15:02:36 +0200 (CEST)
To: Silviu VLASCEANU <silviu.vlasceanu@gmail.com>
Subject: Re: [NDP] Router autoconfiguration with RS/RA
MIME-Version: 1.0
Date: Fri, 06 Jun 2008 15:02:36 +0200
From: Remi Denis-Courmont <rdenis@simphalempin.com>
Organization: Remlab.net
In-Reply-To: <3a44f430806060528o3ab46c73k863537e53e62275b@mail.gmail.com>
References: <3a44f430806060528o3ab46c73k863537e53e62275b@mail.gmail.com>
Message-ID: <40eb17363334c8d98ee68a6d97706548@chewa.net>
X-Sender: rdenis@simphalempin.com
User-Agent: RoundCube Webmail/0.1-rc2
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

On Fri, 6 Jun 2008 14:28:51 +0200, "Silviu VLASCEANU"
<silviu.vlasceanu@gmail.com> wrote:
> Why wouldn't a router be authorized to send Router Sollicitation
messages?
> Moreover, why couldn't a router autoconfigure its egress interface based
> on Router Advertisements received on this interface?

That would be useless. Lets ignore security issues. And lets even assume a
hierarchical network.

A router could learn what is "upstream" router is using RS/RA. But what's
the point? It would still not be able to route. Something needs to
configure the downstream prefixes from the downstream router to the
upstream router.
In other words, you need:
 - prefix delegation,
 - static configuration, or
 - a real routing protocol.

Once you have one of these, RS/RA is effectively useless.

> The same question for autoconfiguring the prefix it advertises on its
subnets.

You cannot do that statelessly. That's why.

-- 
Rémi Denis-Courmont
http://www.remlab.net

--------------------------------------------------------------------
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