IETF Logo Mail Archive

Re: [dhcwg] Default Route configured by DHCPv6?

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 07 October 2010 20:41 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33A8A3A6FE1 for <dhcwg@core3.amsl.com>; Thu, 7 Oct 2010 13:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level:
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[AWL=0.486, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 GJNYcc66cS8R for <dhcwg@core3.amsl.com>; Thu, 7 Oct 2010 13:41:44 -0700 (PDT)
Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [212.27.42.1]) by core3.amsl.com (Postfix) with ESMTP id 065D83A7162 for <dhcwg@ietf.org>; Thu, 7 Oct 2010 13:41:42 -0700 (PDT)
Received: from [127.0.0.1] (unknown [82.239.213.32]) by smtp1-g21.free.fr (Postfix) with ESMTP id 981B19400F7; Thu, 7 Oct 2010 22:42:40 +0200 (CEST)
Message-ID: <4CAE30B8.3020105@gmail.com>
Date: Thu, 07 Oct 2010 22:42:32 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
References: <4C8AA60F.30905@gmail.com> <201010041316.o94DGs2u021921@cichlid.raleigh.ibm.com>
In-Reply-To: <201010041316.o94DGs2u021921@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 101007-1, 07/10/2010), Outbound message
X-Antivirus-Status: Clean
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Default Route configured by DHCPv6?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 20:41:45 -0000

Le 04/10/2010 15:16, Thomas Narten a écrit :
> Alexandru Petrescu<alexandru.petrescu@gmail.com>  writes:
>
>> I need a default route configured automatically in the Mobile
>> Router connected at home.
>
> See also:
>
> http://tools.ietf.org/html/draft-droms-dhc-dhcpv6-default-router-00
>
> It's expired, but its on my TODO list to revise and resubmit.

I support the tendency of the ideas in this draft.

It currently lacks a means to encode messages conforming to DHCPv6.  Is
there some initial thought about how shoudl the default route be
communicated in a DHCPv6 message?

When I look at rfc3315, should I dig consider more "IA Address Option"?
  Or more the "Relay Message Option"?  (presumably it's the Relay's
address on which the Solicit was received that should be the default route).

Or is this the wrong way to go.

Alex

>
> Thomas
>

v2.23.0 | Report a Bug | By Email