Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-24
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7852.
|
|
|---|---|---|---|
| Authors | Randall Gellens , Brian Rosen , Hannes Tschofenig , Roger Marshall , James Winterbottom | ||
| Last updated | 2014-10-13 | ||
| Replaces | draft-rosen-ecrit-additional-data | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
GENART Telechat review
(of
-34)
by Francis Dupont
Almost ready
GENART Last Call review
(of
-33)
by Francis Dupont
Almost ready
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Became RFC 7852 (Proposed Standard) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-ietf-ecrit-additional-data-24
Internet-Draft Additional Call Data October 2014 </provided-by> </gp:geopriv> <dm:deviceID>mac:00-0d-4b-30-72-df</dm:deviceID> <dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp> </dm:device> </presence> Figure 14: Access Network Provider returning PIDF-LO with Additional Data. 7. XML Schemas This section defines the XML schemas of the five data blocks. Additionally, the Provided-By schema is specified. 7.1. EmergencyCallData.ProviderInfo XML Schema <?xml version="1.0"?> <xs:schema targetNamespace= "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"> <xs:simpleType name="iso3166a2"> <xs:restriction base="xs:token"> <xs:pattern value="[A-Z]{2}"/> </xs:restriction> </xs:simpleType> <xs:element name="EmergencyCallData.ProviderInfo" type="pi:ProviderInfoType"/> <xs:element name="DataProviderReference" type="xs:token" minOccurs="1" maxOccurs="1"/> Gellens, et al. Expires April 16, 2015 [Page 47] Internet-Draft Additional Call Data October 2014 <xs:simpleType name="SubcontractorPriorityType"> <xs:restriction base="xs:string"> <xs:enumeration value="sub"/> <xs:enumeration value="main"/> </xs:restriction> </xs:simpleType> <xs:complexType name="ProviderInfoType"> <xs:sequence> <xs:element name="id" type="xs:string" minOccurs="1" maxOccurs="1"/> <xs:element name="DataProviderString" type="xs:string" minOccurs="1" maxOccurs="1"/> <xs:element name="ProviderID" type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:element name="ProviderIDSeries" type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:element name="TypeOfProvider" type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:element name="ContactURI" type="xs:anyURI" minOccurs="1" maxOccurs="1"/> <xs:element name="Language" type="pi:iso3166a2" minOccurs="1" maxOccurs="unbounded" /> <xs:element name="DataProviderContact" type="xc:vcardType" minOccurs="0" maxOccurs="1"/> <xs:element name="SubcontratorPrincipal" type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:element name="SubcontractorPriority" type="pi:SubcontractorPriorityType" minOccurs="0" maxOccurs="1"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> Gellens, et al. Expires April 16, 2015 [Page 48] Internet-Draft Additional Call Data October 2014 Figure 15: EmergencyCallData.ProviderInfo XML Schema. 7.2. EmergencyCallData.ServiceInfo XML Schema <?xml version="1.0"?> <xs:schema targetNamespace= "urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo" xmlns:xml="http://www.w3.org/XML/1998/namespace" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:element name="EmergencyCallData.ServiceInfo" type="svc:ServiceInfoType"/> <xs:complexType name="ServiceInfoType"> <xs:sequence> <xs:element name="DataProviderReference" type="xs:token" minOccurs="1" maxOccurs="1"/> <xs:element name="ServiceEnvironment" type="xs:string" minOccurs="1" maxOccurs="1"/> <xs:element name="ServiceType" type="xs:string" minOccurs="1" maxOccurs="unbounded"/> <xs:element name="ServiceMobility" type="xs:string" minOccurs="1" maxOccurs="1"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> Figure 16: EmergencyCallData.ServiceInfo XML Schema. Gellens, et al. Expires April 16, 2015 [Page 49] Internet-Draft Additional Call Data October 2014 7.3. EmergencyCallData.DeviceInfo XML Schema <?xml version="1.0"?> <xs:schema targetNamespace= "urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:xml="http://www.w3.org/XML/1998/namespace" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:element name="EmergencyCallData.DeviceInfo" type="dev:DeviceInfoType"/> <xs:complexType name="DeviceInfoType"> <xs:sequence> <xs:element name="DataProviderReference" type="xs:token" minOccurs="1" maxOccurs="1"/> <xs:element name="DeviceClassification" type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:element name="DeviceMfgr" type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:element name="DeviceModelNr" type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:element name="UniqueDeviceID" minOccurs="0" maxOccurs="unbounded"> <xs:complexType> <xs:simpleContent> <xs:extension base="xs:string"> <xs:attribute name="TypeOfDeviceID" type="xs:string" use="required"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="DeviceSpecificData" type="xs:anyURI" minOccurs="0" maxOccurs="1"/> Gellens, et al. Expires April 16, 2015 [Page 50] Internet-Draft Additional Call Data October 2014 <xs:element name="DeviceSpecificType" type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> Figure 17: EmergencyCallData.DeviceInfo XML Schema. 7.4. EmergencyCallData.SubscriberInfo XML Schema Gellens, et al. Expires April 16, 2015 [Page 51] Internet-Draft Additional Call Data October 2014 <?xml version="1.0"?> <xs:schema targetNamespace= "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sub= "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xml="http://www.w3.org/XML/1998/namespace" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"/> <xs:element name="EmergencyCallData.SubscriberInfo" type="sub:SubscriberInfoType"/> <xs:complexType name="SubscriberInfoType"> <xs:complexContent> <xs:sequence> <xs:element name="DataProviderReference" type="xs:token" minOccurs="1" maxOccurs="1"/> <xs:element name="SubscriberData" type="xc:vcardType" minOccurs="0" maxOccurs="1" /> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="privacyRequested" type="xs:boolean" use="required"/> </xs:complexContent> </xs:complexType> </xs:schema> Figure 18: EmergencyCallData.SubscriberInfo XML Schema. 7.5. EmergencyCallData.Comment XML Schema Gellens, et al. Expires April 16, 2015 [Page 52] Internet-Draft Additional Call Data October 2014 <?xml version="1.0"?> <xs:schema targetNamespace= "urn:ietf:params:xml:ns:EmergencyCallData:Comment" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment" xmlns:xml="http://www.w3.org/XML/1998/namespace" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:element name="EmergencyCallData.Comment" type="com:CommentType"/> <xs:complexType name="CommentType"> <xs:sequence> <xs:element name="DataProviderReference" type="xs:token" minOccurs="1" maxOccurs="1"/> <xs:element name="Comment" type="com:CommentSubType" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="CommentSubType"> <xs:simpleContent> <xs:extension base="xs:string"> <xs:attribute ref="xml:lang"/> </xs:extension> </xs:simpleContent> </xs:complexType> </xs:schema> Figure 19: EmergencyCallData.Comment XML Schema. 7.6. Provided-By XML Schema This section defines the Provided-By schema. <?xml version="1.0"?> Gellens, et al. Expires April 16, 2015 [Page 53] Internet-Draft Additional Call Data October 2014 <xs:schema targetNamespace= "urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData" xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:sub= "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace= "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"/> <xs:import namespace= "urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"/> <xs:import namespace= "urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"/> <xs:import namespace= "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"/> <xs:import namespace= "urn:ietf:params:xml:ns:EmergencyCallData:Comment"/> <xs:element name="provided-by" type="ad:provided-by-Type"/> <xs:complexType name="provided-by-Type"> <xs:sequence> <xs:element name="DataProviderReference" type="xs:token" minOccurs="1" maxOccurs="1"/> <xs:element name="EmergencyCallDataReference" type="ad:ByRefType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="EmergencyCallDataValue" type="ad:EmergencyCallDataValueType" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> Gellens, et al. Expires April 16, 2015 [Page 54] Internet-Draft Additional Call Data October 2014 <!-- Additional Data By Reference --> <xs:complexType name="ByRefType"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:sequence> <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded" processContents="lax"/> </xs:sequence> <xs:attribute name="purpose" type="xs:token" use="required"/> <xs:attribute name="ref" type="xs:anyURI" use="required"/> </xs:restriction> </xs:complexContent> </xs:complexType> <!-- Additional Data By Value --> <xs:complexType name="EmergencyCallDataValueType"> <xs:sequence> <xs:element name="EmergencyCallData.ProviderInfo" type="pi:ProviderInfoType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="EmergencyCallData.ServiceInfo" type="svc:ServiceInfoType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="EmergencyCallData.DeviceInfo" type="dev:DeviceInfoType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="EmergencyCallData.SubscriberInfo" type="sub:SubscriberInfoType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="EmergencyCallData.Comment" type="com:CommentType" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:schema> Figure 20: Provided-By XML Schema. Gellens, et al. Expires April 16, 2015 [Page 55] Internet-Draft Additional Call Data October 2014 8. Security Considerations The data structures described in this document contain information usually considered private. When information is provided by value, entities that are a party to the SIP signaling (such as proxy servers and back-to-back user agents) will have access to it and need to protect it against inappropriate disclosure. An entity that is able to eavesdrop on the SIP signaling will also have access. Some media (such as in the clear Wi-Fi) is more vulnerable than others (such as 3G or 4G cellular data traffic) to eavesdropping. Mechanisms that protect against eavesdropping (such as Transport Layer Security (TLS)) SHOULD be preferentially used whenever feasible. When information is provided by reference, HTTPS is specified for dereferencing, and the provider of the information is REQUIRED to validate the credentials of the requester. While the creation of a public key infrastructure (PKI) that has global scope may be difficult, the alternatives to creating devices and services that can provide critical information securely are more daunting. The provider of the information MAY enforce any policy it wishes to use, but PSAPs and responder agencies SHOULD deploy a PKI so that providers of additional data can check the certificate of the client and decide the appropriate policy to enforce based on that certificate. Ideally, the PSAP and emergency responders will be given credentials signed by an authority trusted by the data provider. In most circumstances, nationally recognized credentials would be sufficient, and if the emergency services arranges a PKI, data providers could be provisioned with the root CA public key for a given nation. Some nations are developing a PKI for this, and related, purposes. Since calls could be made from devices where the device and/or the service provider(s) are not local to the emergency services authorities, globally recognized credentials are useful. This might be accomplished by extending the notion of the "forest guide" described in [RFC5582] to allow the forest guide to provide the credential of the PKI root for areas for which it has coverage information, but standards for such a mechanism are not yet available. In its absence, the data provider will need to obtain by out of band means the root CA credentials for any areas to which it is willing to provide additional data. With the credential of the root CA for a national emergency services PKI, the data provider server can validate the credentials of an entity requesting additional data by reference. The data provider also needs a credential that can be verified by the emergency services to know that it is receiving data from an authorized server. The emergency services authorities could provide credentials, distinguishable from credentials provided to emergency Gellens, et al. Expires April 16, 2015 [Page 56] Internet-Draft Additional Call Data October 2014 responders and PSAPs, which could be used to validate data providers. Such credentials would have to be acceptable to any PSAP or responder that could receive a call with additional data supplied by that provider. This would be extensible to global credential validation using the forest guide as mentioned above. In the absence of such credentials, the emergency services authorities could maintain a list of local data providers' credentials as provided to them out of band. At a minimum, the emergency services authorities could obtain a credential from the DNS entry of the domain in the Additional Data URI to at least validate that the server is known to the domain providing the URI. Data provided by devices by reference have similar credential validation issues as for service providers, and the solutions are the same. Much of the information supplied by service providers and devices is private and confidential; service providers and devices generally go to lengths to protect this information; disclosing it in the context of an emergency call is a trade-off to protect the greater interest of the customer in an emergency. Neither service providers nor devices will supply private information unless the call is recognized as an emergency call. In cellular telephony systems (such as those using 3GPP IMS), there are different procedures for an originating device to place an emergency versus a normal call. If a call that is really an emergency call is initiated as a normal call and the cellular service provider recognizes this, 3GPP IMS permits the service provider to either accept the call anyway or reject it with a specific code that instructs the device to retry the call as an emergency call. Service providers SHOULD choose the latter, because otherwise the device will not have included the information specified in this document (since the device didn't recognize the call as being an emergency call). 9. Privacy Considerations This document enables functionality for conveying additional information about the caller and the caller's device and service to the callee. Some of this information is personal data and therefore privacy concerns arise. An explicit privacy indicator for information directly relating to the caller's identity is defined and use is mandatory. However, observance of this request for privacy and what information it relates to is determined by the destination jurisdiction. There are a number of privacy concerns with non-emergency real-time communication services that are also applicable to emergency calling. Gellens, et al. Expires April 16, 2015 [Page 57] Internet-Draft Additional Call Data October 2014 Data protection regulation world-wide has, however, decided to create exceptions for emergency services since the drawbacks of disclosing personal data are outweighed by the benefit for the emergency caller. Hence, the data protection rights of individuals are commonly waived for emergency situations. There are, however, still various countries that offer some degree of anonymity for the caller towards PSAP call takers. The functionality defined in this document, however, far exceeds the amount of information sharing found in the legacy POTS system. For this reason there are additional privacy threats to consider, which are described in more detail in [RFC6973]. Stored Data Compromise: There is an increased risk of stored data compromise since additional data is collected and stored in databases. Without adequate measures to secure stored data from unauthorized or inappropriate access at access network providers, service providers, end devices, as well as PSAPs, individuals are exposed to potential financial, reputational, or physical harm. Misattribution: If the personal data collected and conveyed is incorrect or inaccurate then this may lead to misattribution. Misattribution occurs when data or communications related to one individual are attributed to another. Identification: By the nature of the additional data and its capability to provide much richer information about the caller, the call, and the location, the calling party is identified in a much better way. Some users may feel uncomfortable with this degree of information sharing even in emergency services situations. Secondary Use: There is a risk of secondary use, which is the use of collected information about an individual without the individual's consent for a purpose different from that for which the information was collected. The stated purpose of the additional data is for emergency services purposes but theoretically the same information could be used for any other call as well. Additionally, parties involved in the emergency call may retain the obtained information and may re-use it for other, non- emergency services purposes. Disclosure: When the data defined in this document is not properly protected (while in transit with traditional communication security techniques, and while stored using access control mechanisms) there is the risk of disclosure, which is the revelation of private information about an individual. Gellens, et al. Expires April 16, 2015 [Page 58] Internet-Draft Additional Call Data October 2014 To mitigate these privacy risks the following countermeasures can be taken: In regions where callers can elect to suppress certain personally identifying information, network or PSAP functionality can inspect privacy flags within the SIP headers to determine what information may be passed, stored, or displayed to comply with local policy or law. RFC 3325 [RFC3325] defines the "id" priv-value token. The presence of this privacy type in a Privacy header field indicates that the user would like the network asserted identity to be kept private with respect to SIP entities outside the trust domain with which the user authenticated, including the PSAP. This document defines various data structures that contain privacy- sensitive data. For example, identifiers for the device (e.g., serial number, MAC address) or account/SIM (e.g., IMSI), contact information for the user, location of the caller. Local regulations may govern what data must be provided in emergency calls, but in general, the emergency call system is aided by the information described in this document. There is a tradeoff between the privacy considerations and the utility of the data. For protection, this specification requires all retrieval of data passed by reference to be protected against eavesdropping and alteration via communication security techniques (namely TLS). Furthermore, security safeguards are required to prevent unauthorized access to stored data. Various security incidents over at least the past few decades have shown that data breaches are not uncommon and are often caused by lack of proper access control frameworks, software bugs (such as buffer overflows), or missing input parsing (such as SQL injection attacks). The risks of data breaches is increased with the obligation for emergency services to retain emergency call related data for extended periods (e.g., several years are the norm). Finally, it is also worth highlighting the nature of the SIP communication architecture, which introduces additional complications for privacy. Some forms of data can be sent by value in the SIP signaling or by reference (a URL in the SIP signaling). When data is sent by value, all intermediaries have access to the data. As such, these intermediaries may also introduce additional privacy risk. Therefore, in situations where the conveyed information is privacy- sensitive and intermediaries are involved, transmitting by reference might be appropriate, assuming the source of the data can operate a sufficient dereferencing infrastructure and that proper access control policies are available for distinguishing the different entities dereferencing the reference. Without access control policies any party in possession of the reference is able to resolve the reference and to obtain the data, including intermediaries. Gellens, et al. Expires April 16, 2015 [Page 59] Internet-Draft Additional Call Data October 2014 10. IANA Considerations 10.1. Registry creation This document creates a new registry called 'Emergency Call Additional Data'. The following sub-registries are created for this registry. 10.1.1. Provider ID Series Registry This document creates a new sub-registry called 'Additional Call Data Provider ID Series'. As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should determine that the entity requesting a new value is a legitimate issuer of service provider IDs suitable for use in Additional Call Data. Private entities issuing and using internally-generated IDs are encouraged to register and use a unique identifier. This guarantees that IDs issued and used by the entity are globally unique and distinguishable. The content of this registry includes: Name: The identifier which will be used in the 'ProviderIDSeries' element. Source: The full name of the organization issuing the identifiers. URL: A URL to the organization for further information. The initial set of values is listed in Figure 21. +-----------+--------------------------+----------------------+ | Name | Source | URL | +-----------+--------------------------+----------------------+ | NENA | National Emergency | http://www.nena.org | | | Number Association | | | EENA | European Emergency | http://www.eena.org | | | Number Association | | | domain | (The ID is a fully- | (not applicable) | | | qualified domain name) | | +-----------+--------------------------+----------------------+ Figure 21: Provider ID Series Registry. Gellens, et al. Expires April 16, 2015 [Page 60] Internet-Draft Additional Call Data October 2014 10.1.2. Service Environment Registry This document creates a new sub-registry called 'Additional Call Service Environment'. As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should determine that the entity requesting a new value is relevant for this service element, and that the new value is distinct from existing values, and its use is unambiguous. The content of this registry includes: Token: The value to be used in the <ServiceEnvironment> element. Description: A short description of the value. The initial set of values is listed in Figure 22. +-----------+--------------------------+ | Token | Description | +-----------+--------------------------+ | Business | Business service | | Residence | Residential service | | unknown | Type of service unknown | | | (e.g., anonymous pre- | | | paid service) | +-----------+--------------------------+ Figure 22: Service Environment Registry. 10.1.3. Service Type Registry This document creates a new sub-registry called 'Additional Call Service Type'. As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should determine that the entity requesting a new value is relevant for this service element and that the requested value is clearly distinct from other values so that there is no ambiguity as to when the value is to be used or which value is to be used. The content of this registry includes: Name: The value to be used in the <ServiceType> element. Description: A short description of the value. The initial set of values is listed in Figure 3. Gellens, et al. Expires April 16, 2015 [Page 61] Internet-Draft Additional Call Data October 2014 10.1.4. Service Mobility Registry This document creates a new sub-registry called 'Additional Call Service Mobility'. As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should determine that the entity requesting a new value is relevant for this service element and that the requested value is clearly distinct from other values so that there is no ambiguity as to when the value is to be used or which value is to be used. The content of this registry includes: Token: The value used in the <ServiceMobility> element. Description: A short description of the value. The initial set of values is listed in Figure 23. +-----------+----------------------------+ | Token | Description | +-----------+----------------------------+ | Mobile | The device is able to | | | move at any time | | Fixed | The device is not expected | | | to move unless the service | | | is relocated | | Nomadic | The device is not expected | | | to change its point of | | | attachment while on a call | | Unknown | No information is known | | | about the service mobility | | | environment for the device | +-----------+----------------------------+ Figure 23: Service Environment Registry. 10.1.5. Service Provider Type Registry This document creates a new sub-registry called 'Service Provider Type'. As defined in [RFC5226], this registry operates under "Expert Review". The expert should determine that the proposed new value is distinct from existing values and appropriate for use in the TypeOfServicerProvider element The content of this registry includes: Tokenproviderid: The value used in the 'TypeOfProvider' element. Gellens, et al. Expires April 16, 2015 [Page 62] Internet-Draft Additional Call Data October 2014 Description: A short description of the type of service provider. The initial set of values is defined in Figure 1. 10.1.6. Service Delivered Registry This document creates a new sub-registry called 'Service Delivered'. As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should consider whether the proposed service is unique from existing services and the definition of the service will be clear to implementors and PSAPs/responders. The content of this registry includes: Name: The value used in the 'ServiceType' element. Description: Short description identifying the nature of the service. The initial set of values are defined in Figure 3. 10.1.7. Device Classification Registry This document creates a new sub-registry called 'Device Classification'. As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should consider whether the proposed class is unique from existing classes and the definition of the class will be clear to implementors and PSAPs/responders. The content of this registry includes: Token: Value used in the 'DeviceClassification' element. Description: Short description identifying the device type. The initial set of values are defined in Figure 5. 10.1.8. Device ID Type Type Registry This document creates a new sub-registry called 'Additional Call Data Device ID Type'. As defined in [RFC5226], this registry operates under "Expert Review" rules. The expert should ascertain that the proposed type is well understood, and provides the information useful to PSAPs and responders to uniquely identify a device. The content of this registry includes: Token: The value to be placed in the 'TypeOfDeviceID' element. Gellens, et al. Expires April 16, 2015 [Page 63] Internet-Draft Additional Call Data October 2014 Description: Short description identifying the type of the device ID. The initial set of values are defined in Figure 6. 10.1.9. Device/Service Data Type Registry This document creates a new sub-registry called 'Device/Service Data Type Registry'. As defined in [RFC5226], this registry operates under "Expert Review" and "Specification Required" rules. The expert should ascertain that the proposed type is well understood, and provides information useful to PSAPs and responders. The specification must contain a complete description of the data, and a precise format specification suitable to allow interoperable implementations. The content of this registry includes: Token: The value to be placed in the <DeviceSpecificType> element. Description: Short description identifying the the data. Specification: Citation for the specification of the data. The initial set of values are listed in Figure 24. +----------+----------------------------------------+---------------+ | Token | Description | Specification | +----------+----------------------------------------+---------------+ | IEEE1512 | Common Incident Management Message Set | IEEE 1512-2006| +----------+----------------------------------------+---------------+ Figure 24: Device/Service Data Type Registry. 10.1.10. Emergency Call Data Types Registry This document creates a new sub-registry called 'Emergency Call Data Types' in the 'purpose' registry established by RFC 3261 [RFC3261]. As defined in [RFC5226], this registry operates under "Expert Review" and "Specification Required" rules. The expert is responsible for verifying that the document contains a complete and clear specification and the proposed functionality does not obviously duplicate existing functionality. The content of this registry includes: Token: The root of the data's MIME subtype (not including the 'EmergencyCallData' prefix and any suffix such as '+xml') Gellens, et al. Expires April 16, 2015 [Page 64] Internet-Draft Additional Call Data October 2014 Reference: The document that describes the data object Note that the values from this registry are part of the 'EmergencyCallData' compound value; when used as a value of the 'purpose' parameter of the Call-Info header, the values listed in this registry are prefixed by 'EmergencyCallData.' per the the 'EmergencyCallData' registation Section 10.2. The initial set of values are listed in Figure 25. +----------------+------------+ | Token | Reference | +----------------+------------+ | ProviderInfo | [This RFC] | | ServiceInfo | [This RFC] | | DeviceInfo | [This RFC] | | SubscriberInfo | [This RFC] | | Comment | [This RFC] | +----------------+------------+ Figure 25: Additional Data Blocks Registry. 10.2. 'EmergencyCallData' Purpose Parameter Value This document defines the 'EmergencyCallData' value for the "purpose" parameter of the Call-Info header field. The Call-Info header and the corresponding registry for the 'purpose' parameter was established with RFC 3261 [RFC3261]. Note that 'EmergencyCallData' is a compound value; when used as a value of the 'purpose' parameter of the Call-Info header, 'EmergencyCallData' is immediately followed by a dot ('.') and a value from the 'Emergency Call Data Types' registry Section 10.1.10. Header Parameter New Field Name Value Reference ---------- --------- ----------------- --------- Call-Info purpose EmergencyCallData [This RFC] 10.3. URN Sub-Namespace Registration for provided-by Registry Entry This section registers the namespace specified in Section 10.5.1 in the provided-by registry established by RFC 4119, for usage within the <provided-by> element of a PIDF-LO. Gellens, et al. Expires April 16, 2015 [Page 65] Internet-Draft Additional Call Data October 2014 The schema for the provided-by element used by this document is specified in Section 7.6. 10.4. MIME Registrations 10.4.1. MIME Content-type Registration for 'application/ EmergencyCallData.ProviderInfo+xml' This specification requests the registration of a new MIME type according to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. MIME media type name: application MIME subtype name: EmergencyCallData.ProviderInfo+xml Mandatory parameters: none Optional parameters: charset (indicates the character encoding of the contents) Encoding considerations: Uses XML, which can contain 8-bit characters, depending on the character encoding. See Section 3.2 of RFC 7303 [RFC7303]. Security considerations: This content type is designed to carry the data provider information, which is a sub-category of additional data about an emergency call. Since this data may contain personal information, appropriate precautions might be needed to limit unauthorized access, inappropriate disclosure, and eavesdropping of personal information. Please refer to Section 8 and Section 9 for more information. Interoperability considerations: None Published specification: [TBD: This specification] Applications which use this media type: Emergency Services Additional information: Magic Number: None File Extension: .xml Macintosh file type code: 'TEXT' Gellens, et al. Expires April 16, 2015 [Page 66] Internet-Draft Additional Call Data October 2014 Person and email address for further information: Hannes Tschofenig, Hannes.Tschofenig@gmx.net Intended usage: LIMITED USE Author: This specification is a work item of the IETF ECRIT working group, with mailing list address <ecrit@ietf.org>. Change controller: The IESG <ietf@ietf.org> 10.4.2. MIME Content-type Registration for 'application/ EmergencyCallData.ServiceInfo+xml' This specification requests the registration of a new MIME type according to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. MIME media type name: application MIME subtype name: EmergencyCallData.ServiceInfo+xml Mandatory parameters: none Optional parameters: charset (indicates the character encoding of the contents) Encoding considerations: Uses XML, which can contain 8-bit characters, depending on the character encoding. See Section 3.2 of RFC 7303 [RFC7303]. Security considerations: This content type is designed to carry the service information, which is a sub-category of additional data about an emergency call. Since this data may contain personal information, appropriate precautions may be needed to limit unauthorized access, inappropriate disclosure, and eavesdropping of personal information. Please refer to Section 8 and Section 9 for more information. Interoperability considerations: None Published specification: [TBD: This specification] Applications which use this media type: Emergency Services Additional information: Magic Number: None Gellens, et al. Expires April 16, 2015 [Page 67] Internet-Draft Additional Call Data October 2014 File Extension: .xml Macintosh file type code: 'TEXT' Person and email address for further information: Hannes Tschofenig, Hannes.Tschofenig@gmx.net Intended usage: LIMITED USE Author: This specification is a work item of the IETF ECRIT working group, with mailing list address <ecrit@ietf.org>. Change controller: The IESG <ietf@ietf.org> 10.4.3. MIME Content-type Registration for 'application/ EmergencyCallData.DeviceInfo+xml' This specification requests the registration of a new MIME type according to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. MIME media type name: application MIME subtype name: EmergencyCallData.DeviceInfo+xml Mandatory parameters: none Optional parameters: charset (indicates the character encoding of the contents) Encoding considerations: Uses XML, which can contain 8-bit characters, depending on the character encoding. See Section 3.2 of RFC 7303 [RFC7303]. Security considerations: This content type is designed to carry device information, which is a sub-category of additional data about an emergency call. Since this data contains personal information, appropriate precautions need to be taken to limit unauthorized access, inappropriate disclosure to third parties, and eavesdropping of this information. Please refer to Section 8 and Section 9 for more information. Interoperability considerations: None Published specification: [TBD: This specification] Applications which use this media type: Emergency Services Gellens, et al. Expires April 16, 2015 [Page 68] Internet-Draft Additional Call Data October 2014 Additional information: Magic Number: None File Extension: .xml Macintosh file type code: 'TEXT' Person and email address for further information: Hannes Tschofenig, Hannes.Tschofenig@gmx.net Intended usage: LIMITED USE Author: This specification is a work item of the IETF ECRIT working group, with mailing list address <ecrit@ietf.org>. Change controller: The IESG <ietf@ietf.org> 10.4.4. MIME Content-type Registration for 'application/ EmergencyCallData.SubscriberInfo+xml' This specification requests the registration of a new MIME type according to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. MIME media type name: application MIME subtype name: EmergencyCallData.SubscriberInfo+xml Mandatory parameters: none Optional parameters: charset (indicates the character encoding of the contents) Encoding considerations: Uses XML, which can contain 8-bit characters, depending on the character encoding. See Section 3.2 of RFC 7303 [RFC7303]. Security considerations: This content type is designed to carry owner/subscriber information, which is a sub-category of additional data about an emergency call. Since this data contains personal information, appropriate precautions need to be taken to limit unauthorized access, inappropriate disclosure to third parties, and eavesdropping of this information. Please refer to Section 8 and Section 9 for more information. Interoperability considerations: None Gellens, et al. Expires April 16, 2015 [Page 69] Internet-Draft Additional Call Data October 2014 Published specification: [TBD: This specification] Applications which use this media type: Emergency Services Additional information: Magic Number: None File Extension: .xml Macintosh file type code: 'TEXT' Person and email address for further information: Hannes Tschofenig, Hannes.Tschofenig@gmx.net Intended usage: LIMITED USE Author: This specification is a work item of the IETF ECRIT working group, with mailing list address <ecrit@ietf.org>. Change controller: The IESG <ietf@ietf.org> 10.4.5. MIME Content-type Registration for 'application/ EmergencyCallData.Comment+xml' This specification requests the registration of a new MIME type according to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. MIME media type name: application MIME subtype name: EmergencyCallData.Comment+xml Mandatory parameters: none Optional parameters: charset (indicates the character encoding of the contents) Encoding considerations: Uses XML, which can contain 8-bit characters, depending on the character encoding. See Section 3.2 of RFC 7303 [RFC7303]. Security considerations: This content type is designed to carry a comment, which is a sub-category of additional data about an emergency call. This data may contain personal information. Appropriate precautions may be needed to limit unauthorized access, inappropriate disclosure to third parties, and Gellens, et al. Expires April 16, 2015 [Page 70] Internet-Draft Additional Call Data October 2014 eavesdropping of this information. Please refer to Section 8 and Section 9 for more information. Interoperability considerations: None Published specification: [TBD: This specification] Applications which use this media type: Emergency Services Additional information: Magic Number: None File Extension: .xml Macintosh file type code: 'TEXT' Person and email address for further information: Hannes Tschofenig, Hannes.Tschofenig@gmx.net Intended usage: LIMITED USE Author: This specification is a work item of the IETF ECRIT working group, with mailing list address <ecrit@ietf.org>. Change controller: The IESG <ietf@ietf.org> 10.5. URN Sub-Namespace Registration 10.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:EmergencyCallData Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as delegated by the IESG <iesg@ietf.org>. XML: Gellens, et al. Expires April 16, 2015 [Page 71] Internet-Draft Additional Call Data October 2014 BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/> <title>Namespace for Additional Emergency Call Data</title> </head> <body> <h1>Namespace for Additional Data related to an Emergency Call </h1> <p>See [TBD: This document].</p> </body> </html> END 10.5.2. Registration for urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as delegated by the IESG <iesg@ietf.org>. XML: Gellens, et al. Expires April 16, 2015 [Page 72] Internet-Draft Additional Call Data October 2014 BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/> <title>Namespace for Additional Emergency Call Data: Data Provider Information</title> </head> <body> <h1>Namespace for Additional Data related to an Emergency Call </h1> <h2>Data Provider Information</h2> <p>See [TBD: This document].</p> </body> </html> END 10.5.3. Registration for urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as delegated by the IESG <iesg@ietf.org>. XML: Gellens, et al. Expires April 16, 2015 [Page 73] Internet-Draft Additional Call Data October 2014 BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/> <title>Namespace for Additional Emergency Call Data: Service Information</title> </head> <body> <h1>Namespace for Additional Data related to an Emergency Call </h1> <h2>Service Information</h2> <p>See [TBD: This document].</p> </body> </html> END 10.5.4. Registration for urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as delegated by the IESG <iesg@ietf.org>. XML: Gellens, et al. Expires April 16, 2015 [Page 74] Internet-Draft Additional Call Data October 2014 BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/> <title>Namespace for Additional Emergency Call Data: Device Information</title> </head> <body> <h1>Namespace for Additional Data related to an Emergency Call </h1> <h2>Device Information</h2> <p>See [TBD: This document].</p> </body> </html> END 10.5.5. Registration for urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as delegated by the IESG <iesg@ietf.org>. XML: Gellens, et al. Expires April 16, 2015 [Page 75] Internet-Draft Additional Call Data October 2014 BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/> <title>Namespace for Additional Emergency Call Data: Owner/Subscriber Information</title> </head> <body> <h1>Namespace for Additional Data related to an Emergency Call </h1> <h2> Owner/Subscriber Information</h2> <p>See [TBD: This document].</p> </body> </html> END 10.5.6. Registration for urn:ietf:params:xml:ns:EmergencyCallData:Comment This section registers a new XML namespace, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as delegated by the IESG <iesg@ietf.org>. XML: Gellens, et al. Expires April 16, 2015 [Page 76] Internet-Draft Additional Call Data October 2014 BEGIN <?xml version="1.0"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"/> <title>Namespace for Additional Emergency Call Data:Comment </title> </head> <body> <h1>Namespace for Additional Data related to an Emergency Call </h1> <h2> Comment</h2> <p>See [TBD: This document].</p> </body> </html> END 10.6. Schema Registrations This specification registers five schemas, as per the guidelines in RFC 3688 [RFC3688]. URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo 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 15. URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo 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 16. URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo 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 17. URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo Gellens, et al. Expires April 16, 2015 [Page 77] Internet-Draft Additional Call Data October 2014 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 7.4. URI: urn:ietf:params:xml:schema:emergencycalldata: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 7.5. 10.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 11. 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 many NENA participants, including Delaine Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, and Robert (Bob) Sherry. We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin Thomson, Keith Drage, Laura Liess, Chris Santer, and Barbara Stark for their review comments. Guy Caron deserves special mention for his detailed and extensive review comments. Gellens, et al. Expires April 16, 2015 [Page 78] Internet-Draft Additional Call Data October 2014 12. References 12.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. [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, F., Watson, M., and M. Zonoun, "MIME media types for ISUP and QSIG Objects", RFC 3204, December 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. [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks", RFC 3325, November 2002. [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter", RFC 3459, January 2003. [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. [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, October 2008. [RFC5621] Camarillo, G., "Message Body Handling in the Session Initiation Protocol (SIP)", RFC 5621, September 2009. [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, August 2011. [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 6351, August 2011. Gellens, et al. Expires April 16, 2015 [Page 79] Internet-Draft Additional Call Data October 2014 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13, RFC 6838, January 2013. [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, July 2014. 12.2. Informational References [I-D.gellens-slim-negotiating-human-language] Gellens, R., "Negotiating Human Language in Real-Time Communications", draft-gellens-slim-negotiating-human- language (work in progress), October 2014. [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)", RFC 3840, August 2004. [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, December 2004. [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for Emergency Context Resolution with Internet Technologies", RFC 5012, January 2008. [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)", RFC 5139, February 2008. [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations", RFC 5491, March 2009. [RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and Framework", RFC 5582, September 2009. [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. Thomson, "Dynamic Extensions to the Presence Information Data Format Location Object (PIDF-LO)", RFC 5962, September 2010. [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. Gellens, et al. Expires April 16, 2015 [Page 80] Internet-Draft Additional Call Data October 2014 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and R. George, "Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF- LO)", RFC 6848, January 2013. [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for Communications Services in Support of Emergency Calling", BCP 181, RFC 6881, March 2013. [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., Morris, J., Hansen, M., and R. Smith, "Privacy Considerations for Internet Protocols", RFC 6973, July 2013. [RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. Thomson, "Relative Location Representation", RFC 7035, October 2013. [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. Patel, "Public Safety Answering Point (PSAP) Callback", RFC 7090, April 2014. 12.3. URIs [1] http://www.nena.org/?page=cid2014 [2] http://www.nena.org/?page=CompanyID 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. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="urn:ietf:params:xml:ns:vcard-4.0" xmlns:ns1="urn:ietf:params:xml:ns:vcard-4.0"> <!-- 3.3 iana-token = xsd:string { pattern = "[a-zA-Z0-9-]+" } x-name = xsd:string { pattern = "x-[a-zA-Z0-9-]+" } --> Gellens, et al. Expires April 16, 2015 [Page 81] Internet-Draft Additional Call Data October 2014 <xs:simpleType name="iana-token"> <xs:annotation> <xs:documentation>vCard Format Specification </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"/> </xs:simpleType> <xs:simpleType name="x-name"> <xs:restriction base="xs:string"/> </xs:simpleType> <!-- 4.1 --> <xs:element name="text" type="xs:string"/> <xs:group name="value-text-list"> <xs:sequence> <xs:element maxOccurs="unbounded" ref="ns1:text"/> </xs:sequence> </xs:group> <!-- 4.2 --> <xs:element name="uri" type="xs:anyURI"/> <!-- 4.3.1 --> <xs:element name="date" substitutionGroup="ns1:value-date-and-or-time"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="\d{8}|\d{4}-\d\d| --\d\d(\d\d)?|---\d\d"/> </xs:restriction> </xs:simpleType> </xs:element> <!-- 4.3.2 --> <xs:element name="time" substitutionGroup="ns1:value-date-and-or-time"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d) (Z|[+\-]\d\d(\d\d)?)?"/> </xs:restriction> </xs:simpleType> </xs:element> <!-- 4.3.3 --> <xs:element name="date-time" substitutionGroup="ns1:value-date-and-or-time"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value= Gellens, et al. Expires April 16, 2015 [Page 82] Internet-Draft Additional Call Data October 2014 "(\d{8}|--\d{4}|---\d\d)T \d\d(\d\d(\d\d)?)?(Z|[+\-]\d\d(\d\d)?)?"/> </xs:restriction> </xs:simpleType> </xs:element> <!-- 4.3.4 --> <xs:element name="value-date-and-or-time" abstract="true"/> <!-- 4.3.5 --> <xs:complexType name="value-timestamp"> <xs:sequence> <xs:element ref="ns1:timestamp"/> </xs:sequence> </xs:complexType> <xs:element name="timestamp"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="\d{8}T\d{6}(Z|[+\-]\d\d(\d\d)?)?"/> </xs:restriction> </xs:simpleType> </xs:element> <!-- 4.4 --> <xs:element name="boolean" type="xs:boolean"/> <!-- 4.5 --> <xs:element name="integer" type="xs:integer"/> <!-- 4.6 --> <xs:element name="float" type="xs:float"/> <!-- 4.7 --> <xs:element name="utc-offset"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="[+\-]\d\d(\d\d)?"/> </xs:restriction> </xs:simpleType> </xs:element> <!-- 4.8 --> <xs:element name="language-tag"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="([a-z]{2,3}((-[a-z]{3}){0,3})?|[a-z]{4,8}) (-[a-z]{4})?(-([a-z]{2}|\d{3}))?(-([0-9a-z]{5,8}| \d[0-9a-z]{3}))*(-[0-9a-wyz](-[0-9a-z]{2,8})+)* (-x(-[0-9a-z]{1,8})+)?|x(-[0-9a-z]{1,8})+|[a-z]{1,3} (-[0-9a-z]{2,8}){1,2}"/> </xs:restriction> </xs:simpleType> </xs:element> <!-- Gellens, et al. Expires April 16, 2015 [Page 83] Internet-Draft Additional Call Data October 2014 5.1 --> <xs:group name="param-language"> <xs:annotation> <xs:documentation>Section 5: Parameters</xs:documentation> </xs:annotation> <xs:sequence> <xs:element minOccurs="0" ref="ns1:language"/> </xs:sequence> </xs:group> <xs:element name="language"> <xs:complexType> <xs:sequence> <xs:element ref="ns1:language-tag"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 5.2 --> <xs:group name="param-pref"> <xs:sequence> <xs:element minOccurs="0" ref="ns1:pref"/> </xs:sequence> </xs:group> <xs:element name="pref"> <xs:complexType> <xs:sequence> <xs:element name="integer"> <xs:simpleType> <xs:restriction base="xs:integer"> <xs:minInclusive value="1"/> <xs:maxInclusive value="100"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <!-- 5.4 --> <xs:group name="param-altid"> <xs:sequence> <xs:element minOccurs="0" ref="ns1:altid"/> </xs:sequence> </xs:group> <xs:element name="altid"> <xs:complexType> <xs:sequence> <xs:element ref="ns1:text"/> </xs:sequence> Gellens, et al. Expires April 16, 2015 [Page 84] Internet-Draft Additional Call Data October 2014 </xs:complexType> </xs:element> <!-- 5.5 --> <xs:group name="param-pid"> <xs:sequence> <xs:element minOccurs="0" ref="ns1:pid"/> </xs:sequence> </xs:group> <xs:element name="pid"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="text"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="\d+(\.\d+)?"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <!-- 5.6 --> <xs:group name="param-type"> <xs:sequence> <xs:element minOccurs="0" ref="ns1:type"/> </xs:sequence> </xs:group> <xs:element name="type"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="text"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="work"/> <xs:enumeration value="home"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <!-- 5.7 --> <xs:group name="param-mediatype"> <xs:sequence> <xs:element minOccurs="0" ref="ns1:mediatype"/> </xs:sequence> </xs:group> <xs:element name="mediatype"> Gellens, et al. Expires April 16, 2015 [Page 85] Internet-Draft Additional Call Data October 2014 <xs:complexType> <xs:sequence> <xs:element ref="ns1:text"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 5.8 --> <xs:group name="param-calscale"> <xs:sequence> <xs:element minOccurs="0" ref="ns1:calscale"/> </xs:sequence> </xs:group> <xs:element name="calscale"> <xs:complexType> <xs:sequence> <xs:element name="text"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="gregorian"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <!-- 5.9 --> <xs:group name="param-sort-as"> <xs:sequence> <xs:element minOccurs="0" ref="ns1:sort-as"/> </xs:sequence> </xs:group> <xs:element name="sort-as"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" ref="ns1:text"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 5.10 --> <xs:group name="param-geo"> <xs:sequence> <xs:element minOccurs="0" name="geo"> <xs:complexType> <xs:sequence> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> Gellens, et al. Expires April 16, 2015 [Page 86] Internet-Draft Additional Call Data October 2014 </xs:sequence> </xs:group> <!-- 5.11 --> <xs:group name="param-tz"> <xs:sequence> <xs:element minOccurs="0" name="tz"> <xs:complexType> <xs:choice> <xs:element ref="ns1:text"/> <xs:element ref="ns1:uri"/> </xs:choice> </xs:complexType> </xs:element> </xs:sequence> </xs:group> <!-- 6.1.3 --> <xs:element name="source"> <xs:complexType> <xs:sequence> <xs:element name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.1.4 --> <xs:element name="kind"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="unbounded" name="text"> <xs:simpleType> <xs:union memberTypes="ns1:x-name ns1:iana-token"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="individual"/> </xs:restriction> </xs:simpleType> Gellens, et al. Expires April 16, 2015 [Page 87] Internet-Draft Additional Call Data October 2014 <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="group"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="org"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="location"/> </xs:restriction> </xs:simpleType> </xs:union> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.2.1 --> <xs:element name="fn"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-language"/> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:text"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.2.2 --> <xs:element name="n"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-language"/> Gellens, et al. Expires April 16, 2015 [Page 88] Internet-Draft Additional Call Data October 2014 <xs:group ref="ns1:param-sort-as"/> <xs:group ref="ns1:param-altid"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element maxOccurs="unbounded" ref="ns1:surname"/> <xs:element maxOccurs="unbounded" ref="ns1:given"/> <xs:element maxOccurs="unbounded" ref="ns1:additional"/> <xs:element maxOccurs="unbounded" ref="ns1:prefix"/> <xs:element maxOccurs="unbounded" ref="ns1:suffix"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="surname" type="xs:string"/> <xs:element name="given" type="xs:string"/> <xs:element name="additional" type="xs:string"/> <xs:element name="prefix" type="xs:string"/> <xs:element name="suffix" type="xs:string"/> <!-- 6.2.3 --> <xs:element name="nickname"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-language"/> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> </xs:sequence> </xs:complexType> </xs:element> <xs:group ref="ns1:value-text-list"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.2.4 --> <xs:element name="photo"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> Gellens, et al. Expires April 16, 2015 [Page 89] Internet-Draft Additional Call Data October 2014 <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.2.5 --> <xs:element name="bday"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-calscale"/> </xs:sequence> </xs:complexType> </xs:element> <xs:choice> <xs:element ref="ns1:value-date-and-or-time"/> <xs:element ref="ns1:text"/> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.2.6 --> <xs:element name="anniversary"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-calscale"/> </xs:sequence> </xs:complexType> </xs:element> <xs:choice> <xs:element ref="ns1:value-date-and-or-time"/> <xs:element ref="ns1:text"/> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.2.7 --> <xs:element name="gender"> Gellens, et al. Expires April 16, 2015 [Page 90] Internet-Draft Additional Call Data October 2014 <xs:complexType> <xs:sequence> <xs:element ref="ns1:sex"/> <xs:element minOccurs="0" ref="ns1:identity"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="sex"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value=""/> <xs:enumeration value="M"/> <xs:enumeration value="F"/> <xs:enumeration value="O"/> <xs:enumeration value="N"/> <xs:enumeration value="U"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="identity" type="xs:string"/> <!-- 6.3.1 --> <xs:group name="param-label"> <xs:sequence> <xs:element minOccurs="0" ref="ns1:label"/> </xs:sequence> </xs:group> <xs:element name="label"> <xs:complexType> <xs:sequence> <xs:element ref="ns1:text"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="adr"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-language"/> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-geo"/> <xs:group ref="ns1:param-tz"/> <xs:group ref="ns1:param-label"/> </xs:sequence> Gellens, et al. Expires April 16, 2015 [Page 91] Internet-Draft Additional Call Data October 2014 </xs:complexType> </xs:element> <xs:element maxOccurs="unbounded" ref="ns1:pobox"/> <xs:element maxOccurs="unbounded" ref="ns1:ext"/> <xs:element maxOccurs="unbounded" ref="ns1:street"/> <xs:element maxOccurs="unbounded" ref="ns1:locality"/> <xs:element maxOccurs="unbounded" ref="ns1:region"/> <xs:element maxOccurs="unbounded" ref="ns1:code"/> <xs:element maxOccurs="unbounded" ref="ns1:country"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="pobox" type="xs:string"/> <xs:element name="ext" type="xs:string"/> <xs:element name="street" type="xs:string"/> <xs:element name="locality" type="xs:string"/> <xs:element name="region" type="xs:string"/> <xs:element name="code" type="xs:string"/> <xs:element name="country" type="xs:string"/> <!-- 6.4.1 --> <xs:element name="tel"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:element minOccurs="0" name="type"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="text"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="work"/> <xs:enumeration value="home"/> <xs:enumeration value="text"/> <xs:enumeration value="voice"/> <xs:enumeration value="fax"/> <xs:enumeration value="cell"/> <xs:enumeration value="video"/> <xs:enumeration value="pager"/> <xs:enumeration value="textphone"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> Gellens, et al. Expires April 16, 2015 [Page 92] Internet-Draft Additional Call Data October 2014 </xs:complexType> </xs:element> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:choice> <xs:element ref="ns1:text"/> <xs:element ref="ns1:uri"/> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.4.2 --> <xs:element name="email"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:text"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.4.3 --> <xs:element name="impp"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> Gellens, et al. Expires April 16, 2015 [Page 93] Internet-Draft Additional Call Data October 2014 </xs:complexType> </xs:element> <!-- 6.4.4 --> <xs:element name="lang"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:language-tag"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.5.1 --> <xs:group name="property-tz"> <xs:sequence> <xs:element name="tz"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:choice> <xs:element ref="ns1:text"/> <xs:element ref="ns1:uri"/> <xs:element ref="ns1:utc-offset"/> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:group> <!-- 6.5.2 --> Gellens, et al. Expires April 16, 2015 [Page 94] Internet-Draft Additional Call Data October 2014 <xs:group name="property-geo"> <xs:sequence> <xs:element name="geo"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:group> <!-- 6.6.1 --> <xs:element name="title"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-language"/> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:text"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.6.2 --> <xs:element name="role"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> Gellens, et al. Expires April 16, 2015 [Page 95] Internet-Draft Additional Call Data October 2014 <xs:group ref="ns1:param-language"/> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:text"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.6.3 --> <xs:element name="logo"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-language"/> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.6.4 --> <xs:element name="org"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-language"/> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-sort-as"/> </xs:sequence> </xs:complexType> </xs:element> Gellens, et al. Expires April 16, 2015 [Page 96] Internet-Draft Additional Call Data October 2014 <xs:group ref="ns1:value-text-list"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.6.5 --> <xs:element name="member"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.6.6 --> <xs:element name="related"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:element minOccurs="0" name="type"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="text"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="work"/> <xs:enumeration value="home"/> <xs:enumeration value="contact"/> <xs:enumeration value="acquaintance"/> <xs:enumeration value="friend"/> <xs:enumeration value="met"/> <xs:enumeration value="co-worker"/> <xs:enumeration value="colleague"/> <xs:enumeration value="co-resident"/> <xs:enumeration value="neighbor"/> Gellens, et al. Expires April 16, 2015 [Page 97] Internet-Draft Additional Call Data October 2014 <xs:enumeration value="child"/> <xs:enumeration value="parent"/> <xs:enumeration value="sibling"/> <xs:enumeration value="spouse"/> <xs:enumeration value="kin"/> <xs:enumeration value="muse"/> <xs:enumeration value="crush"/> <xs:enumeration value="date"/> <xs:enumeration value="sweetheart"/> <xs:enumeration value="me"/> <xs:enumeration value="agent"/> <xs:enumeration value="emergency"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:choice> <xs:element ref="ns1:uri"/> <xs:element ref="ns1:text"/> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.7.1 --> <xs:element name="categories"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> </xs:sequence> </xs:complexType> </xs:element> <xs:group ref="ns1:value-text-list"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.7.2 --> Gellens, et al. Expires April 16, 2015 [Page 98] Internet-Draft Additional Call Data October 2014 <xs:element name="note"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-language"/> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:text"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.7.3 --> <xs:element name="prodid"> <xs:complexType> <xs:sequence> <xs:element ref="ns1:text"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.7.4 --> <xs:element name="rev" type="ns1:value-timestamp"/> <!-- 6.7.5 --> <xs:element name="sound"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-language"/> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> Gellens, et al. Expires April 16, 2015 [Page 99] Internet-Draft Additional Call Data October 2014 <!-- 6.7.6 --> <xs:element name="uid"> <xs:complexType> <xs:sequence> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.7.7 --> <xs:element name="clientpidmap"> <xs:complexType> <xs:sequence> <xs:element ref="ns1:sourceid"/> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="sourceid" type="xs:positiveInteger"/> <!-- 6.7.8 --> <xs:element name="url"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.8.1 --> <xs:element name="key"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> Gellens, et al. Expires April 16, 2015 [Page 100] Internet-Draft Additional Call Data October 2014 <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:choice> <xs:element ref="ns1:uri"/> <xs:element ref="ns1:text"/> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.9.1 --> <xs:element name="fburl"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> <!-- 6.9.2 --> <xs:element name="caladruri"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> Gellens, et al. Expires April 16, 2015 [Page 101] Internet-Draft Additional Call Data October 2014 </xs:element> <!-- 6.9.3 --> <xs:element name="caluri"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" name="parameters"> <xs:complexType> <xs:sequence> <xs:group ref="ns1:param-altid"/> <xs:group ref="ns1:param-pid"/> <xs:group ref="ns1:param-pref"/> <xs:group ref="ns1:param-type"/> <xs:group ref="ns1:param-mediatype"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element ref="ns1:uri"/> </xs:sequence> </xs:complexType> </xs:element> <!-- Top-level grammar --> <xs:group name="property"> <xs:choice> <xs:element ref="ns1:adr"/> <xs:element ref="ns1:anniversary"/> <xs:element ref="ns1:bday"/> <xs:element ref="ns1:caladruri"/> <xs:element ref="ns1:caluri"/> <xs:element ref="ns1:categories"/> <xs:element ref="ns1:clientpidmap"/> <xs:element ref="ns1:email"/> <xs:element ref="ns1:fburl"/> <xs:element ref="ns1:fn"/> <xs:group ref="ns1:property-geo"/> <xs:element ref="ns1:impp"/> <xs:element ref="ns1:key"/> <xs:element ref="ns1:kind"/> <xs:element ref="ns1:lang"/> <xs:element ref="ns1:logo"/> <xs:element ref="ns1:member"/> <xs:element ref="ns1:n"/> <xs:element ref="ns1:nickname"/> <xs:element ref="ns1:note"/> <xs:element ref="ns1:org"/> <xs:element ref="ns1:photo"/> <xs:element ref="ns1:prodid"/> <xs:element ref="ns1:related"/> <xs:element ref="ns1:rev"/> Gellens, et al. Expires April 16, 2015 [Page 102] Internet-Draft Additional Call Data October 2014 <xs:element ref="ns1:role"/> <xs:element ref="ns1:gender"/> <xs:element ref="ns1:sound"/> <xs:element ref="ns1:source"/> <xs:element ref="ns1:tel"/> <xs:element ref="ns1:title"/> <xs:group ref="ns1:property-tz"/> <xs:element ref="ns1:uid"/> <xs:element ref="ns1:url"/> </xs:choice> </xs:group> <xs:element name="vcards"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" ref="ns1:vcard"/> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="vcardType"> <xs:complexContent> <xs:restriction base="xs:anyType"> <xs:choice maxOccurs="unbounded"> <xs:group ref="ns1:property"/> <xs:element ref="ns1:group"/> </xs:choice> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:element name="vcard" type="ns1:vcardType"/> <xs:element name="group"> <xs:complexType> <xs:group minOccurs="0" maxOccurs="unbounded" ref="ns1:property"/> <xs:attribute name="name" use="required"/> </xs:complexType> </xs:element> </xs:schema> Gellens, et al. Expires April 16, 2015 [Page 103] Internet-Draft Additional Call Data October 2014 Authors' Addresses Randall Gellens Qualcomm Technologies, Inc. 5775 Morehouse Drive San Diego, CA 92121 US Email: rg+ietf@qti.qualcomm.com Brian Rosen NeuStar 470 Conrad Dr. Mars, PA 16046 US Phone: +1 724 382 1051 Email: br@brianrosen.net Hannes Tschofenig (no affiliation) 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 James Winterbottom (no affiliation) AU Email: a.james.winterbottom@gmail.com Gellens, et al. Expires April 16, 2015 [Page 104]