One document matched: draft-rosen-rph-reg-policy-00.xml

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" []>
<rfc category="std" ipr="trust200902" docName="draft-rosen-rph-reg-policy-00">
  <?rfc toc="yes" ?>
  <?rfc symrefs="yes" ?>
  <?rfc sortrefs="yes"?>
  <?rfc compact="yes" ?>
  <?rfc iprnotified="no" ?>
  <?rfc strict="yes" ?>
  <front>
    <title abbrev="RPH Registry Management">Resource Priority Header (RPH) Registry Management Policy to IETF Review</title>
    <author fullname="Brian Rosen" initials="B.R" surname="Rosen">
      <organization>NeuStar</organization>
      <address>
        <postal>
          <street>470 Conrad Dr.</street>
          <city>Mars</city>
          <region>PA</region>
          <code>16046</code>
          <country>US</country>
        </postal>
        <phone>+1 724 382 1051</phone>
        <email>br@brianrosen.net</email>
      </address>
    </author>
    <date year="2013"/>
    <area>RAI</area>
    <workgroup>ecrit</workgroup>
    <keyword>I-D</keyword>
    <keyword>Internet-Draft</keyword>
    <keyword>Resource Priority Header</keyword>
     <abstract>
      <t>RFC4412 defines "Resource-Priority Namespaces" and 
      "Resource-Priority Priority-values" registries.
      The management policy of these registries is "Standards Action".  
      This document changes the management policy of these registries
      to "IETF Review".</t>
   </abstract>
  </front>
  <middle>
    <section anchor="security" title="Security Considerations">

      <t>This document does not introduce any the security considerations beyond those in <xref target="RFC4412"/></t>
      
    </section>

    <section title="Introduction">
      <t><xref target="RFC4412"/> defines "Resource-Priority Namespaces" and 
      "Resource-Priority Priority-values" registries. 
      The management policy of these registries is "Standards Action" as 
      defined in <xref target="RFC5226"/>.  Experience has suggested that 
      a document that only defines a new 
      namespace with its priorities, and does not create new protocol  
      semantics, should not be a standards-track document.  This document 
      updates <xref target="RFC4412"/> to change the management policy of 
      the registries to "IETF Review".</t>
    </section>
    <section title="IANA Considerations">
<t>Change the management policy of management policy of the "Resource-Priority Namespaces" and "Resource-Priority Priority-values" registries to "IETF Review" as defined in <xref target="RFC5226"/>.</t>
   </section>

 
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.4412" ?>
      <?rfc include="reference.RFC.5226" ?>
     </references>
   </back>
</rfc>