Re: [dhcwg] Re: I-D ACTION:draft-ietf-dhc-agent-vpn-id-02.txt

> When a service provider has several customers using net-10, 
> but a single DHCP server, it needs to discriminate among them.

Ah. It would be good if the ID said that.  

> If the network device closest to the customer is configured with
> the VPN identifier for that customer network, the DHCP server
> can manage pools for each VPN independently.

So, the key requirement is for the relay agent to indicate which
customer or "address realm" (using NAT terminology) the request it is
relaying comes from. Using VPN IDs is one way, but it only works if
VPNs are used. Seems like a more general approach would be
desireable. I could imagine the same issue coming up in environments
where just IP (or IPsec tunnels) were used, in which case no L2 VPNs
would be available.

Why can't you use something like the Agent Circuit ID Sub-option
(sub-option code 1)? You could stuff  an identifier in there to
indicate which "VPN" to use.

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