IETF Logo Mail Archive

Re: [dhcwg] Prefix length option for Dhcpv6

Suresh Krishnan <suresh.krishnan@ericsson.com> Tue, 01 March 2011 15:49 UTC

Return-Path: <suresh.krishnan@ericsson.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 6122E3A68BF for <dhcwg@core3.amsl.com>; Tue, 1 Mar 2011 07:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.344
X-Spam-Level:
X-Spam-Status: No, score=-102.344 tagged_above=-999 required=5 tests=[AWL=0.254, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 rvsi3qu3EvEO for <dhcwg@core3.amsl.com>; Tue, 1 Mar 2011 07:49:22 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 26E8B3A67AE for <dhcwg@ietf.org>; Tue, 1 Mar 2011 07:49:19 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p21GcdGq030340; Tue, 1 Mar 2011 10:38:47 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.208]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 1 Mar 2011 10:50:13 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: ravi kumar <ravikumar.lrk@gmail.com>, DHC WG <dhcwg@ietf.org>
Date: Tue, 01 Mar 2011 10:50:12 -0500
Thread-Topic: [dhcwg] Prefix length option for Dhcpv6
Thread-Index: AcvX8R4+GQJt9ZEBQiKLUKLpU2F7lgANw11A
Message-ID: <4FD1E7CD248BF84F86BD4814EDDDBCC150EBF2F94A@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTi=X9RynmHVzfjDwdYhHPJs5Hov8gGGu9d8MNFeA@mail.gmail.com>
In-Reply-To: <AANLkTi=X9RynmHVzfjDwdYhHPJs5Hov8gGGu9d8MNFeA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_4FD1E7CD248BF84F86BD4814EDDDBCC150EBF2F94AEUSAACMS0703e_"
MIME-Version: 1.0
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 15:49:23 -0000

Hi Ravi,
  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


Thanks
Suresh


________________________________
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of ravi kumar
Sent: Tuesday, March 01, 2011 1:15 AM
To: DHC WG
Subject: [dhcwg] Prefix length option for Dhcpv6


Since the Dhcpv6 client receives a /128 address from Dhcp server, the length of prefix would not be known to the client unless there are RA's on link with prefix advertised. Is this not a limitation in the sense that, stand-alone dhcpv6 address is not useful ? Consider the case of Dhcpv4, where client receives subnet mask aong with the address. Is there any equivalent option in Dhcpv6 for this purpose ? The main concern is that in a router-less network (which might make sense in a small network), the Dhcpv6 address is of not much use with clients not able to reach each other over ipv6.

regards

Ravi

v2.23.0 | Report a Bug | By Email