--- 1/draft-ietf-ecrit-dhc-lost-discovery-00.txt 2007-03-22 16:12:21.000000000 +0100 +++ 2/draft-ietf-ecrit-dhc-lost-discovery-01.txt 2007-03-22 16:12:21.000000000 +0100 @@ -1,22 +1,22 @@ -Network Working Group H. Schulzrinne +ECRIT H. Schulzrinne Internet-Draft Columbia U. Intended status: Standards Track J. Polk -Expires: June 13, 2007 Cisco +Expires: September 21, 2007 Cisco H. Tschofenig Siemens Networks GmbH & Co KG - December 10, 2006 + March 20, 2007 A Dynamic Host Configuration Protocol (DHCP) based Location-to-Service Translation Protocol (LoST) Discovery Procedure - draft-ietf-ecrit-dhc-lost-discovery-00.txt + draft-ietf-ecrit-dhc-lost-discovery-01.txt 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 @@ -27,25 +27,25 @@ 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 June 13, 2007. + This Internet-Draft will expire on September 21, 2007. Copyright Notice - Copyright (C) The Internet Society (2006). + Copyright (C) The IETF Trust (2007). Abstract The Location-to-Service Translation Protocol (LoST) describes an XML- based protocol for mapping service identifiers and geospatial or civic location information to service contact Uniform Resource Locators (URLs). LoST servers can be located anywhere but a placement closer to the end host, e.g., in the access network, is desireable. Such a LoST server placement provides benefits in disaster situations with intermittent network connectivity regarding @@ -117,23 +117,20 @@ The domain name is encoded according to Section 3.1 of RFC 1035 [RFC1035] whereby each label is represented as a one octet length field followed by that number of octets. The domain name ends with the null label of the root, a domain name is terminated by a length byte of zero. The high order two bits of every length octet must be zero, and the remaining six bits of the length field limit the label to 63 octets or less. To simplify implementations, the total length of a domain name (i.e., label octets and label length octets) is restricted to 255 octets or less. - RFC 1035 [RFC1035] encoding was chosen to accommodate future - internationalized domain name mechanisms. - For DHCPv4 only: If the length of the domain name exceeds the maximum permissible within a single option (i.e., 254 octets), then the domain name MUST be represented in the DHCP message as specified in [RFC3396]. 4. LoST Server DHCPv4 Option The LoST server DHCPv4 option carries a DNS (RFC 1035 [RFC1035]) fully-qualified domain name to be used by the LoST client to locate a LoST server. @@ -238,22 +235,22 @@ The authors would like to thank Andrew Newton and Leslie Daigle for their draft review. We would like to particularly thank Andrew Newton for the simplifications he proposed. 10. References 10.1. Normative References [I-D.ietf-ecrit-lost] Hardie, T., "LoST: A Location-to-Service Translation - Protocol", draft-ietf-ecrit-lost-02 (work in progress), - October 2006. + Protocol", draft-ietf-ecrit-lost-05 (work in progress), + March 2007. [RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997. [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997. @@ -262,28 +259,28 @@ [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003. 10.2. Informative References [I-D.daigle-unaptr] Daigle, L., "Domain-based Application Service Location Using URIs and the Dynamic Delegation Discovery Service - (DDDS)", draft-daigle-unaptr-01 (work in progress), - October 2006. + (DDDS)", draft-daigle-unaptr-02 (work in progress), + February 2007. [I-D.ietf-ecrit-requirements] Schulzrinne, H. and R. Marshall, "Requirements for Emergency Context Resolution with Internet Technologies", - draft-ietf-ecrit-requirements-12 (work in progress), - August 2006. + draft-ietf-ecrit-requirements-13 (work in progress), + March 2007. [I-D.ietf-ecrit-security-threats] Taylor, T., "Security Threats and Requirements for Emergency Call Marking and Mapping", draft-ietf-ecrit-security-threats-03 (work in progress), July 2006. [RFC3319] Schulzrinne, H. and B. Volz, "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers", RFC 3319, July 2003. @@ -322,32 +319,32 @@ Otto-Hahn-Ring 6 Munich, Bavaria 81739 Germany Phone: +49 89 636 40390 Email: Hannes.Tschofenig@siemens.com URI: http://www.tschofenig.com Full Copyright Statement - Copyright (C) The Internet Society (2006). + Copyright (C) The IETF Trust (2007). 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. 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 + OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST 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. Intellectual Property 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