<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dhc-anonymity-profile" target="https://datatracker.ietf.org/doc/html/draft-ietf-dhc-anonymity-profile-01">
   <front>
      <title>Anonymity profile for DHCP clients</title>
      <author initials="C." surname="Huitema" fullname="Christian Huitema">
         </author>
      <author initials="T." surname="Mrugalski" fullname="Tomek Mrugalski">
         </author>
      <author initials="S." surname="Krishnan" fullname="Suresh Krishnan">
         </author>
      <date month="June" day="30" year="2015" />
      <abstract>
	 <t>   Some DHCP options carry unique identifiers.  These identifiers can
   enable device tracking even if the device administrator takes care of
   randomizing other potential identifications like link-layer addresses
   or IPv6 addresses.  The anonymity profile is designed for clients
   that wish to remain anonymous to the visited network.  The profile
   provides guidelines on the composition of DHCP or DHCPv6 requests,
   designed to minimize disclosure of identifying information.  This
   draft updates RFC4361.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dhc-anonymity-profile-01" />
   
</reference>
