RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option

["Bernie Volz" <[e-mail]>]

A very basic question ... why have a Relay Agent Information option and have
sub-options inside this? And, especially 8-bit suboptions.
 
It seems to me that with the larger 16-bit DHCPv6 option space, we'd just
define an option to carry the "Radius Attributes" instead of placing this
under a general "Relay Agent" option. The context of the message is pretty
clear -- if it is from the relay, it can only be in a Relay-Forw (and
Relay-Reply) message option area.
 
There's also another advantage to this. Take the DHCPv4 subnet-selection
option - there are two forms of this, one in for the relay agent and another
for the client. This won't be necessary in DHCPv6 as the LOCATION of the
message (either in the Client's Solicit, Request, ... or in a
Relay-Forw/Relay-Reply) tells us who added it and which we'd prefer to use.
This means only ONE option number is needed.
 
So, I'd much rather see this specify a base option,
OPTION-RADIUS-ATTRIBUTES, and have this contain the Radius attributes in the
standard Radius encoding. So, it is just 16-bit option code, 16-bit length,
followed by the radius encoding (as 8-bit suboptions).
 
You can then specify that OPTION-RADIUS-ATTRIBUTES can only appear in the
Relay-Forw (and Relay-Reply) message and MUST NOT appear in client messages
themselves.
 
- Bernie

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of
Wing Cheong Lau
Sent: Friday, October 22, 2004 12:45 PM
To: [e-mail]
Subject: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS
Attributes sub-option


Dear all,

We have submitted a new draft on DHCPv6 Relay Information Option and RADIUS
Attributes sub-option last week. It's already available from the ietf site 

http://www.ietf.org/internet-drafts/draft-droms-dhc-v6-relayopt-00.txt

but I have not seen the official announcement so far.

The draft basically carries over similar capabilities, namely, 
RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt
from DHCPv4 to DHCPv6, with initial use cases targetting for 
the 3GPP2 environment.

Comments are welcome.

Regards,

Wing

Abstract 
    
   This document introduces the capabilities of the DHCPv4 Relay Agent 
   Information Option in RFC 3046 and the corresponding RADIUS-
   Attributes Sub-option to DHCPv6. In particular, the document 
   describes a new DHCPv6 option called the Relay Agent Information 
   option which extends the set of DHCPv6 options as defined in RFC 3315 
   and 3376. Following its DHCPv4 counterpart as defined in RFC 3046, 
   the new option is inserted by the DHCPv6 relay agent when forwarding 
   client-originated DHCPv6 packets to a DHCPv6 server. Servers 
   recognizing the Relay Agent Information option may use the 
   information to implement IP address or other parameter assignment 
   policies.  The DHCP Server echoes the option back verbatim to the 
   relay agent in server-to-client replies, and the relay agent strips 
   the option before forwarding the reply to the client. The Relay Agent 
   Information option is organized as a single DHCPv6 option that 
   contains one or more "sub-options" that convey information known by 
   the relay agent.  A RADIUS Attributes Sub-option, following its 
   DHCPv4 counterpart, is also defined.  

_______________________________________________
dhcwg mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/dhcwg