[dhcwg] question about duid in dhcpv6

Фïr <xiaoyang007@gmail.com> Fri, 02 October 2009 16:02 UTC

Return-Path: <xiaoyang007@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 D10CA28C11A for <dhcwg@core3.amsl.com>; Fri, 2 Oct 2009 09:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.507
X-Spam-Level: **
X-Spam-Status: No, score=2.507 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, DEAR_SOMETHING=1.605, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
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 3bfmVafh5Mw0 for <dhcwg@core3.amsl.com>; Fri, 2 Oct 2009 09:02:27 -0700 (PDT)
Received: from mail-iw0-f186.google.com (mail-iw0-f186.google.com [209.85.223.186]) by core3.amsl.com (Postfix) with ESMTP id 1CA6028C0FC for <dhcwg@ietf.org>; Fri, 2 Oct 2009 09:02:27 -0700 (PDT)
Received: by iwn16 with SMTP id 16so655863iwn.29 for <dhcwg@ietf.org>; Fri, 02 Oct 2009 09:03:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=A0Ax52HaN9AxHGhwp7MrwIzQGFpfFPe1nDF2O7+9WZE=; b=c8hCvnZEkJZ9Y7sBEfPHLrkcqKlCSB363ZdNmIDln7GUyM1ouyOcHTv1y7squZrpgH YqneoHgNMRyl4g9XoXQSrGaqu/Av7FDW6DXq8GjwkUlBpIjpftd4Gi+S54J2VICQfHbp yJy1oLY1seP85L1oMzriWUWVNrx3M+bRxXxGk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=K4XFKTs/z4tsXSPAma0QhLYilNCVuPu8cdYrdbWg3XSsoOXRfUXa1ffnrVN5psPqKL L99azQIj8q7zcOFCcNTDlx5JM11JsyKRVJy80mwkDLyJyvhofDzDI5dLN3/A/ezBOgMK 5kPPtJMrqJG6RrAyJWSEFpLj+ZSwIVU3vZbvw=
MIME-Version: 1.0
Received: by 10.231.25.199 with SMTP id a7mr4915737ibc.51.1254499432641; Fri, 02 Oct 2009 09:03:52 -0700 (PDT)
Date: Sat, 03 Oct 2009 00:03:52 +0800
Message-ID: <7302d480910020903u1fe8ec2dqfc5c7e0ae2a39e49@mail.gmail.com>
From: 肖�r <xiaoyang007@gmail.com>
To: dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="0015177412180db7d30474f5e934"
X-Mailman-Approved-At: Tue, 06 Oct 2009 13:40:53 -0700
Subject: [dhcwg] question about duid in 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: Fri, 02 Oct 2009 16:02:27 -0000

Dear sir,

I am a graduate student from BUPT, China. Recently, I am doing some research
to add some feature to DHCPv6. However, I have a question about the usage of
DUID field to ask you.

Considering such a scenario: server wants to send client a message with the
Server Identifier Option preserving DUID field as a special address. When
client receives the message, it will try to interpret DUID as an address for
further processing, such as verification. I am confused because in the RFC
3315, it mentions that "Clients and servers MUST treat DUIDs as opaque
values and MUST only compare DUIDs for equality. Clients and servers MUST
NOT in any other way interpret DUIDs", so I want to ask you whether it
violates the RFC 3315?

Thank you for your time and consideration.

Best Regards.

Xiao Yang