RE: [dhcwg] dhcp6 verndor class option

"Bernie Volz" <volz@cisco.com> Wed, 01 September 2004 17:18 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 NAA12281; Wed, 1 Sep 2004 13:18:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Xa0-0002sz-0L; Wed, 01 Sep 2004 12:03:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Wk0-0002VQ-7M for dhcwg@megatron.ietf.org; Wed, 01 Sep 2004 11:09:40 -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 LAA24981 for <dhcwg@ietf.org>; Wed, 1 Sep 2004 11:09:37 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2WmD-00051B-8l for dhcwg@ietf.org; Wed, 01 Sep 2004 11:11:57 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 01 Sep 2004 11:21:37 -0400
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i81F91ZQ008187; Wed, 1 Sep 2004 11:09:06 -0400 (EDT)
Received: from volzw2k (dhcp-10-86-160-46.cisco.com [10.86.160.46]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ALF94279; Wed, 1 Sep 2004 11:09:00 -0400 (EDT)
From: Bernie Volz <volz@cisco.com>
To: 'mao shanxiang' <maoshx@huawei.com>, 'Keshava' <keshavaak@huawei.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] dhcp6 verndor class option
Date: Wed, 01 Sep 2004 11:09:00 -0400
Organization: Cisco
Message-ID: <000501c49035$9c60ea00$2ea0560a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300
In-Reply-To: <000601c48fdf$d93bf240$db04120a@emily>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: 7bit
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

This is completely up to the server. See DHCP Relay Agent Information Option
(RFC 3046) for more details as to how this is may be used in DHCPv4. This
really is no different for DHCPv6, just that the way the information is
carried is different and is vendor-specific -- though likely there will be
standardized relay agent options to carry information in the future.

- Bernie

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] 
> On Behalf Of mao shanxiang
> Sent: Wednesday, September 01, 2004 12:55 AM
> To: Bernie Volz; 'Keshava'; dhcwg@ietf.org
> Subject: Re: [dhcwg] dhcp6 verndor class option
> 
> 
> 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
> 


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