Re: [Geopriv] Last Call: <draft-ietf-geopriv-res-gw-lis-discovery-07.txt> (Location Information Server (LIS) Discovery using IP address and Reverse DNS) to Proposed Standard

--001a11c25700a4366704ecd13433
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

Some of you may notice that a couple of unusual things about this LC:
1. It is the third LC for this document.
2. It is only a week long.

The second LC was because the IESG decided to change the state of the
proposed RFC from Informational to Proposed Standard.  Unfortunately, while
the document was updated, the datatracker was not, so the email for the
second LC said "Information" even though the document said "Proposed
Standard".  So we are running an abbreviated third LC with the correct
status indicated in both places to ensure that everyone has sufficient
notice.

Thanks,
--Richard





On Thu, Dec 5, 2013 at 2:29 PM, The IESG <[email protected]> wrote:

>
> The IESG has received a request from the Geographic Location/Privacy WG
> (geopriv) to consider the following document:
> - 'Location Information Server (LIS) Discovery using IP address and
>    Reverse DNS'
>   <draft-ietf-geopriv-res-gw-lis-discovery-07.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> [email protected] mailing lists by 2013-12-12. Exceptionally, comments may be
> sent to [email protected] instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    The residential gateway is a device that has become an integral part
>    of home networking equipment.  Discovering a Location Information
>    Server (LIS) is a necessary part of acquiring location information
>    for location-based services.  However, discovering a LIS when a
>    residential gateway is present poses a configuration challenge,
>    requiring a method that is able to work around the obstacle presented
>    by the gateway.
>
>    This document describes a solution to this problem.  The solution
>    provides alternative domain names as input to the LIS discovery
>    process based on the network addresses assigned to a Device.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-discovery/
>
> IESG discussion can be tracked via
>
> http://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-discovery/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> Geopriv mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/geopriv
>

--001a11c25700a4366704ecd13433
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>Some of you may notice that a c=
ouple of unusual things about this LC:</div><div>1. It is the third LC for =
this document.</div><div>2. It is only a week long.</div><div><br></div><di=
v>
The second LC was because the IESG decided to change the state of the propo=
sed RFC from Informational to Proposed Standard. =A0Unfortunately, while th=
e document was updated, the datatracker was not, so the email for the secon=
d LC said &quot;Information&quot; even though the document said &quot;Propo=
sed Standard&quot;. =A0So we are running an abbreviated third LC with the c=
orrect status indicated in both places to ensure that everyone has sufficie=
nt notice. =A0</div>
<div><br></div><div>Thanks,</div><div>--Richard</div><div><br></div><div><b=
r></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Thu, Dec 5, 2013 at 2:29 PM, The IESG <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">iesg-secr=
[email protected]</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
The IESG has received a request from the Geographic Location/Privacy WG<br>
(geopriv) to consider the following document:<br>
- &#39;Location Information Server (LIS) Discovery using IP address and<br>
=A0 =A0Reverse DNS&#39;<br>
=A0 &lt;draft-ietf-geopriv-res-gw-lis-discovery-07.txt&gt; as Proposed Stan=
dard<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:[email protected]">[email protected]</a> mailing lists by 2013-12=
-12. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:[email protected]">[email protected]</a> instead. In eith=
er case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=A0 =A0The residential gateway is a device that has become an integral part=
<br>
=A0 =A0of home networking equipment. =A0Discovering a Location Information<=
br>
=A0 =A0Server (LIS) is a necessary part of acquiring location information<b=
r>
=A0 =A0for location-based services. =A0However, discovering a LIS when a<br=
>
=A0 =A0residential gateway is present poses a configuration challenge,<br>
=A0 =A0requiring a method that is able to work around the obstacle presente=
d<br>
=A0 =A0by the gateway.<br>
<br>
=A0 =A0This document describes a solution to this problem. =A0The solution<=
br>
=A0 =A0provides alternative domain names as input to the LIS discovery<br>
=A0 =A0process based on the network addresses assigned to a Device.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-di=
scovery/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-geop=
riv-res-gw-lis-discovery/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-geopriv-res-gw-lis-di=
scovery/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ie=
tf-geopriv-res-gw-lis-discovery/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
_______________________________________________<br>
Geopriv mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/geopriv" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/geopriv</a><br>
</blockquote></div><br></div>

--001a11c25700a4366704ecd13433--