IETF Logo Mail Archive

[dhcwg] RFC 3633 - Pefix Allotment by Servers

"ravi kumar" <ravikumar.lrk@gmail.com> Sun, 11 November 2007 07:03 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ir6qY-0002Bb-J5; Sun, 11 Nov 2007 02:03:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ir6qX-00029m-Ry for dhcwg@ietf.org; Sun, 11 Nov 2007 02:03:05 -0500
Received: from wa-out-1112.google.com ([209.85.146.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ir6qU-0002Wv-J3 for dhcwg@ietf.org; Sun, 11 Nov 2007 02:03:05 -0500
Received: by wa-out-1112.google.com with SMTP id k40so1736348wah for <dhcwg@ietf.org>; Sat, 10 Nov 2007 23:03:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=ZyAkVsLd9O0WPd/FzNpg7CnpqSM8hUgs3AXp36+FtoI=; b=rYec+eNx7gUGYJ+mHoulVEhHN1qRtwYyL/tOfIUfDhXIYpqr0tK4hhXBNPQd549x8uheW4tzicUIcRwDFDZ87qUQkPEDCokMG63Vw6zy/LIEC9FwizrEKi+cLHw5oowRHPZQfV/+P5KWZ/uYBKfe+yMaUSdaOVMfZKmE5Hf9Cpo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=DZQhi8KgOc5RLORbZJ5KTkfkVmkylHVJG54o4/RwnhdIQjPwZZ3szIKHPmFExInYHEVEo6TrH66qyrXCdxmwKRcMeEZLX1zbOiYNd+7gOdsmt5nvv+zoB26mSw3tvnIXfpJcMufKPsOo5Pfq9JbAX9FCnVKzcgatLIMeLyFuKV4=
Received: by 10.114.159.1 with SMTP id h1mr899956wae.1194764581945; Sat, 10 Nov 2007 23:03:01 -0800 (PST)
Received: by 10.114.193.3 with HTTP; Sat, 10 Nov 2007 23:03:01 -0800 (PST)
Message-ID: <adf2a3a0711102303q3d1e2962v1c57f317af37806a@mail.gmail.com>
Date: Sun, 11 Nov 2007 12:33:01 +0530
From: ravi kumar <ravikumar.lrk@gmail.com>
To: dhcwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [dhcwg] RFC 3633 - Pefix Allotment by Servers
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: dhcwg-bounces@ietf.org

RFC 3633 does not specify regarding "How Delegating Router selects
prefixes to be given to the clients"
Is there a common algorithm followed by the Servers that support
Prefix Delegation, for this purpose.

>From the documentation of Dibbler, I found the foolowing algorithm:

1. client didn't provide any hints: one prex from each pool will be granted
2. client has provided hint and that is valid (supported and unused):
requested prex will be granted
3. client has provided hint, which belongs to supported pool, but this
prex is used: other prex from
that pool will be asigned
4. client has provided hint, but it is invalid (not beloninging to a
supported pool, multicast or link-
local): see point 1

I would like to know, if majority of Server implementations use the
above algorithm to allot prefixes to the client.

regards
Ravi

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

v2.23.0 | Report a Bug | By Email