Re: [dhcwg] dhcp6 verndor class option

mao shanxiang <maoshx@huawei.com> Wed, 01 September 2004 14:53 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 KAA22218; Wed, 1 Sep 2004 10:53:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2SF1-0006IZ-M0; Wed, 01 Sep 2004 06:21:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2NQ4-0003Ul-Ls for dhcwg@megatron.ietf.org; Wed, 01 Sep 2004 01:12:28 -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 BAA07133 for <dhcwg@ietf.org>; Wed, 1 Sep 2004 01:12:28 -0400 (EDT)
Received: from mta1.huawei.com ([61.144.161.40] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2NSB-0000Tu-Sm for dhcwg@ietf.org; Wed, 01 Sep 2004 01:14:40 -0400
Received: from emily (huawei.com [172.17.1.62]) by mta0.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0I3C007M4J3WMG@mta0.huawei.com> for dhcwg@ietf.org; Wed, 01 Sep 2004 12:57:34 +0800 (CST)
Date: Wed, 01 Sep 2004 10:25:04 +0530
From: mao shanxiang <maoshx@huawei.com>
Subject: Re: [dhcwg] dhcp6 verndor class option
To: Bernie Volz <volz@cisco.com>, 'Keshava' <keshavaak@huawei.com>, dhcwg@ietf.org
Message-id: <000601c48fdf$d93bf240$db04120a@emily>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
X-imss-version: 2.7
X-imss-result: Passed
X-imss-approveListMatch: *@huawei.com
References: <000101c48fc3$748d79c0$6401a8c0@amer.cisco.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 01 Sep 2004 06:21:21 -0400
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Bernie,

if relay includes such option, what is the behavior of the server? the
server can return information in the Relay-Reply, but what is the usage for
server to analyze such option info? give different policy?

can you please clarify me?

Regards,
Emily

----- Original Message ----- 
From: "Bernie Volz" <volz@cisco.com>
To: "'Keshava'" <keshavaak@huawei.com>; <dhcwg@ietf.org>; <ipv6@ietf.org>
Cc: <maoshx@huawei.com>
Sent: Wednesday, September 01, 2004 7:01 AM
Subject: RE: [dhcwg] dhcp6 verndor class option


If there's relay specific information that could be used by a server (or
other relay), there is no reason the relay can't include this in its
Relay-Forw message (and the server return information in the Relay-Reply).

Note that Appendix A, Appearance of Options in Message Types, indicates that
these are valid:

            Status  Rap. User  Vendor Vendor Inter. Recon. Recon.
             Code  Comm. Class Class  Spec.    ID    Msg.  Accept
   R-forw.                 *     *      *      *
   R-repl.                 *     *      *      *

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
Keshava
Sent: Friday, August 27, 2004 10:10 AM
To: dhcwg@ietf.org; ipv6@ietf.org
Cc: keshavaak@huawei.com; maoshx@huawei.com
Subject: [dhcwg] dhcp6 verndor class option


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