RE: [dhcwg] dhcp6 verndor class option
"Bernie Volz" <volz@cisco.com> Wed, 01 September 2004 16:32 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 MAA05609; Wed, 1 Sep 2004 12:32:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2XMd-0005p1-3C; Wed, 01 Sep 2004 11:49:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2VGM-0004FR-4R for dhcwg@megatron.ietf.org; Wed, 01 Sep 2004 09:35:00 -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 JAA06726 for <dhcwg@ietf.org>; Wed, 1 Sep 2004 09:34:54 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2Tl0-0000q1-M3 for dhcwg@ietf.org; Wed, 01 Sep 2004 07:58:32 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 01 Sep 2004 05:03:43 +0000
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 i81BteKX013164; Wed, 1 Sep 2004 04:55:41 -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 ALF80427; Wed, 1 Sep 2004 07:55:39 -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 07:55:40 -0400
Organization: Cisco
Message-ID: <000401c4901a$9a2434b0$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: <000601c48fdf$d93bf240$db04120a@emily>
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4939.300
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable
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
Well, as we have no DHCPv6 option to carry a subscriber ID, perhaps the relay wants to communicate that to the server? So, it could send this in the vendor-specific option. Or, if the relay is on a switch, it could include the port on which the client is located. There's all sorts of possibilities. - Bernie > -----Original Message----- > From: mao shanxiang [mailto:maoshx@huawei.com] > 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] 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