< draft-linsner-geopriv-adminspecific-00.txt   draft-linsner-geopriv-adminspecific-01.txt >
GeoPriv M. Linsner GeoPriv M. Linsner
Internet Draft Cisco Systems Internet Draft Cisco Systems
Intended status: Standards Track S. Dhesikan Intended status: Standards Track S. Dhesikan
Expires: January 12, 2008 Cisco Systems Expires: January 2009 Cisco Systems
July 11, 2007 H. Tschofenig
Nokia Siemens Networks
July 14, 2008
Administrative Specific Elements for Civic Location Format Administrative Specific Elements for Civic Location Format
draft-linsner-geopriv-adminspecific-00.txt draft-linsner-geopriv-adminspecific-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 35 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on January 12, 2008. This Internet-Draft will expire on January 15, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines additional civic address parameters for use in This document defines additional civic address parameters for use in
Location Objects [1] and [4]. The format is based on the civic Location Objects [1], [2], and [4]. The format is based on the civic
address definition of PIDF-LO. These addition parameters allow address definition of PIDF-LO. These addition parameters allow
expression of administrative specific location data elements. expression of administrative specific location data elements.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [1]. document are to be interpreted as described in RFC-2119 [1].
Table of Contents Table of Contents
skipping to change at page 2, line 26 skipping to change at page 2, line 28
3. Example Schema.................................................6 3. Example Schema.................................................6
4. Security Considerations........................................7 4. Security Considerations........................................7
5. IANA Considerations............................................7 5. IANA Considerations............................................7
5.1. XML Schema Registration...................................7 5.1. XML Schema Registration...................................7
5.2. CAType Registry Update....................................7 5.2. CAType Registry Update....................................7
6. Acknowledgments................................................7 6. Acknowledgments................................................7
7. References.....................................................8 7. References.....................................................8
7.1. Normative References......................................8 7.1. Normative References......................................8
7.2. Informative References....................................8 7.2. Informative References....................................8
Author's Addresses................................................8 Author's Addresses................................................8
Intellectual Property Statement...................................8 Intellectual Property Statement...................................9
Disclaimer of Validity............................................9 Disclaimer of Validity............................................9
1. Introduction 1. Introduction
In large enterprise/campus networks, information about a host's In large enterprise/campus networks, information about a host's
network/campus location is often useful for internal application network/campus location is often useful for internal application
configuration and maintenance of both applications and network configuration and maintenance of both applications and network
infrastructure. Typically, this is information that is not useful infrastructure. Typically, this is information that is not useful
outside of the campus or enterprise. Currently, this information is outside of the campus or enterprise. Currently, this information is
collected via additional data collection mechanisms such as SNMP or collected via additional data collection mechanisms such as SNMP or
skipping to change at page 6, line 7 skipping to change at page 6, line 7
A location that includes administrative specific information for zone A location that includes administrative specific information for zone
6. 6.
<ADMIN>cisco</ADMIN> <ADMIN>cisco</ADMIN>
<AS-2>zone6</AS-2> <AS-2>zone6</AS-2>
3. Example Schema 3. Example Schema
<xs:schema targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" <xs:schema
targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd" /> schemaLocation="http://www.w3.org/2001/xml.xsd" />
<xs:element name="civicAddress" type="ca:civicAddress" /> <xs:element name="civicAddress" type="ca:civicAddress" />
<xs:complexType name="caType"> <xs:complexType name="caType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="xs:token"> <xs:extension base="xs:token">
<xs:attribute ref="xml:lang" use="optional" /> <xs:attribute ref="xml:lang" use="optional" />
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
<xs:complexType name="civicAddress"> <xs:complexType name="civicAddress">
<xs:sequence> <xs:sequence>
<!-- additions to civicAddress --> <!-- additions to civicAddress -->
<xs:element name="admin" type="ca:caType" minOccurs="0" /> <xs:element name="admin" type="ca:caType" minOccurs="0" />
<xs:element name="as-1" type="ca:caType" minOccurs="0" /> <xs:element name="as-1" type="ca:caType" minOccurs="0" />
<xs:element name="as-2" type="ca:caType" minOccurs="0" /> <xs:element name="as-2" type="ca:caType" minOccurs="0" />
<xs:element name="as-3" type="ca:caType" minOccurs="0" /> <xs:element name="as-3" type="ca:caType" minOccurs="0" />
<xs:element name="as-4" type="ca:caType" minOccurs="0" /> <xs:element name="as-4" type="ca:caType" minOccurs="0" />
<xs:element name="as-5" type="ca:caType" minOccurs="0" /> <xs:element name="as-5" type="ca:caType" minOccurs="0" />
<xs:element name="as-6" type="ca:caType" minOccurs="0" /> <xs:element name="as-6" type="ca:caType" minOccurs="0" />
<xs:element name="as-7" type="ca:caType" minOccurs="0" /> <xs:element name="as-7" type="ca:caType" minOccurs="0" />
<xs:element name="as-8" type="ca:caType" minOccurs="0" /> <xs:element name="as-8" type="ca:caType" minOccurs="0" />
<xs:element name="as-9" type="ca:caType" minOccurs="0" /> <xs:element name="as-9" type="ca:caType" minOccurs="0" />
<xs:element name="as-10" type="ca:caType" minOccurs="0" /> <xs:element name="as-10" type="ca:caType" minOccurs="0" />
<xs:element name="as-11" type="ca:caType" minOccurs="0" /> <xs:element name="as-11" type="ca:caType" minOccurs="0" />
<xs:element name="as-12" type="ca:caType" minOccurs="0" /> <xs:element name="as-12" type="ca:caType" minOccurs="0" />
<xs:element name="as-13" type="ca:caType" minOccurs="0" /> <xs:element name="as-13" type="ca:caType" minOccurs="0"
<xs:element name="as-14" type="ca:caType" minOccurs="0" /> />
<xs:element name="as-15" type="ca:caType" minOccurs="0" /> <xs:element name="as-14" type="ca:caType" minOccurs="0" />
<xs:element name="as-16" type="ca:caType" minOccurs="0" /> <xs:element name="as-15" type="ca:caType" minOccurs="0" />
<xs:element name="as-17" type="ca:caType" minOccurs="0" /> <xs:element name="as-16" type="ca:caType" minOccurs="0" />
<xs:element name="as-18" type="ca:caType" minOccurs="0" /> <xs:element name="as-17" type="ca:caType" minOccurs="0"
<xs:element name="as-19" type="ca:caType" minOccurs="0" /> />
<xs:element name="as-20" type="ca:caType" minOccurs="0" /> <xs:element name="as-18" type="ca:caType" minOccurs="0" />
<xs:element name="as-21" type="ca:caType" minOccurs="0" /> <xs:element name="as-19" type="ca:caType" minOccurs="0" />
<xs:element name="as-22" type="ca:caType" minOccurs="0" /> <xs:element name="as-20" type="ca:caType" minOccurs="0" />
<xs:element name="as-23" type="ca:caType" minOccurs="0" /> <xs:element name="as-21" type="ca:caType" minOccurs="0"
<xs:element name="as-24" type="ca:caType" minOccurs="0" /> />
<xs:element name="as-25" type="ca:caType" minOccurs="0" /> <xs:element name="as-22" type="ca:caType" minOccurs="0" />
</xs:sequence> <xs:element name="as-23" type="ca:caType" minOccurs="0" />
</xs:complexType> <xs:element name="as-24" type="ca:caType" minOccurs="0" />
</xs:schema> <xs:element name="as-25" type="ca:caType" minOccurs="0"
/>
</xs:sequence>
</xs:complexType>
</xs:schema>
4. Security Considerations 4. Security Considerations
The XML parameters defined in the document are additions to the The XML parameters defined in the document are additions to the
current PIDF-LO specification. Therefore the parameters defined here current PIDF-LO specification. Therefore the parameters defined here
are subject to the same security considerations of [1]. are subject to the same security considerations of [1].
5. IANA Considerations 5. IANA Considerations
5.1. XML Schema Registration 5.1. XML Schema Registration
skipping to change at page 8, line 13 skipping to change at page 8, line 13
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
7. References 7. References
7.1. Normative References 7.1. Normative References
[1] Petersen, J., "A Presence-based GEOPRIV Location Object [1] Petersen, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005. Format", RFC 4119, December 2005.
[2] Thomson, M. & Winterbottom, J., "Revised Civic Location Format [2] Thomson, M. & Winterbottom, J., "Revised Civic Location Format
for PIDF-LO", draft-ietf-geopriv-revised-civic-lo-05.txt, for Presence Identifier Format Location Object (PIDF-LO)", RFC
February 2007. 5139, February 2008.
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[4] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4 [4] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4
and DHCPv6) Option for Civic Addresses Configuration and DHCPv6) Option for Civic Addresses Configuration
Information", RFC4776, November 2006 Information", RFC4776, November 2006
7.2. Informative References 7.2. Informative References
skipping to change at page 8, line 39 skipping to change at page 8, line 39
Marco Island, Florida, USA Marco Island, Florida, USA
Email: mlinsner@cisco.com Email: mlinsner@cisco.com
Subha Dhesikan Subha Dhesikan
Cisco Systems, Inc. Cisco Systems, Inc.
San Jose, California, USA San Jose, California, USA
Email: sdhesika@cisco.com Email: sdhesika@cisco.com
Hannes Tschofenig
Nokia Siemens Networks
Linnoitustie 6
Espoo 02600
Finland
Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 9, line 30 skipping to change at page 9, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 15 change blocks. 
53 lines changed or deleted 69 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/