draft-ietf-geopriv-res-gw-lis-discovery-06.txt   draft-ietf-geopriv-res-gw-lis-discovery-07.txt 
GEOPRIV M. Thomson GEOPRIV M. Thomson
Internet-Draft Microsoft Internet-Draft Microsoft
Intended status: Standards Track R. Bellis Intended status: Standards Track R. Bellis
Expires: March 10, 2014 Nominet UK Expires: May 08, 2014 Nominet UK
September 06, 2013 November 04, 2013
Location Information Server (LIS) Discovery using IP address and Reverse Location Information Server (LIS) Discovery using IP address and Reverse
DNS DNS
draft-ietf-geopriv-res-gw-lis-discovery-06 draft-ietf-geopriv-res-gw-lis-discovery-07
Abstract Abstract
The residential gateway is a device that has become an integral part The residential gateway is a device that has become an integral part
of home networking equipment. Discovering a Location Information of home networking equipment. Discovering a Location Information
Server (LIS) is a necessary part of acquiring location information Server (LIS) is a necessary part of acquiring location information
for location-based services. However, discovering a LIS when a for location-based services. However, discovering a LIS when a
residential gateway is present poses a configuration challenge, residential gateway is present poses a configuration challenge,
requiring a method that is able to work around the obstacle presented requiring a method that is able to work around the obstacle presented
by the gateway. by the gateway.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 10, 2014. This Internet-Draft will expire on May 08, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 35 skipping to change at page 2, line 35
4.3. Shortened DNS Names . . . . . . . . . . . . . . . . . . . 8 4.3. Shortened DNS Names . . . . . . . . . . . . . . . . . . . 8
4.4. When To Use The Reverse DNS Method . . . . . . . . . . . 9 4.4. When To Use The Reverse DNS Method . . . . . . . . . . . 9
4.5. Private Address Spaces . . . . . . . . . . . . . . . . . 9 4.5. Private Address Spaces . . . . . . . . . . . . . . . . . 9
4.6. Necessary Assumptions and Restrictions . . . . . . . . . 10 4.6. Necessary Assumptions and Restrictions . . . . . . . . . 10
4.7. Failure Modes . . . . . . . . . . . . . . . . . . . . . . 10 4.7. Failure Modes . . . . . . . . . . . . . . . . . . . . . . 10
4.8. Deployment Considerations . . . . . . . . . . . . . . . . 11 4.8. Deployment Considerations . . . . . . . . . . . . . . . . 11
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 11 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8. IAB Considerations . . . . . . . . . . . . . . . . . . . . . 13 8. IAB Considerations . . . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 14 10.1. Normative References . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 15 10.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
A Location Information Server (LIS) is a service provided by an A Location Information Server (LIS) is a service provided by an
access network. The LIS uses knowledge of the access network access network. The LIS uses knowledge of the access network
topology and other information to generate location information for topology and other information to generate location information for
Devices. Devices within an access network are able to acquire Devices. Devices within an access network are able to acquire
location information from a LIS. location information from a LIS.
skipping to change at page 8, line 38 skipping to change at page 8, line 38
corresponds to a search on a /24 or /16 network prefix. This corresponds to a search on a /24 or /16 network prefix. This
allows for fewer DNS records in the case where a single access allows for fewer DNS records in the case where a single access
network covering an entire /24 or /16 network is served by the network covering an entire /24 or /16 network is served by the
same LIS. same LIS.
o For IP version 6, the resulting domain SHOULD be shortened o For IP version 6, the resulting domain SHOULD be shortened
successively by 16, 18, 20 and 24 labels and the query repeated. successively by 16, 18, 20 and 24 labels and the query repeated.
This corresponds to a search on a /64, /56, /48 or /32 network This corresponds to a search on a /64, /56, /48 or /32 network
prefix. prefix.
This set of labels is intended to provide network operators with a
degree of flexibility in where LIS discovery records can be placed
without significantly increasing the number of DNS names that are
searched. This does not attach any other significance to these
specific zone cuts, or create a classful addressing hierachy based on
the reverse DNS tree.
For example, the IPv4 address "192.0.2.75" could result in queries For example, the IPv4 address "192.0.2.75" could result in queries
to: to:
o 75.2.0.192.in-addr.arpa. o 75.2.0.192.in-addr.arpa.
o 2.0.192.in-addr.arpa. o 2.0.192.in-addr.arpa.
o 0.192.in-addr.arpa. o 0.192.in-addr.arpa.
Similarly, the IPv6 address "2001:DB8::28e4:3a93:4429:dfb5" could Similarly, the IPv6 address "2001:DB8::28e4:3a93:4429:dfb5" could
skipping to change at page 15, line 19 skipping to change at page 15, line 30
"DNS Extensions to Support IP Version 6", RFC 3596, "DNS Extensions to Support IP Version 6", RFC 3596,
October 2003. October 2003.
[RFC5986] Thomson, M. and J. Winterbottom, "Discovering the Local [RFC5986] Thomson, M. and J. Winterbottom, "Discovering the Local
Location Information Server (LIS)", RFC 5986, September Location Information Server (LIS)", RFC 5986, September
2010. 2010.
[I-D.ietf-geopriv-held-measurements] [I-D.ietf-geopriv-held-measurements]
Thomson, M. and J. Winterbottom, "Using Device-provided Thomson, M. and J. Winterbottom, "Using Device-provided
Location-Related Measurements in Location Configuration Location-Related Measurements in Location Configuration
Protocols", draft-ietf-geopriv-held-measurements-08 (work Protocols", draft-ietf-geopriv-held-measurements-09 (work
in progress), June 2013. in progress), September 2013.
10.2. Informative References 10.2. Informative References
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets", BCP E. Lear, "Address Allocation for Private Internets", BCP
5, RFC 1918, February 1996. 5, RFC 1918, February 1996.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC
2131, March 1997. 2131, March 1997.
 End of changes. 6 change blocks. 
9 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/