See [TBD: This document].
END Rosen, Tschofenig, MarshExpireseAugust 20, 2013 [Page 39] Internet-Draft Additional Call Data February 2013 14.5.2. Registration for urn:ietf:params:xml:ns:emergencyCallProviderInfo This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:emergencyCallProviderInfo Registrant Contact: IETF, ECRIT working group,See [TBD: This document].
END 14.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:emergencyCall.SvcInfo Registrant Contact: IETF, ECRIT working group,See [TBD: This document].
END 14.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:emergencyCall.DevInfo Registrant Contact: IETF, ECRIT working group,See [TBD: This document].
END Rosen, Tschofenig, MarshExpireseAugust 20, 2013 [Page 41] Internet-Draft Additional Call Data February 2013 14.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:emergencyCall.SubInfo Registrant Contact: IETF, ECRIT working group,See [TBD: This document].
END 14.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:emergencyCall.Comment Registrant Contact: IETF, ECRIT working group,See [TBD: This document].
END 14.6. Schema Registrations This specification registers five schemas, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:schema:additional- data:emergencyCallProviderInfo Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as delegated by the IESG (iesg@ietf.org). XML: The XML schema can be found in Figure 2. URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as delegated by the IESG (iesg@ietf.org). XML: The XML schema can be found in Figure 3. URI: urn:ietf:params:xml:schema:additional- data:emergencyCallDevInfo Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as delegated by the IESG (iesg@ietf.org). XML: The XML schema can be found in Figure 4. URI: urn:ietf:params:xml:schema:additional- data:emergencyCall.SubInfo Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as delegated by the IESG (iesg@ietf.org). Rosen, Tschofenig, MarshExpireseAugust 20, 2013 [Page 43] Internet-Draft Additional Call Data February 2013 XML: The XML schema can be found in Section 8.2. URI: urn:ietf:params:xml:schema:additional- data:emergencyCall.Comment Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as delegated by the IESG (iesg@ietf.org). XML: The XML schema can be found in Section 9.2. 14.7. VCard Parameter Value Registration This document registers a new value in the vCARD Parameter Values registry as defined by [RFC6350] with the following template: Value: main Purpose: The main telephone number, typically of an enterprise, as opposed to a direct dial number of an individual employee Conformance: This value can be used with the "TYPE" parameter applied on the "TEL" property. Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-900 0 15. Acknowledgments This work was originally started in NENA and has benefitted from a large number of participants in NENA standardization efforts, originally in the Long Term Definition Working Group, the Data Technical Committee and most recently the Additional Data working group. The authors are grateful for the initial work and extended comments provided by the many NENA participants. 16. References 16.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource Locators", RFC 2392, August 1998. [RFC3023] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC 3023, January 2001. [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002. Rosen, Tschofenig, MarshExpireseAugust 20, 2013 [Page 44] Internet-Draft Additional Call Data February 2013 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object Format", RFC 4119, December 2005. [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", RFC 4288, December 2005. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, August 2011. [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 6351, August 2011. 16.2. Informational References [I-D.iab-privacy-considerations] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., Morris, J., Hansen, M. and R. Smith, "Privacy Considerations for Internet Protocols", Internet-Draft draft-iab-privacy-considerations-03, July 2012. [I-D.ietf-ecrit-phonebcp] Rosen, B. and J. Polk, "Best Current Practice for Communications Services in support of Emergency Calling", Internet-Draft draft-ietf-ecrit-phonebcp-20, September 2011. [RFC5222] Hardie, T., Newton, A., Schulzrinne, H. and H. Tschofenig, "LoST: A Location-to-Service Translation Protocol", RFC 5222, August 2008. [RFC6443] Rosen, B., Schulzrinne, H., Polk, J. and A. Newton, "Framework for Emergency Calling Using Internet Multimedia", RFC 6443, December 2011. Authors' Addresses Brian Rosen NeuStar 470 Conrad Dr. Mars, PA 16046 US Phone: +1 724 382 1051 Email: br@brianrosen.net Rosen, Tschofenig, MarshExpireseAugust 20, 2013 [Page 45] Internet-Draft Additional Call Data February 2013 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 Roger Marshall TeleCommunication Systems, Inc. 2401 Elliott Avenue Seattle, WA 98121 US Phone: +1 206 792 2424 Email: rmarshall@telecomsys.com URI: http://www.telecomsys.com Randall Gellens Qualcomm Technologies, Inc. 5775 Morehouse Drive San Diego, CA 92121 US Email: rg+ietf@qti.qualcomm.com Rosen, Tschofenig, MarshExpireseAugust 20, 2013 [Page 46]