<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119   PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC5222   PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5222.xml">
<!ENTITY RFC5226   PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">
]>

<?rfc inline="yes"?>
<?rfc toc="yes" ?>
<?rfc tocdepth="2" ?> 
<?rfc symrefs="yes" ?>
<?rfc iprnotified="no" ?>
<?rfc strict="no" ?>
<?rfc compact="no" ?>
<?rfc sortrefs="yes" ?>
<!-- <?rfc colonspace='yes' ?> --> 

<rfc category="std" ipr="trust200902" updates="5222" docName="draft-ietf-ecrit-location-profile-registry-policy-02">
  <front>
    <title abbrev="LoST-Validation">Changing the LoST Location Profile Registry Policy</title>

        <author fullname="Randall Gellens" initials="R." 
            surname="Gellens">
      <organization>Core Technology Consulting</organization>
      <address>
      <postal>
          <street></street>
          <city></city>
          <region> </region>
          <code> </code>
          <country>US </country>
        </postal>
        <email>rg+ietf@coretechnologyconsulting.com</email>
        <uri>http://www.coretechnologyconsulting.com</uri>
      </address>
    </author>

<!--
    <author initials="B." surname="Rosen" fullname="Brian Rosen">
      <organization></organization>
      <address>
        <postal>
          <street>470 Conrad Dr</street>
          <city>Mars</city>
          <region> PA </region>
          <code>16046 </code>
          <country>US </country>
        </postal>
        <phone> </phone>
        <email>br@brianrosen.net
        </email>
      </address>
    </author>
-->

    <date year="2021"/>
    <area>Applications and Real Time</area>
    <workgroup>ecrit</workgroup>
    <keyword>Internet-Draft</keyword>
    <abstract>
      <t>This document changes the policy of the Location-to-Service Translation (LoST) Location Profile IANA registry established by RFC5222 from Standards Action to Specification Required.  This allows standards development organizations (SDOs) other than the IETF to add new values.</t>
    </abstract>
  </front>
  <middle>

<!--
    <section anchor="terminology" title="Terminology">
      <t>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
          <xref target="RFC2119"/>. </t>
    </section>
-->


    <section anchor="scope" title="Document Scope">
        <t>This document changes the policy of the Location-to-Service Translation (LoST) Location Profile IANA registry <xref target="reg"/> established by <xref target="RFC5222"/> from Standards Action to Specification Required (as defined in <xref target="RFC8126"/>).  This allows standards development organizations (SDOs) other than the IETF to add new values.</t>
    </section>


    <section anchor="intro" title="Introduction">
      <t>The Location-to-Service Translation Protocol, LoST <xref target="RFC5222"/> uses a location profile when conveying location (e.g., in a mapping request and a service boundary result).  <xref target="RFC5222"/> established an IANA registry of location profiles <xref target="reg"/>, with a registry policy of Standards Action.  This requires a standards-track RFC for any new registry values.  The National Emergency Number Association (NENA) is an SDO that makes significant use of LoST in its emergency call specifications (e.g., <xref target="NENA-i3"/>) and has identified a need for additional location profiles.  This document changes the registry policy to Specification Required, allowing other SDOs such as NENA to add values.</t>
    </section>


    <section anchor="security" title="Security Considerations">
      <t>No new security considerations are identified by this change in registry policy.</t>
    </section>

    <section anchor="iana" title="IANA Considerations">
        
      <t>IANA is requested to change the policy of the Location-to-Service Translation (LoST) Location Profile Registry (established by <xref target="RFC5222"/>) to Specification Required.  The expert reviewer is designated per <xref target="RFC8126"/>.  The reviewer should verify that:
<?rfc compact="yes" ?>
<?rfc subcompact="yes" ?>
        <list style="symbols">
        <t>the proposed new value is specified by the IETF, NENA, or a similar SDO in which location profiles are in scope;</t>
        <t>the proposed new value has a clear need (which includes there not being an existing profile that meets the need);</t>
        <t>the profile specification is unambiguous and interoperable.</t>
        </list>
      </t>
<?rfc compact="no" ?>
<?rfc subcompact="no" ?>
    </section> <!-- title="IANA Considerations" -->


    <!-- <section title="Contributors">
      <t></t>
    </section> -->


    <section title="Acknowledgements">
      <t>Many thanks to Ted Hardie for his helpful review and suggestions, and to Guy Caron for his suggestion to clarify that "clear need" includes there not being an existing profile.</t>
    </section>



