<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
     which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [

<!ENTITY RFC2119  	PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
<!ENTITY RFC4776	PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4776.xml'>
<!ENTITY RFC4119	PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4119.xml'>
<!ENTITY RFC5139	PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5139.xml'>
<!ENTITY RFC3693	PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3693.xml'>

]>
	<rfc category="info" ipr="trust200902" docName="draft-george-ecrit-lamp-post-02">

  	<?rfc toc="yes" ?>

  	<?rfc symrefs="yes" ?>

 	<?rfc sortrefs="yes"?>

  	<?rfc iprnotified="no" ?>

  	<?rfc strict="yes" ?>

	<?rfc compact="yes" ?>

<front>
  <title abbrev="Civic Location Format Extension">
  Civic Location Format Extension for Utility and Lamp Post Numbers
  </title>
  
  <author initials="R." surname="George" fullname="Robins George">
     <organization abbrev="Huawei Technologies">Huawei Technologies </organization>
     <address>
       <postal>
 	  <street> Huawei Base, Bantian, Longgang District </street>
 	  <city> Shenzhen </city> 
 	  <region> Guangdong </region>
 	  <code> 518129 </code> 
 	  <country> P. R. China</country> 
       </postal>
       <phone> +86-755-28788314 </phone>
       <email> robinsg@huawei.com </email>
     </address>
   </author>
   
     <author initials="Q." surname="Sun" fullname="Qian Sun">
       <organization abbrev="Huawei Technologies">Huawei Technologies </organization>
       <address>
         <postal>
   	  <street> Huawei Base, Bantian, Longgang District </street>
   	  <city> Shenzhen </city> 
   	  <region> Guangdong </region>
   	  <code> 518129 </code> 
   	  <country> P. R. China</country> 
         </postal>
         <phone> +86-755-28787351 </phone>
         <email> sunqian@huawei.com </email>
       </address>
   </author>  
 
     <author initials="H." surname="Schulzrinne" fullname="Henning Schulzrinne">
       <organization abbrev="Columbia University">Columbia University </organization>
       <address>
         <postal>
   	  <street> Department of Computer Science </street>
   	  <city> 450 Computer Science Building </city> 
   	  <region> New York </region>
   	  <code> NY, 10027 </code> 
   	  <country> US </country> 
         </postal>
         <phone> +1 212 939 7004 </phone>
         <email> hgs@cs.columbia.edu </email>
         <uri> http://www.cs.columbia.edu </uri>
       </address>
   </author>
      <author fullname="Brian Rosen" initials="B." 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 year="2010"/>

  <area>RAI</area>
  <workgroup>ECRIT</workgroup>

<abstract>

	<t>	
	
	This document describes an extension to civic location format
	and adds two new CAtypes: PN (pole number) and MP (milepost). Pole Numbers are used on poles such as lamp posts or utility poles, and can be used in some circumstances as location information.   Mileposts are numeric values measured from an end of a trail, road, railway line or other feature.  
	</t>
	
</abstract>
</front>


<middle>

<section anchor="intro" title="Introduction">

	<t>
	
	In some areas, utility and lamp posts carry 
	a unique identifier, which we call a pole number in this document. 
	In some countries, the label on the lamp post also carries 
	the local emergency service number, such as "110", encouraging 
	callers to use the pole number to identify their location.	
	</t>
	<figure>
	<artwork>
		       _.-----,===.
		      | |    (''''')
		      | |     `---'
		      | |
		      | |               ,---------,
		      | |    ,---,      |Emergency|
		      | |   /|,-.|----->| Number  |
		      | |  / |110|      '---------'
		      | | /  |`-'|
		      |_|/   | 2 |      ,---------,
		      | |    | 1 |      |Lamp Post|
		      | |    | 2 |----->| Number  |
		      |-|    | 1 |      '---------'
		      | |\   | 0 |
		      | | \  | 1 |
		      | |  \ | 4 |
		      | |   \|,,,|
		_     | |
		 ``-..|.|
			``--.._
			       `'--.._


             Lamp post with emergency number.                 
         </artwork>
         </figure>

	<t>On some roads, and many trails, railroad rights of way and other linear features, a post with a mile or kilometer distance from one end of the feature may be found (a "milepost").  There are other cases of poles or markers with numeric indications that are not the same as a "house number" or street address number.
	</t>
	
	<t>
	
	In this document, we define an extension of the civic address format 
	defined in <xref target="RFC4119"/> updated by <xref target="RFC5139"/> to carry such pole number and milepost information.
       </t>
         
         
	 
         


</section>

<section anchor="terms" title="Terminology Used in This Document">

	<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="PN" title="Pole Number and Milepost">

	<t>
	
	<xref target='RFC4776'/> and  <xref target='RFC5139'/> 
	provides a full set of parameters that may be used to
	describe a civic location.
        
        </t>
        
        <t>
        
        This document describes two new CAtypes, PN (pole number), which is used to support post numbers, and MP (milepost), which is used to support mileposts. The pole number can consist of any combination of 
	letters and digits. Punctuation characters and embedded spaces are ignored; 
	lower and upper case letters are treated as equivalent.  Mileposts are traditionally mile or kilometer distances from one end of the feature, but the field may contain any combination of letters, digits and punctuation characters.  There could be country specific considerations for PN or MP use, but none are described in this document.
	
	</t>


	<figure>
	<artwork>     
	
+---------+--------+-------------------------------+--------------+
| CAtype  | PIDF   | Description                   | Example      |
+---------+--------+-------------------------------+--------------+
| 43      |   PN   | lamp post number              | A12101S      |
+---------+--------+-------------------------------+--------------+	
| 44      |   MP   | Milepost                      | 102.4        |
+---------+--------+-------------------------------+--------------+	
		 
		 Table 1: New Civic PIDF-LO Types

	</artwork>
        </figure>
	



</section>

<section anchor="Examples" title="Examples">

	<t>
	<figure>
	<artwork>  
	<![CDATA[
	   <civicAddress xml:lang="en-AU"
	     xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
	     <country>CN</country>
	     <A1>GD</A1>
	     <A3>Shenzhen</A3>
	     <A4>Bantian</A4>
	     <RD>Wuhe</RD>
	     <LMK>Bai Cao Yuan</LMK> 
	     <LOC>Front Gate</LOC>
	     <NAM>Video Rental Store</NAM>
	     <PC>518129</PC>
	     <PN>2121014</PN>     
	   </civicAddress>


	   <civicAddress xml:lang="en-AU"
	     xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
	     <country>US</country>
	     <A1>PA</A1>
	     <A3>Hopewell</A3>
	     <RD>Baker Trail</RD>
             <MP>11.4</MP>
	   </civicAddress>
	]]>
	</artwork>
        </figure>

 	</t>
	

</section>



<section anchor="security" title="Security Considerations">
	
	<t>
	
	The security considerations of [RFC4119] is relevant
   	to this document.  No new security considerations arise as a result of these new fields

	</t>
	
	
	
</section>


<section anchor="iana" title="IANA Considerations">

	<section anchor="CATYPE" title="CAtype Registry Update">
 
		<t>

		This document updates the CAtype registry established by [RFC4776]. 
                Two entries are defined, with values as indicated in Table 1.

		</t>

</section>
</section>


</middle>


<back>

	<references title="Normative References">

		&RFC2119;

	</references>
	
	<references title="Informative References">

		&RFC4776;
		&RFC4119;
		&RFC5139;
		&RFC3693;

		
		
        	
	</references>	


</back>
</rfc>
