Re: [dhcwg] Review request for draft-ietf-dhc-host-gen-id

Ted Lemon <Ted.Lemon@nominum.com> Thu, 29 March 2012 21:45 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A446321E801F for <dhcwg@ietfa.amsl.com>; Thu, 29 Mar 2012 14:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.493
X-Spam-Level:
X-Spam-Status: No, score=-106.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m2xhTygVzIb0 for <dhcwg@ietfa.amsl.com>; Thu, 29 Mar 2012 14:45:16 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id A45E421E8019 for <dhcwg@ietf.org>; Thu, 29 Mar 2012 14:45:15 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKT3TX67cSL5PKIuHJB0V84TvfwwH6weOC@postini.com; Thu, 29 Mar 2012 14:45:15 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D45BF1B8217 for <dhcwg@ietf.org>; Thu, 29 Mar 2012 14:45:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CBD32190064; Thu, 29 Mar 2012 14:45:13 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0247.003; Thu, 29 Mar 2012 14:45:13 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Sheng Jiang <jiangsheng@huawei.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Review request for draft-ietf-dhc-host-gen-id
Thread-Index: AQHNDYTEvKYY7dEar06J4LJG6pajkJaBv72A//+LmtiAAK6zgP//060q
Date: Thu, 29 Mar 2012 21:45:13 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307472D4619@mbx-01.win.nominum.com>
References: <5D36713D8A4E7348A7E10DF7437A4B921E47C59E@SZXEML506-MBS.china.huawei.com> <4F746855.8050006@gmail.com> <8D23D4052ABE7A4490E77B1A012B6307472D43BA@mbx-01.win.nominum.com>, <5D36713D8A4E7348A7E10DF7437A4B921E47CD24@SZXEML506-MBS.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B921E47CD24@SZXEML506-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] Review request for draft-ietf-dhc-host-gen-id
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 29 Mar 2012 21:45:16 -0000

> The prefix is NOT always 64. In principle, it can be 0 to 128, even the
> one assign to host. You can see this in ND prefix option as well: section
> 4.6.2 of RFC 2461.  I don't see a reason why cannot it to be greater than
> 64. Looking at SLAAC, RFC2462, it only defined prefix length + interface
> id length should be equal to 128. The interface id is typically be 64-bit
> long, but it is NOT a MUST. In principle, it can be other length as well
> as far as I understand.

The text doesn't explicitly prevent it, but in practice there is no other width that is allowed.   The prefix can't really be wider than 64 bits, and can't really be narrower.   I'd be curious to hear if you know of some concrete example to the contrary, but it's my understanding that this is pretty much written in stone.

> I am afraid this have to be bitfields. Actually, RFC3633 has already done bitfields in DHCPv6, hasn't it?

No, prefix length is 8 bits in RFC3633.