RE: Relay Agent Options.

Hi:

The motive is that there may be options similar to the DHCPv4 relay-agent
options that will be defined in the future. This might include subscriber
ID, remote agent ID, Radius options, etc. (I am planning to write up these
I-Ds but just haven't had the time yet.) Also, the relay agent can include
the vendor options (though RFC 3315 isn't that clear about that).

Presently, a server MUST send back the Interface-ID option and can ignore
any others (except of course for the Relay Message Option).

- Bernie

> -----Original Message-----
> From: dhcwg-bounces <at> ietf.org [mailto:dhcwg-bounces <at> ietf.org] 
> On Behalf Of Achint Setia
> Sent: Friday, December 03, 2004 12:21 AM
> To: dhcwg <at> ietf.org
> Subject: [dhcwg] Relay Agent Options.
> 
> 
> 
> Hi,
> 
> I have a couple of doubts regarding the Relay Agent Options:-
> 
> 1. What is the motive behind allowing the relay agent to add options
> while     
>    forwarding the client packet to the server? Are they to be used by
> the     
>    server in configuration selection for the client?
> 
> 2. If yes, does that mean that when the server sends back the 
> Relay Reply,
>    the ONLY TWO options that can be included are the Relay Message and
> the    
>    interface id.
>    I am asking this because I am not sure as to how the relay 
> agent will
> 
>    handle options other than these two in the Relay Reply?
> 
> Hope someone can clarify them.
> 
> Thanks,
> Achint Setia.
>  
>  
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg <at> ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>