Network Working Group James M. Polk Internet-Draft Ralph Droms Expires: November 11th, 2005 Cisco Systems May 11th, 2005 Dynamic Host Configuration Protocol (DHCP) Location Configuration Information Transmitted Upstream draft-polk-geopriv-dhc-geo-lci-upstream-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on October 29, 2005. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document updates RFC 3825 to allow explicitly the transmission of DHCP option 123, "Location Configuration Information", from a DHCP client to a DHCP server. Transmission of option 123 from a client to a server allows a client that knows its location through some other means to communicate that location to the DHCP server. Polk & Droms Expires November 11th, 2005 [Page 1] Internet-Draft DHCP Geo LCI Upstream May 2005 1. Introduction This document updates RFC 3825, "Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information" [RFC3825], to allow explicitly the transmission of DHCP option 123, "Location Configuration Information", from the client to the server. This document updates RFC 3825 [RFC3825]. 1.1 Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. Transmitting DHCP Option 123 Upstream RFC3825 made communications between the client and server explicit for retrieval of location configuration information (in the coordinate format), but only explicitly discussed location information going from the server to the client. This option can be supplied to the client unrequested, or it can be requested by the client. See RFC 3825 for those details. In addition to the case in which the DHCP server explicitly provides location information to the client, it may be the case that the client has obtained its own location information through some other mechanism such as manual configuration or through a Global Positioning System (GPS). When the client has its own location information, the client MAY include that information in DHCP option 123 [RFC3825] in a DHCPDISCOVER or DHCPREQUEST message sent to the server, to supply the client's location information to the DHCP server. 3. IANA Considerations This document makes no request of the IANA. Note to RFC Editor: in the process assigning numbers and building IANA registries prior to publication, this section will have served its purpose. It may therefore be removed upon publication as an RFC. 4. Security Considerations Where critical decisions might be based on the value of this LCI option, DHCP authentication in [RFC3118] SHOULD be used to protect the integrity of the DHCP options. Polk & Droms Expires November 11th, 2005 [Page 2] Internet-Draft DHCP Geo LCI Upstream May 2005 Since there is no privacy protection for DHCP messages, an eavesdropper who can monitor the link between the client and destination DHCP server to capture this LCI. When implementing a DHC server that will serve clients across an uncontrolled network, one should consider the potential security risks. 5. Acknowledgements To Ted Hardie for comments leading to this document's creation. 6. References 6.1 Normative References [RFC3825] Polk, J., Schnizlein, J., Linsner, M., " Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information", RFC 3825, July 2004 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3046] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, January 2001. [RFC3118] Droms, R. and W. Arbaugh, "Authentication for DHCP Messages", RFC 3118, June 2001. [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997. Author's Address James M. Polk Cisco Systems 3913 Treemont Circle Colleyville, Texas 76034 USA Phone: +1-817-271-3552 Email: jmpolk@cisco.com Ralph Droms Cisco Systems 1414 Massachusetts Avenue Boxborough, MA 01719 Polk & Droms Expires November 11th, 2005 [Page 3] Internet-Draft DHCP Geo LCI Upstream May 2005 Phone: +1-978-936-1674 Email: rdroms@cisco.com Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Polk & Droms Expires November 11th, 2005 [Page 4]