02600
G1V 2M2
See [TBD: This document].
Rosen, et al. Expires November 06, 2013 [Page 51] Internet-Draft Additional Call Data May 2013 END 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 Rosen, et al. Expires November 06, 2013 [Page 52] Internet-Draft Additional Call Data May 2013 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 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 Rosen, et al. Expires November 06, 2013 [Page 54] Internet-Draft Additional Call Data May 2013 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 1. URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo Rosen, et al. Expires November 06, 2013 [Page 55] Internet-Draft Additional Call Data May 2013 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 5. 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). 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-90 00 15. Acknowledgments Rosen, et al. Expires November 06, 2013 [Page 56] Internet-Draft Additional Call Data May 2013 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. [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] Rosen, et al. Expires November 06, 2013 [Page 57] Internet-Draft Additional Call Data May 2013 Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., Morris, J., Hansen, M., and R. Smith, "Privacy Considerations for Internet Protocols", draft-iab-privacy- considerations-03 (work in progress), July 2012. [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for Emergency Context Resolution with Internet Technologies", RFC 5012, January 2008. [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. Tschofenig, "LoST: A Location-to-Service Translation Protocol", RFC 5222, August 2008. [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 5985, September 2010. [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, "Framework for Emergency Calling Using Internet Multimedia", RFC 6443, December 2011. [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for Communications Services in Support of Emergency Calling", BCP 181, RFC 6881, March 2013. Appendix A. XML Schema for vCard/xCard This section contains the vCard/xCard XML schema version of the Relax NG schema defined in RFC 6351 [RFC6351] for simplified use with the XML schemas defined in this document. The schema in RFC 6351 [RFC6351] is the normative source and this section is informative only.