IETF Logo Mail Archive

[dhcwg] Deafult Router information for DHCPv6

Cristian Cadar <Cristian.Cadar@netlab.nec.de> Fri, 21 May 2004 09:13 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17529; Fri, 21 May 2004 05:13:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR5t2-0007Q6-QN; Fri, 21 May 2004 05:00:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR5kY-0004gW-3Q for dhcwg@optimus.ietf.org; Fri, 21 May 2004 04:51:30 -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 EAA16140 for <dhcwg@ietf.org>; Fri, 21 May 2004 04:51:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR5kV-00015g-0m for dhcwg@ietf.org; Fri, 21 May 2004 04:51:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR5jY-0000wr-00 for dhcwg@ietf.org; Fri, 21 May 2004 04:50:28 -0400
Received: from tokyo.netlab.nec.de ([195.37.70.2] helo=tokyo.ccrle.nec.de) by ietf-mx with esmtp (Exim 4.12) id 1BR5ie-0000em-00 for dhcwg@ietf.org; Fri, 21 May 2004 04:49:33 -0400
Received: from venus.office (venus.office [10.1.1.11]) by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id i4L8mvDW047189 for <dhcwg@ietf.org>; Fri, 21 May 2004 10:48:57 +0200 (CEST)
Received: from cadar.office (cadar.office [10.1.1.118]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 031AC44A90 for <dhcwg@ietf.org>; Fri, 21 May 2004 10:48:57 +0200 (CEST)
From: Cristian Cadar <Cristian.Cadar@netlab.nec.de>
Organization: NEC Europe Ltd.
To: dhcwg@ietf.org
Date: Fri, 21 May 2004 10:49:33 +0200
User-Agent: KMail/1.5.4
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200405211049.33733.Cristian.Cadar@netlab.nec.de>
X-Scanned-By: MIMEDefang 2.35
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=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Deafult Router information for DHCPv6
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

I know that this issue was already discussed on the list but I ran into a problem
which I would like to clarify here. 
Seemingly the only way for getting the default router information is to make use of 
the RA. So when I'm using dhcpv6 and want get the default router information 
is it a MUST to use the RA for this pourpose? I could not find any statement in any of the RFC/drafts saying that.
I mean for the time being I cannot see any other possibility.
There might be scenarios where the use of RA is not desired and prefering to have a dhcpv6 option
carrying this information along. If the use of RA is not a MUST I think we need a new option.


Thanks,
Cristian





_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email