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.
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.

John

At 03:54 PM 11/6/2002, Thomas Narten wrote:
>Looking  through this document, could someone explain what problem
>this ID is solving?
>
>In particular, it seems to me that DHCP servers/relay agents shouldn't
>and don't need to understand about VPNs.  I.e., when a node joins the
>network, it is assigned a VPN. This ID proposes that a relay agent
>include a string or other identifier in the relay agent option to
>indicate the VPN the client is assigned to. But, it seems to me that
>the relay agent could just as easily be assigned an IP address on each
>VPN, and then just stuff that address into the giaddr field of the
>packets. This is normal DHC, using existing protocols and standards.
>In this case, neither the relay agent nor the DHC server need to know
>about VPNs in any way other than they already do. I.e, the giaddr
>field indicates a VPN, and existing standard DHC config technique can
>be used to assign addresses and other paramaters to the client.
>
>What is it that I'm not understanding here?
>
>Thomas
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg

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