One document matched: draft-rosen-geopriv-prefix-00.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc4119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4119.xml">
<!ENTITY rfc4776 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4776.xml">
<!ENTITY rfc5139 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5139.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc compact="yes"?>
<rfc category="info" docName="draft-rosen-geopriv-prefix-00" ipr="trust200902">
  <front>
    <title abbrev='Road and House Prefix'>
      Prefix elements for Road and House Numbers in PIDF-LO
    </title>

    <author fullname="Brian Rosen" initials="B.R." surname="Rosen">
      <organization abbrev="NeuStar">NeuStar, Inc.</organization>

      <address>
        <postal>
          <street>470 Conrad Dr</street>

          <city>Mars</city>

          <region>PA</region>

          <code>16046</code>

          <country>US</country>
        </postal>

        <email>br@brianrosen.net</email>
      </address>
    </author>

    <date day="3" month="July" year="2009" />

    <area>app</area>

<abstract>
<t>RFC4119 updated by RFC5139 defines suffixes for street names and house numbers, but does not define prefixes.  Both occur regularly
in addresses and CAtypes are needed for them.  This memo defines STP Street Prefix and HNP house number prefix CAtypes.</t>
</abstract></front><middle>
<section 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"></xref>.</t>
<section title="Prefixes in addressing">	
<t>In <xref target="RFC4119"/> one can define a PIDF for 123 Main Street but not 123 Boulevard Coranado.  There is an STS CAtype for a
suffix, but no corresponding prefix.  <xref target="RFC5139"/> added PRM Premodifier and POM
Postmodifier, but those are not suitable for the purpose.</t>
<t>Similarly, one can express 123B Main, but not H123 Main.  Although one can include such letters
in the house number, most addressing authorities keep the number numeric only to facilitate sorting, and have prefix and suffix fields
for alphanumerics that appear in front of or following the numeric house number.</t>
<t>To remedy this situation, new CAtypes are required: STP for a street (road) prefix, and HNP for a house number prefix.</t>
</section>
<section title="Security Considerations">
<t>The XML representation described in this document is designed for
   inclusion in a PIDF-LO document.  As such, it is subject to the same
   security considerations as are described in <xref target="RFC4119"/>.
   Considerations relating to the inclusion of this representation in
   other XML documents are outside the scope of this document.</t>
</section>
<section title="IANA Considerations">
<t>   This document updates the civic address type registry established by
   <xref target="RFC4776"/>.  Two additional value are added:</t>
<figure><artwork>
    41      STP    Street (Road) Prefix
    42      HNP    House Number Prefix
</artwork></figure>
</section></section>
  </middle>

  <back>
     <references title="Normative References">
      &rfc2119;
      &rfc4119;
    </references>
   <references title="Informative References">
      &rfc4776;
      &rfc5139;
    </references>
  </back>
</rfc>