[dhcwg] dhcp6 verndor class option
Keshava <keshavaak@huawei.com> Fri, 27 August 2004 14:33 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03581; Fri, 27 Aug 2004 10:33:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C0hcY-0002ku-4K; Fri, 27 Aug 2004 10:22:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C0hbF-0000CQ-3I; Fri, 27 Aug 2004 10:21:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02511; Fri, 27 Aug 2004 10:21:01 -0400 (EDT)
Received: from mta0.huawei.com ([61.144.161.41] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0hcK-0002A1-Gv; Fri, 27 Aug 2004 10:22:16 -0400
Received: from keshavaak (mta1.huawei.com [172.17.1.60]) by mta1.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTPA id <0I33008CVYON0Y@mta1.huawei.com>; Fri, 27 Aug 2004 21:55:37 +0800 (CST)
Date: Fri, 27 Aug 2004 19:39:52 +0530
From: Keshava <keshavaak@huawei.com>
To: dhcwg@ietf.org, ipv6@ietf.org
Message-id: <001f01c48c3f$86a44f80$1604120a@keshavaak>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-Priority: 3
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: keshavaak@huawei.com, maoshx@huawei.com
Subject: [dhcwg] dhcp6 verndor class option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Keshava <keshavaak@huawei.com>
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>
Content-Type: multipart/mixed; boundary="===============0775208248=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Hi,
Can you please clarify in he RFC 3315 (DHCP6)
"Appearance of Options in Message Types" section mentions that the dhcp6 relay should support
vendor class option.
But in the message processing in the "Section 22.16 Vendor Class Option" does not mention any
thing about this for relay . It only mentions about how the client should process this.
Can some one please clarify this what should be done for dhcp6 relay ?
regards,
keshava
_______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhcp6 verndor class option Keshava
- RE: [dhcwg] dhcp6 verndor class option Bernie Volz
- Re: [dhcwg] dhcp6 verndor class option mao shanxiang
- RE: [dhcwg] dhcp6 verndor class option Bernie Volz
- RE: [dhcwg] dhcp6 verndor class option Bernie Volz