<!--
    <section title="Changes from Previous Versions">
<?rfc compact="yes" ?>
<?rfc subcompact="yes" ?>
      <section title="Changes from -00 to -01">
        <t>
        <list style="symbols">
            <t>Fixed incorrect tag in <xref target="iana"/></t>
            <t>Clarified background and explanation in <xref target="intro"/></t>
            <t>Clarified text in <xref target="LoST-Validation"/></t>
            <t>Expanded text in <xref target="security"/></t>
        </list>
        </t>
      </section>
      <section title="Changes from -01 to -02">
        <t>
        <list style="symbols">
            <t>Fixed bug in .xml file</t>
        </list>
        </t>
      </section>
      <section title="Changes from -02 to -03">
        <t>
        <list style="symbols">
            <t>Reworded fallback text in <xref target="intro"/></t>
        </list>
        </t>
      </section>
      <section title="Changes from -03 to -04">
        <t>
        <list style="symbols">
            <t>Fixed some references to <xref target="RFC4848"/> that should be to <xref target="RFC5222"/> in sections <xref target="intro"/> and <xref target="LoST-Validation"/></t>
            <t>Added clarifying text in Abstract</t>
            <t>Copied text from Abstract to <xref target="scope"/></t>
            <t>Added clarifying text in <xref target="intro"/></t>
        </list>
        </t>
      </section>
      <section title="Changes from -04 to -05">
        <t>
        <list style="symbols">
            <t>Added reference to <xref target="RFC5222"/> in <xref target="security"/></t>
            <t>Added clarifying text to <xref target="intro"/></t>
            <t>Moved some text from <xref target="intro"/> to <xref target="LoST-Validation"/></t>
            <t>Added new section <xref target="back"/></t>
        </list>
        </t>
      </section>
      <section title="Changes from -05 to -06">
        <t>
        <list style="symbols">
            <t>Changed intended status from Informational to Standards Track</t>
            <t>Added indication that the document (if approved) updates RFC 5222</t>
            <t>Added text to Abstract, Document Scope (<xref target="scope"/>), and Introduction (<xref target="intro"/>) to better explain document purpose.</t>
            <t>Added Informational reference to <xref target="RFC5582"/></t>
            <t>Minor wording improvements in multiple sections</t>
        </list>
        </t>
      </section>
      <section title="Changes from -06 to -07">
        <t>
        <list style="symbols">
            <t>Minor editorial changes to Introduction (<xref target="intro"/>)</t>
        </list>
        </t>
      </section>
      <section title="Changes from -07 to -08">
        <t>
        <list style="symbols">
            <t>Added text in Abstract and Document Scope (<xref target="scope"/>) clarifying the updates to <xref target="RFC5582"/></t>
        </list>
        </t>
      </section>
<section title="Changes from -08 to -09">
        <t>
        <list style="symbols">
            <t>Added text in Security Considerations (<xref target="security"/>) making the use of DNS Security <xref target="RFC4033"/> a SHOULD</t>
        </list>
        </t>
      </section>
<?rfc compact="no" ?>
<?rfc subcompact="no" ?>
    </section>
-->
    

  </middle>

  <back>

    <references title="Normative References">
        <!-- &RFC2119; -->
<?rfc include="reference.RFC.5222.xml"?>
<?rfc include="reference.RFC.8126.xml"?>

          <reference anchor="reg"       target="https://www.iana.org/assignments/lost-location-profiles/lost-location-profiles.xhtml">
        <front>
            <title>Location-to-Service Translation (LoST) Location Profile Registry</title>
            <author/>
            <date />
        </front>
    </reference>


  </references>


  <references title="Informative references">

          <reference anchor="NENA-i3"
      target="https://www.nena.org/page/i3_Stage3">
        <front>
            <title>Detailed Functional and Interface Standards for the NENA i3 Solution</title>
            <author fullname="" initials="" surname="National Emergency Number Association (NENA) Interconnection and Security Committee, i3 Architecture Working Group"/>
            <date year="2016"/>
        </front>
    </reference>
  </references>

  </back>
</rfc>
