Re: [NDP] Router autoconfiguration with RS/RA

"Ole Troan" <otroan@employees.org> Fri, 06 June 2008 22:47 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B2EE3A6A3F; Fri, 6 Jun 2008 15:47:47 -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 E24263A6875 for <ipv6@core3.amsl.com>; Fri, 6 Jun 2008 15:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 BOqB8UD4ss-p for <ipv6@core3.amsl.com>; Fri, 6 Jun 2008 15:47:38 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by core3.amsl.com (Postfix) with ESMTP id 6D4453A6A3F for <ipv6@ietf.org>; Fri, 6 Jun 2008 15:47:38 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so690634ywj.49 for <ipv6@ietf.org>; Fri, 06 Jun 2008 15:47:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=XqhgwnBMue6nBvuMd4BahP/pJ+1J6kIt9DoYfYny8AE=; b=Cu9e3/DLQWAlvhvnuU39fO3LJbax6CWOhdvg4eZFJHt4dvrNKfiaxkQEJaBHUwv0bU RxY/xEpVBHImW15zMB+62VCB6QbKy+pvZrqxNAMb4mGu180NrjScgQkZSmUdAavTTJ0B VfGlDO4RudmIEAi1ys/Pqc9MraStoOetB7qIQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=Ib+eURIqetGgorS9MKW93KDYOnHCp/Ls8+USCOqCNx8i3wHvuW5m0SEYqpREGCePml f5J67FihD9ctQZzLvWuxkVimnfl8FllKPjj10U5p9YoZaxV3ILAGMhB9N87YuTR4ZYx6 chROahPVxPu7IY3XgkwqtVrq2GouAc21PHafo=
Received: by 10.150.83.22 with SMTP id g22mr1052951ybb.152.1212792468527; Fri, 06 Jun 2008 15:47:48 -0700 (PDT)
Received: by 10.151.26.7 with HTTP; Fri, 6 Jun 2008 15:47:48 -0700 (PDT)
Message-ID: <2bbba3c10806061547u14bed193h8c10a76cbf04266a@mail.gmail.com>
Date: Sat, 07 Jun 2008 00:47:48 +0200
From: Ole Troan <otroan@employees.org>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: [NDP] Router autoconfiguration with RS/RA
In-Reply-To: <4849A949.5060509@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <3a44f430806060528o3ab46c73k863537e53e62275b@mail.gmail.com> <B00EDD615E3C5344B0FFCBA910CF7E1D04E41CDA@xmb-rtp-20e.amer.cisco.com> <4849A949.5060509@gmail.com>
X-Google-Sender-Auth: 022856183f6960d0
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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

2008/6/6 Alexandru Petrescu <alexandru.petrescu@gmail.com>:
> Hemant Singh (shemant) wrote:
>> Silviu,
>>
>> A router can receive an RA on the router's upstream
>
> Yes it can.  It uses it to report whether some things went wrong, log
> stuff, but don't act.
>
>> and use this RA to autoconfigure the ipv6 address on interface(s) of
>>  the router.
>
> Usually no, it can not.  A particular case of a Mobile Router away from
> home can auto-configure an address on its egress interface with
> stateless autoconf.  But a non-mobile router (not implementing rfc3963)
> can't and it shouldn't.
>
> A router is something that forwards packets.  A linux router can't
> auto-configure an address once one sets the forwarding=1.  A Cisco
> router I have doubts, but it doesn't mean it follows rfc.

a router can very well have an interface configured in host mode where
it uses normal host configuration mechanisms. it obviously can't
advertise any learnt information back out the same interface. I don't
see any reason why it couldn't also do forwarding on this interface.

router/host mode is a per interface property.

and has been said before the RS/RA mechanism for router
discovery/prefix discovery does not support prefix delegation. of
course you can invent a new protocol using RS/RA messages to do it,
but I haven't seen any convincing reason why we should. note that the
DHCP PD was triggered by a draft proposing using ICMP for PD. we
suggested using DHCP instead, since one eventually would have
reinvented lots of the DHCP machinery to make it work.

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