RE: [dhcwg] dhcp6 verndor class option

"Bernie Volz" <volz@cisco.com> Wed, 01 September 2004 02:00 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 WAA23257; Tue, 31 Aug 2004 22:00:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2KA8-0001lt-LL; Tue, 31 Aug 2004 21:43:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2K5h-0000dv-8I; Tue, 31 Aug 2004 21:39:16 -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 VAA22035; Tue, 31 Aug 2004 21:39:11 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2K7m-0005HL-33; Tue, 31 Aug 2004 21:41:23 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-5.cisco.com with ESMTP; 31 Aug 2004 18:32:18 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i811Vqb7004788; Tue, 31 Aug 2004 18:31:53 -0700 (PDT)
Received: from volzw2k (che-vpn-cluster-2-207.cisco.com [10.86.242.207]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ALF64861; Tue, 31 Aug 2004 21:31:51 -0400 (EDT)
From: Bernie Volz <volz@cisco.com>
To: 'Keshava' <keshavaak@huawei.com>, dhcwg@ietf.org, ipv6@ietf.org
Subject: RE: [dhcwg] dhcp6 verndor class option
Date: Tue, 31 Aug 2004 21:31:50 -0400
Organization: Cisco
Message-ID: <000101c48fc3$748d79c0$6401a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-Reply-To: <001f01c48c3f$86a44f80$1604120a@keshavaak>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: quoted-printable
Cc: maoshx@huawei.com
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: quoted-printable

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