Re: [dhcwg] Prefix length option for Dhcpv6

Tomasz Mrugalski <tomasz.mrugalski@gmail.com> Tue, 01 March 2011 22:49 UTC

Return-Path: <tomasz.mrugalski@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 A42F93A6B0E for <dhcwg@core3.amsl.com>; Tue, 1 Mar 2011 14:49:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 c8O2x85N4u2A for <dhcwg@core3.amsl.com>; Tue, 1 Mar 2011 14:49:20 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 7E2FE3A6B0B for <dhcwg@ietf.org>; Tue, 1 Mar 2011 14:49:20 -0800 (PST)
Received: by eye13 with SMTP id 13so2193674eye.31 for <dhcwg@ietf.org>; Tue, 01 Mar 2011 14:50:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=qx4Ygjvz5NspLmcSx6UgMdUMttTsfHOu7XHXAftzPLs=; b=sZqrcvFUV3F2CfFixiHB+RC0YkpO+w9LS4iupidqfGokJgi5Rwm9YkS5P2RUtWvQUd sEzQoetFFCIi7Z9DNpMwl68xoDfIGxyISUL80wtehhncB1FtSng76+9H42RjykCVk0z2 ++ncQYAt32RZwg/7vSh+yMSyAKywGJRPHR6Dw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=kWoLXPBubeo1dl5lT29nRhs1dTtOdqWrpqUYlZmLc+RKXM9nOpoIThi1BVWH0XG+gy w8xpCLgccPr4DpGJeC7iJdGDY+ri0XWjwUCceP1W9LfN4QsYDq5T+qJ5Tpzn1DaARZBR 6cmfax9FAWHTGlgWzP2OIYFLlhN8UNOHLqZPg=
Received: by 10.213.107.79 with SMTP id a15mr2953455ebp.86.1299019823850; Tue, 01 Mar 2011 14:50:23 -0800 (PST)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl [109.107.11.157]) by mx.google.com with ESMTPS id t50sm4662632eeh.6.2011.03.01.14.50.22 (version=SSLv3 cipher=OTHER); Tue, 01 Mar 2011 14:50:23 -0800 (PST)
Message-ID: <4D6D7827.3040207@gmail.com>
Date: Tue, 01 Mar 2011 23:50:15 +0100
From: Tomasz Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <AANLkTi=X9RynmHVzfjDwdYhHPJs5Hov8gGGu9d8MNFeA@mail.gmail.com> <4FD1E7CD248BF84F86BD4814EDDDBCC150EBF2F94A@EUSAACMS0703.eamcs.ericsson.se> <20110301.181929.74671719.sthaug@nethelp.no>
In-Reply-To: <20110301.181929.74671719.sthaug@nethelp.no>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-2"
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] Prefix length option for 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: Tue, 01 Mar 2011 22:49:21 -0000

On 2011-03-01 18:19, sthaug@nethelp.no wrote:
>>   This concern has been raised before and was the base for this draft.
>>
>> http://tools.ietf.org/html/draft-droms-dhc-dhcpv6-default-router-00
> 
> However, this draft is expired, and is presumably going nowhere.
> Meanwhile, people are *still* asking for it. The demand is not going
> to disappear.
There's another, current draft that deals routing configuration:
http://tools.ietf.org/html/draft-ietf-mif-dhcpv6-route-option-00

It has been adopted by MIF WG recently. Hopefully, this attempt will be
more successful. In its current form, it does not solve the problem of
conveying prefix length information along with addresses. Therefore
addresses are still supposed to be configured with /128.

-- 
Tomek Mrugalski