SIPPING Working Group V. Hilt Internet-Draft Bell Labs/Alcatel-Lucent Intended status: Standards Track D. Worley Expires: December 14, 2010 Nortel Networks Corp. G. Camarillo Ericsson J. Rosenberg jdrosen.net June 12, 2010 A User Agent Profile Data Set for Media Policy draft-ietf-sipping-media-policy-dataset-10 Abstract This specification defines a document format for the media properties of Session Initiation Protocol (SIP) sessions. Examples for media properties are the codecs or media types used in a session. This document format is based on XML and can be used to describe the properties of a specific SIP session or to define policies that are then applied to SIP sessions. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 14, 2010. Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of Hilt, et al. Expires December 14, 2010 [Page 1] Internet-Draft Media Policy Dataset June 2010 publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Media Policy Dataset Format . . . . . . . . . . . . . . . . . 5 3.1. Namespace and MIME Type . . . . . . . . . . . . . . . . . 5 3.2. Extensibility . . . . . . . . . . . . . . . . . . . . . . 5 3.3. Attributes . . . . . . . . . . . . . . . . . . . . . . . . 6 3.3.1. The 'visibility' Attribute . . . . . . . . . . . . . . 6 3.3.2. The 'direction' Attributes . . . . . . . . . . . . . . 6 3.3.3. The 'q' Attribute . . . . . . . . . . . . . . . . . . 6 3.3.4. The 'label' Attribute . . . . . . . . . . . . . . . . 7 3.4. The Element . . . . . . . . . . . . . . . . 7 4. Session Info Documents . . . . . . . . . . . . . . . . . . . . 7 4.1. Mapping SDP to Session Info Documents . . . . . . . . . . 8 4.2. The Element . . . . . . . . . . . . . . . . 9 4.3. The Element . . . . . . . . . . . . . . . . . . 9 4.3.1. The Element . . . . . . . . . . . . . . . . . 9 4.4. The Element . . . . . . . . . . . . 10 4.4.1. The Element . . . . . . . . . . . 11 4.4.2. The Element . . . . . . . . . . . 12 4.4.3. The Element . . . . . . . . . . . 12 5. Session Policy Documents . . . . . . . . . . . . . . . . . . . 13 5.1. Merging Session Policies . . . . . . . . . . . . . . . . . 13 5.1.1. Single Value Selection . . . . . . . . . . . . . . . . 13 5.1.2. Merging Sets . . . . . . . . . . . . . . . . . . . . . 14 5.1.3. Local Policy Server Selection . . . . . . . . . . . . 15 5.2. The Element . . . . . . . . . . . . . . . 15 5.3. The Element . . . . . . . . . . . . 15 5.4. The Element . . . . . . . . . . . . 16 5.5. The Element . . . . . . . . . . . . . . . 16 5.6. The Element . . . . . . . . . . . . . . 17 5.7. The Element . . . . . . . . . . . . . . . . 17 6. Common Media Policy Dataset Elements . . . . . . . . . . . . . 18 6.1. The Element . . . . . . . . . . . . . . . . . 18 6.2. The Element . . . . . . . . . . . . . . . . . . . 18 6.2.1. The Element . . . . . . . . . . . . . . . 18 6.2.2. The Element . . . . . . . . . . . . . 19 6.3. The Element . . . . . . . . . . . . . . . . . . . 19 6.4. The Element . . . . . . . . . . . . . . . 19 Hilt, et al. Expires December 14, 2010 [Page 2] Internet-Draft Media Policy Dataset June 2010 6.5. The Element . . . . . . . . . . . . . . . 20 6.6. The Element . . . . . . . . . . . . . . . . . . 21 6.7. The Element . . . . . . . . . . . . . . . . . . 22 6.7.1. The Element . . . . . . . . . . . 22 6.7.2. The Element . . . . . . . . . . . . . . . . 22 6.7.3. The Element . . . . . . . . . . . . . . . . . . 22 6.7.4. The Element . . . . . . . . . . . . . . 22 6.7.5. The Element . . . . . . . . . . . . . . . . . 22 6.8. Other Session Properties . . . . . . . . . . . . . . . . . 23 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.1. Session Policy Documents . . . . . . . . . . . . . . . . . 23 7.2. Session Information Documents . . . . . . . . . . . . . . 24 7.2.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 24 7.2.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . 25 8. Relax NG Definition . . . . . . . . . . . . . . . . . . . . . 27 9. Security Considerations . . . . . . . . . . . . . . . . . . . 34 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 10.1. MIME Registration . . . . . . . . . . . . . . . . . . . . 34 10.2. URN Sub-Namespace Registration . . . . . . . . . . . . . . 35 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 11.1. Normative References . . . . . . . . . . . . . . . . . . . 35 11.2. Informative References . . . . . . . . . . . . . . . . . . 37 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37 Hilt, et al. Expires December 14, 2010 [Page 3] Internet-Draft Media Policy Dataset June 2010 1. Introduction The Framework for Session Initiation Protocol (SIP) [RFC3261] User Agent Profile Delivery [I-D.ietf-sipping-config-framework] and the Framework for SIP Session Policies [I-D.ietf-sip-session-policy-framework] define mechanisms to convey session policies and configuration information from a network server to a user agent. An important piece of the information conveyed to the user agent relates to the media properties of the SIP sessions set up by the user agent. Examples for these media properties are the codecs and media types used, the media-intermediaries to be traversed or the maximum bandwidth available for media streams. This specification defines a document format for media properties of SIP sessions, the Media Policy Dataset Format (MPDF). This format can be used in two ways: first, it can be used to describe the properties of a given SIP session (e.g., the media types and codecs used). These MPDF documents are called session info documents and they are usually created based on the session description of a session. Second, the MPDF format can be used to define policies for SIP sessions in a session policy document. A session policy document defines properties for a session (e.g., the media types allowed in a session), independent of a specific session description. If used with the Framework for SIP Session Policies [I-D.ietf-sip-session-policy-framework], session info documents are used in conjunction with session-specific policies. A session info document is created by a UA based on the current session description and submitted to the policy server. The policy server examines the session info document, modifies it if necessary (e.g., by removing video streams if video is not permitted) and returns the possibly modified session info document to the UA. Session policy documents on the other hand are used to describe session-independent policies that can be submitted to the UA independent of a specific session. The two types of MPDF documents, session information and session policy documents, share the same set of XML elements to describe session properties. Since these elements are used in different contexts for session info and session policy documents, two different root elements exist for the two document types: is the root element for session information documents and is the root element for session policy documents. A user agent can receive multiple session policy documents from different sources. This can lead to a situation in which the user agent needs to apply multiple session policy documents to the same session. This standard specifies merging rules for those XML elements that can be present in session policy documents. It should Hilt, et al. Expires December 14, 2010 [Page 4] Internet-Draft Media Policy Dataset June 2010 be noted that these merging rules are part of the semantics of a session policy XML element. User agents implement the merging rules as part of implementing the element semantics. As a consequence, it is not possible to build an entity that can mechanically merge two session policy documents without understanding the semantics of all elements in the input documents. Merging rules are not needed for elements of session information documents since they are created by one source and describe a specific session. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 3. Media Policy Dataset Format This section discusses fundamental properties of the Media Policy Dataset Format (MPDF). 3.1. Namespace and MIME Type The MPDF format is based on XML [W3C.REC-xml-20040204]. A MPDF document MUST be well-formed and MUST be valid according to schemas, including extension schemas, available to the validator and applicable to the XML document. MPDF documents MUST be based on XML 1.0 and MUST be encoded using UTF-8. MPDF makes use of XML namespaces [W3C.REC-xml-names-19990114]. The namespace URIs for schemas defined in this specification are URNs [RFC2141], using the namespace identifier 'ietf' defined by [RFC2648] and extended by [RFC3688]. The namespace URN for the MPDF schema is: urn:ietf:params:xml:ns:mediadataset The MIME type for the Media Policy Dataset Format is: application/media-policy-dataset+xml 3.2. Extensibility The MPDF format can be extended using XML extension mechanisms if additional media properties are needed. In particular, elements from different XML namespaces MAY be present within a MPDF document for Hilt, et al. Expires December 14, 2010 [Page 5] Internet-Draft Media Policy Dataset June 2010 the purposes of extensibility; elements or attributes from unknown namespaces MUST be ignored. 3.3. Attributes The following attributes can be used with elements of the MPDF format. For each MPDF element it is defined, which of these attributes can be used. Attributes that are not defined for an element MUST be ignored. 3.3.1. The 'visibility' Attribute The attribute "visibility" specifies whether or not the user agent is permitted to display the property value to the user. This is used to hide setting values that the administrator may not want the user to see or know. The "visibility" attribute has two possible values: o visible: specifies that display of the property value is not restricted. This is the default value of the attribute if it is not specified. o hidden: Specifies that the user agent SHOULD NOT display the property value. Display of the property value may be allowed using special administrative interfaces, but is not appropriate to the ordinary user. 3.3.2. The 'direction' Attributes Some properties are unidirectional and only apply to messages or data streams transmitted into one direction. For example, a property for media streams can be restricted to outgoing media streams only. Unidirectional properties can be expressed by adding a 'direction' attribute to the respective element. The 'direction' attribute can have the following values: o recvonly: the property only applies to incoming messages/streams. o sendonly: the property only applies to outgoing messages/streams. o sendrecv: the property applies to messages/streams in both directions. This is the default value that is used if the 'direction' attribute is omitted. 3.3.3. The 'q' Attribute It should be possible to express a preference for a certain value, if multiple values are allowed within a property. For example, it should be possible to express that the codecs G.711 and G.729 are allowed, but G.711 is preferred. Preferences can be expressed by adding a 'q' attribute to a property element. Elements derived from Hilt, et al. Expires December 14, 2010 [Page 6] Internet-Draft Media Policy Dataset June 2010 the "setting" element for which multiple occurrences and values are allowed SHOULD have a "q" attribute if the order is significant. Typically these elements are contained in an element derived from the "setting_container" element. The 'q' attribute is only meaningful if the 'policy' attribute set to 'allowed'. It must be ignored in all other cases. An element with a higher 'q' value is preferred over one with a lower 'q' value. 'q' attribute values range from 0 to 1. The default value is 0.5. 3.3.4. The 'label' Attribute Some properties only apply to a specific media stream. The stream to which a property applies MUST be identifiable through a label [RFC4574]. Per-stream properties can be expressed by adding a 'label' attribute to the respective element. Such a property only applies to the identified stream. If there is no stream with this label, the element must be ignored. Per-stream properties require that the labels of media streams are known to the creator of a document (i.e., the profile delivery/policy server). These labels are part of the session description. 3.4. The Element The root element of a property set is it is the container that is provided to the user agent. The elements contained within a contain the specific properties which are to be applied to the user agent. The element is the root element for Session Info and Session Policy documents. 4. Session Info Documents Session info documents describe key properties of a SIP session such as the media streams used in the session. Session info documents are typically created based on an SDP [RFC4566] session description or an SDP offer/answer pair [RFC3264]. Session info documents can be used for session-specific policies [I-D.ietf-sip-session-policy-framework]. In this usage, a UA creates a session info document based on its SDP description(s) and sends this document to the policy server. The policy server modifies this document according to the policies that apply to the described session and returns a version of the session info document that is Hilt, et al. Expires December 14, 2010 [Page 7] Internet-Draft Media Policy Dataset June 2010 compliant to all policies. For example, if video streams are not permissible under current policies and the UA submits a session info document that contains a video stream, the policy server will remove the video stream from the XML markup and return the modified session info document to the UA. Session info documents use the container. They use elements described in this section and common elements described in Section 6. Elements that are only present in session info document do not require merging rules. If used in the context of session-specific policies, session info documents are sent to one policy server at a time only, therefore a UA does not need to merge multiple session info documents into one. A policy server needs to modify a session info document it has received according to its policies. The modification of session info documents is determined by the local policies of the policy server and outside the scope of this standard. A policy server can completely reject a session by returning an session info document with an empty element: <\session-info> 4.1. Mapping SDP to Session Info Documents If a UA has an SDP offer as well as an answer [RFC3264] and wants to create a session info document, the UA MUST use the answer to fill in the elements of the session info document except for the remote-host- port and local-host-port elements, which are taken from the remote and local session description respectively. The local session description is the one created locally by the UA (i.e., the offer if the UA has initiated the offer/answer exchange). The remote session description is the one received from the remote UA. The following rules describe the creation of session info documents based on SDP description(s) for a few exemplary elements. Other elements are created following the same principles. A UA MUST create a separate element for each m= line in an SDP description. The UA MUST insert the media type from the m= line into a element and MUST create a element for each codec listed in the m= line. The UA MUST create a element for each stream using the port taken from the m= line and the address from the corresponding c= line of the local session description. The UA MUST create a element using the port and address from Hilt, et al. Expires December 14, 2010 [Page 8] Internet-Draft Media Policy Dataset June 2010 the m= and c= lines for the same stream taken from the remote session description if this session description is available. The mapping from a session info document to a SDP description follows the same rules in the reverse direction. 4.2. The Element The element describes the properties of a specific SIP session. The element MAY occur multiple times inside a element. The element MAY contain one optional , and multiple (including zero) , , , and elements as well as elements from other namespaces. The MPDF elements are defined in Section 6. 4.3. The Element The element is a container that is used to describe the media streams used in a session. A element can contain multiple elements. Each element describes the properties (e.g., media type, codecs and IP addresses and ports) of a single media stream. The element MUST contain one or more elements. 4.3.1. The Element The element describes a specific media stream. It contains the media type, codecs and the hostname(s) or IP address(es) and port(s) of this stream. The hostname(s) or IP address(es) and port number(s) of a stream correspond to the ones listed in the session description(s). A UA that generates a element MUST insert the hostname/port found in the local session description for this media stream into the local-host-port element. The UA MUST insert the hostname/port of the remote session description into the remote-host-port element, if the remote session description is available to the UA. If not, the UA generates a stream element that only contains the local-host-port element. This element MAY have the following attributes (see Section 3.3): direction, label. The label attribute is used to identify a specific media stream in a Hilt, et al. Expires December 14, 2010 [Page 9] Internet-Draft Media Policy Dataset June 2010 session description. The value of the label attribute is a token. The token can be chosen freely, however, it MUST be unique among all element in a session-info document. If a label attribute [RFC4574] is present in the SDP description, its value MUST be carried over to the label attribute of the corresponding element. The element MUST contain one element, one or more elements and one element. The element MAY contain one element. 4.3.1.1. The Element The element contains the hostname or IP address and the port number of the media stream in the local session description. The hostname or IP address is separated from the port by a ":". An example is: "host.example.com:49562". The hostname or IP address of element is found in the c= element for the stream in the local SDP description. The port number is found in the m= element. 4.3.1.2. The Element The element is structured exactly as the element. However, it identifies the hostname or IP address and port number of the media stream in the remote session description. 4.4. The Element The element expresses a policy for routing a media stream through a media intermediary. The purpose of the element is to tell the UA to send a media stream through one (or a chain of) media intermediaries. Instead of sending the media directly to its final destination, the UA specifies a source route, which touches each intermediary and then reaches the final recipient. If there are N hops, including the final recipient, there needs to be a way for the media stream to specify N destinations. The element is a container that lists all media intermediaries to be traversed. Media intermediaries should be traversed in the order in which they appear in this list. The topmost entry should be traversed first, the last entry should be traversed last. Different types of intermediaries exist. These intermediaries are Hilt, et al. Expires December 14, 2010 [Page 10] Internet-Draft Media Policy Dataset June 2010 not necessarily interoperable and it may not be possible to chain them in an arbitrary order. A element SHOULD therefore only contain intermediary elements of the same type. This element MAY have the following attributes (see Section 3.3): direction. Multiple elements MAY only be present in a container if each applies to a different set of streams (e.g., one element for incoming and one for outgoing streams). The element MUST contain one or more elements defining a specific media intermediary, such as or . Note: it is not intended that the element replaces connectivity discovery mechanisms such as ICE. Instead of finding media relays that provide connectivity, this element defines a policy for media intermediaries that should be traversed. The set of intermediaries defined in the element and the ones discovered through ICE may overlap but don't have to. 4.4.1. The Element A fixed intermediary relies on pre-configured forwarding rules. The user agent simply sends media to the first media intermediary listed. It can assume that this media intermediary has been pre-configured with a forwarding rule for the media stream and knows where to forward the packets to. The configuration of forwarding rules in the intermediary must be done through other means. The contents of a element MUST be echoed to all policy servers that provide policies for a session. I.e., if multiple policy servers provide policies for the same session, this element needs to be forwarded to all of them, possibly in a second round of session-specific policy subscriptions as described in [I-D.ietf-sip-session-policy-framework] in section Contacting the Policy Server. The element MUST contain one element and MAY contain multiple optional elements. 4.4.1.1. The Element The element contains the hostname or IP address and port number of a media intermediary. The UA uses this hostname/IP address and port to send its media streams to the intermediary. The hostname or IP address is separated from the port by a ":". Hilt, et al. Expires December 14, 2010 [Page 11] Internet-Draft Media Policy Dataset June 2010 If a protocol uses multiple subsequent ports (e.g., RTP), the lowest port number SHOULD be included in the element. All additional port numbers SHOULD be identified in elements. 4.4.1.2. The Element If a protocol uses multiple subsequent ports (e.g., RTP), the lowest port number SHOULD be included in the element. All additional port numbers SHOULD be identified in elements. 4.4.2. The Element The TURN [RFC5766] protocol provides a mechanism for inserting a relay into the media path. Although the main purpose of TURN is NAT traversal, it is possible for a TURN relay to perform other media intermediary functionalities. The user agent establishes a binding on the TURN server and uses this binding to transmit and receive media. The element MUST contain one element and MAY contain multiple optional elements and zero or one each of the , , and elements. If no element is present, UDP is assumed. 4.4.2.1. The Element The element contains the shared secret needed to authenticate at the media intermediary. 4.4.2.2. The element The element contains the user ID needed to authenticate to the media intermediary. 4.4.2.3. The Element The element contains the name of the transport to be used for communicating with the TURN server. This document defines the values "tcp" and "udp" for use in the element. Other specifications may define additional values. 4.4.3. The Element The MSRP Relay Extensions [RFC4976] define a means for incorporating relays into the media path of an MSRP [RFC4975] session. MSRP is explicitly designed for a variety of purposes, including policy Hilt, et al. Expires December 14, 2010 [Page 12] Internet-Draft Media Policy Dataset June 2010 enforcement. The element MUST contain one element, and may contain zero or one each of the and elements. 4.4.3.1. The Element The element contains a URI that indicates the MSRP server to use for an intermediary. The UA uses this URI to authenticate with the MSRP relay, and then uses the URI it learns through that authentication process for any MSRP media it sends or receives. Only URIs with a scheme of "msrps:" are valid in the element. 5. Session Policy Documents Session policy documents describe a policy for SIP sessions. Session policy documents are independent of a specific session description and express general policies for SIP sessions. A session policy document is used to determine if a SIP session is policy conformant and to modify this session, if needed, according to the described policies. Session policy documents can be used to encode session-independent policies [I-D.ietf-sip-session-policy-framework]. In this usage, a policy server creates a session policy document and passes this document to a UA. The UA applies the policies defined to the SIP sessions it is establishing. For example, a session policy document can contain an element that prohibits the use of video. To set up a session that is compliant to this policy, a UA does not include the media type video in its SDP offer or answer. Session policy documents use the container. They use elements described in this section and common elements described in Section 6. 5.1. Merging Session Policies A UA may receive session policy documents from multiple sources, which need to be merged into a single session policy document the UA can work with. 5.1.1. Single Value Selection Properties that have a single value (e.g., the maximum bandwidth allowed) require that a common value is determined for this property during the merging process. The merging rules for determining this Hilt, et al. Expires December 14, 2010 [Page 13] Internet-Draft Media Policy Dataset June 2010 value need to be defined individually for each element in the schema definition (e.g., select the lowest maximum bandwidth). 5.1.2. Merging Sets The media-types-allowed, media-types-excluded, codecs-allowed and codecs-excluded are containers that contain a set of media-types/ codecs. The values defined in these containers need to be merged to determine the set of media-types/codecs that are permissible in a session. To merge the media-types-* and codecs-* containers a UA needs to apply all containers it has received one after the other the set of media-types/codecs it supports. After applying media-types-*/ codecs-* elements, the UA has the list of media-types/codecs that are allowed in a session. The containers can be applied in any order. However, each time a container is applied to the set of media-types/ codecs allowed, this set MUST stay the same or be reduced. Media- types/codecs cannot be added during this process. The following example illustrates the merging process for two data sets. In this example, the UA supports the following set of audio codecs: PCMA, PCMU and G729. After applying session policy document 1, the UA removes PCMA as it is disallowed by this policy. The remaining set of codecs is: PCMU and G729. Session policy document 2 disallows all codecs that are not listed. After applying this policy, the set of codecs allowed is: G729. Session Policy Document 1: audio/PCMA Session Policy Document 2: audio/PCMA audio/G729 It is possible that two session policy documents define non- overlapping sets of allowed media-types or codecs. The resulting merged set would be empty, which is illegal according to the schema definition of the media-types/codecs element. This constitutes a conflict that cannot be resolved automatically. If these properties are enforced by both networks, the UA will not be able to set up a session. Hilt, et al. Expires December 14, 2010 [Page 14] Internet-Draft Media Policy Dataset June 2010 The combined set of media-types/codecs MUST again be valid and well- formed according to the schema definitions. A conflict occurs if the combined property set is not a well-formed document after the merging process is completed. 5.1.3. Local Policy Server Selection Some properties require that only values from the local policy server are used. The local policy server is the policy server that is in the local domain of the user agent. If policy documents are delivered through the configuration framework [I-D.ietf-sipping-config-framework], the value received through a subscription using the "local-network" profile-type is used. Values received through other profile-type subscriptions are discarded. If policy documents are delivered through the session-specific policy mechanism [I-D.ietf-sip-session-policy-framework] the value received from the policy server identified by the Local Policy Server URI are used. Values received from other policy servers are discarded. 5.2. The Element The element describes a policy that applies to SIP sessions. The element MAY occur multiple times inside a element. The element MAY contain one optional and element and multiple (including zero) , , , , , , and elements as well as elements from other namespaces. The MPDF elements are defined in Section 6. 5.3. The Element The element is a container that is used to define the set of media types (e.g., audio, video) that are allowed in a session. All media types that are not listed in this container are not permitted in a session. A specific media type is allowed by adding the corresponding element to this container. This element MAY have the following attributes (see Section 3.3): direction, visibility. Multiple elements MAY only be present in a container element if each applies to a different set of streams (e.g., one element for incoming and one for Hilt, et al. Expires December 14, 2010 [Page 15] Internet-Draft Media Policy Dataset June 2010 outgoing streams). The element MUST contain one or more elements. A element MUST NOT be used in a container that contains a element. Merging of session-policy documents: containers are merged as described in "Merging Sets" Section 5.1.2. 5.4. The Element The element is a container that is used to define the set of media types (e.g., audio, video) that are not permitted in a session. All media types that are not listed in this container are allowed and can be used in a session. A specific media type is excluded from a session by adding the corresponding element to this container. This element MAY have the following attributes (see Section 3.3): direction, visibility. Multiple elements MAY only be present in a container element if each applies to a different set of streams (e.g., one element for incoming and one for outgoing streams). The element MUST contain one or more elements. A element MUST NOT be used in a container that contains a element. Merging of session-policy documents: containers are merged as described in "Merging Sets" Section 5.1.2. 5.5. The Element The element is a container that is used to define the set of codecs that may be used in a session. All codes not listed in the element are disallowed and MUST NOT be used in a session. A policy MUST allow the use of at least one codec per media type. A specific codec is allowed by adding the corresponding element to this container. The element MAY have the following attributes (see Section 3.3): direction, visibility. Multiple elements MAY only be present in a container Hilt, et al. Expires December 14, 2010 [Page 16] Internet-Draft Media Policy Dataset June 2010 element if each applies to a different set of streams (e.g., one element for incoming and one for outgoing streams). The element MUST contain one or more elements. A element MUST NOT be used in a container that contains a element. Merging of session-policy documents: containers are merged as described in "Merging Sets" Section 5.1.2. 5.6. The Element The element is a container that is used to define the set of codecs that are disallowed in a session. All codes not listed in the element are permitted and MAY be used in a session. A specific codec is disallowed by adding the corresponding element to this container. The element MAY have the following attributes (see Section 3.3): direction, visibility. Multiple elements MAY only be present in a container element if each applies to a different set of streams (e.g., one element for incoming and one for outgoing streams). The element MUST contain one or more elements. A element MUST NOT be used in a container that contains a element. Merging of session-policy documents: containers are merged as described in "Merging Sets" Section 5.1.2. 5.7. The Element Domains often require that a user agent only uses ports in a certain range for media streams. The element defines a policy for the ports a user agent can use for media. The value of this element consists of a start port and an end port separated by a "-". The start/end port is the first/last port that can be used. This element MAY have the following attributes (see Section 3.3): visibility. Merging of session-policy documents: the local domain of the user agent has precedence over other domains and its local ports value is used. During the merging process, element values Hilt, et al. Expires December 14, 2010 [Page 17] Internet-Draft Media Policy Dataset June 2010 from local policy server selected as described in "Local Policy Server Selection" Section 5.1.3 are used. 6. Common Media Policy Dataset Elements This section describes common XML elements that are used in session info and session policy documents to encode the media properties of SIP sessions. 6.1. The Element The element identifies a specific media type. The value of this element MUST be the name of a IANA registered media type (see RFC4566 [RFC4566]), such as 'audio', 'video', 'text', or 'application'. This element MAY have the following attribute (see Section 3.3): q. If used in a session policy document inside a element, the media types defined MAY be used in a session. If used in a session policy document inside a element, the media types defined MUST NOT be used in a session. 6.2. The Element The element identifies a specific codec. The content of this element MUST be a registered MIME type [RFC4855] using media type and subtype (e.g., audio/PCMA [RFC4856] or video/H263 [RFC4629]) and possibly additional registered MIME type parameters. The element MAY have the following attribute (see Section 3.3): q. If used in a session policy document inside a element, the codec defined MAY be used in a session. If used in a session policy document inside a element, the codec defined MUST NOT be used in a session. The element MUST contain one element and MAY contain multiple optional elements. 6.2.1. The Element The element contains a MIME type that identifies a codec. The value of this element MUST be a combination of a registered MIME media type and subtype [RFC4855] separated by a "/" (e.g., audio/ PCMA, audio/G726-16 [RFC4856] or video/H263 [RFC4629]). Hilt, et al. Expires December 14, 2010 [Page 18] Internet-Draft Media Policy Dataset June 2010 6.2.2. The Element The element may be needed for some codecs to identify a particular encoding or profile. The value of this element MUST be a name-value pair containing the name and the value of a registered MIME type parameter for the codec [RFC4855]. The name and value are separated by a "=". For example, the parameter "profile=0" can be used to specify a specific profile for the codec "video/ H263-2000" [RFC4629]. 6.3. The Element The element defines the overall maximum bandwidth in kilobits per second an entity can/will use for media streams at any point in time. It defines an upper limit for the total bandwidth an entity can/will use for the transmission of media streams. The limit corresponds to the sum of the maximum session bandwidth of all sessions a UA may set up in parallel. The bandwidth limit given in the element includes the bandwidth needed for lower-layer transport and network protocols (e.g., UDP and IP). The element MAY have the following attribute (see Section 3.3): direction. If used in a element, the element MAY have the following additional attribute (see Section 3.3): visibility. If the element occurs multiple times in a container element, each instance MUST apply to a different set of media streams (i.e., one element for outgoing and one for incoming streams). Merging of session-policy documents: the lowest max-bw value is used. 6.4. The Element The element defines the maximum bandwidth in kilobits per second an entity can/will use for media streams in the described session. It defines an upper limit for the total bandwidth of a single session. This limit corresponds to the sum of the maximum stream bandwidth of all media streams in a session. The bandwidth limit given in the element includes the bandwidth needed for lower-layer transport and network protocols (e.g., UDP and IP). Hilt, et al. Expires December 14, 2010 [Page 19] Internet-Draft Media Policy Dataset June 2010 The value of the element is equivalent to the CT bandwidth in the b= line of an SDP [RFC4566] announcement. The element MAY have the following attribute (see Section 3.3): direction. If used in a element, the element MAY have the following additional attribute (see Section 3.3): visibility. If the element occurs multiple times in a container element, each instance MUST apply to a different set of media streams (i.e., one element for outgoing and one for incoming streams). Merging of session-policy documents: the lowest max-session-bw value is used. 6.5. The Element The element defines the maximum bandwidth in kilobits per second an entity can/will use for each media stream in the described session. The bandwidth limit given in the element includes the bandwidth needed for lower-layer transport and network protocols (e.g., UDP and IP). The value of the element is equivalent to the AS bandwidth in the b= line of an SDP [RFC4566] announcement. The element MAY have the following attribute (see Section 3.3): direction, media-type. If used in a element, the element MAY have the following additional attribute (see Section 3.3): visibility. If used in a element, the element MAY have the following additional attribute: label. The media-type attribute is used to define that the element only applies to streams of a certain media type. For example, it may only apply to audio streams. The value of the 'media-type' attribute MUST be the name of a IANA registered media type (see RFC4566 [RFC4566]), such as 'audio', 'video', 'text', or 'application'. Hilt, et al. Expires December 14, 2010 [Page 20] Internet-Draft Media Policy Dataset June 2010 The label attribute is used to define a bandwidth limit for a specific media stream. The use of this attribute requires that the element that represents the media stream to which this bandwidth limit applies also has a label attribute. A element with a label attribute applies only to the stream element that has a label attribute with the same value. If no matching element exists, then the element MUST be ignored. If the element occurs multiple times in a container element, each instance MUST apply to a different set of media streams (i.e., one element for outgoing and one for incoming streams). Merging of session-policy documents: the lowest max-stream-bw value is used. 6.6. The Element The element contains an Differentiated Services Codepoint (DSCP) [RFC2474] value that should be used to populate the IP DS field of media packets. The contains an integer value that represents a 6 bit field and therefore ranges from 0 to 63. This element MAY have the following attributes (see Section 3.3): direction, media-type. If used in a element, the element MAY have the following additional attribute (see Section 3.3): visibility. The media-type attribute is used to define that element only applies to streams of a certain media type. For example, it may only apply to audio streams. The value of the 'media-type' attribute MUST be the name of a IANA registered media type (see RFC4566 [RFC4566]), such as 'audio', 'video', 'text', or 'application'. The element is optional and MAY occur multiple times inside a container. If the element occurs multiple times, each instance MUST apply to a different media stream (i.e., one element for audio and one for video streams). Merging of session-policy documents: the local domain of the user agent has precedence over other domains and its DSCP value is used. During the merging process, element values from local policy server selected as described in "Local Policy Server Selection" Section 5.1.3 are used. Hilt, et al. Expires December 14, 2010 [Page 21] Internet-Draft Media Policy Dataset June 2010 6.7. The Element The element provides context information about a session policy or session information document. The element MAY contain multiple and one element. If used in a element, the element MAY also contain a element. If used in a element, the element MAY also contain a and a element. Merging of session-policy documents: the element is not subject to merging. 6.7.1. The Element The element contains the URI of the policy server that has issued this policy. The element is only defined inside a element. 6.7.2. The Element The element contains a contact address (e.g., a SIP URI or email address) under which the issuer of this document can be reached. 6.7.3. The Element The element provides a short textual description of the policy or session that should be intelligible to the human user. 6.7.4. The Element The element identifies the request-URI the dialog initiating request of a session is sent to. The element is only defined inside a element. 6.7.5. The Element The element provides a mechanism for a policy server to return an opaque token to a UA. This is sometimes needed to ensure Hilt, et al. Expires December 14, 2010 [Page 22] Internet-Draft Media Policy Dataset June 2010 that all requests for a session are routed to the same policy server. The use of this token is described in the Framework for SIP Session Policies [I-D.ietf-sip-session-policy-framework]. The element is only defined inside a element. 6.8. Other Session Properties A number of additional elements have been proposed for a media property language. These elements are deemed to be outside the scope of this format. However, they may be defined in extensions of MPDF or other profile data sets. o maximum number of streams o maximum number of sessions o maximum number of streams per session o external address and port o media transport protocol o outbound proxy o SIP methods o SIP option tags o SIP transport protocol o body disposition o body format o body encryption 7. Examples 7.1. Session Policy Documents The following example describes a session policy document that allows the use of audio and video and prohibits the use of other media types. It allows the use of any codec except G.723 and G.729. Hilt, et al. Expires December 14, 2010 [Page 23] Internet-Draft Media Policy Dataset June 2010 policy@biloxi.example.com sip:policy_manager@example.com Access network policies audio video audio/G729 audio/G723 7.2. Session Information Documents The following examples contain session descriptions and the session information documents that represent these sessions. 7.2.1. Example 1 In this example, a session info document is created based on one session description. This session info document would be created, for example, by a UA that has composed an offer and is now contacting a policy server. Local SDP session description: v=0 o=alice 2890844526 2890844526 IN IP4 host.somewhere.example s= c=IN IP4 host.somewhere.example t=0 0 m=audio 49562 RTP/AVP 0 1 3 a=rtpmap:0 PCMU/8000 a=rtpmap:1 1016/8000 a=rtpmap:3 GSM/8000 m=video 51234 RTP/AVP 31 34 a=rtpmap:31 H261/90000 a=rtpmap:34 H263/90000 MPDF document: Hilt, et al. Expires December 14, 2010 [Page 24] Internet-Draft Media Policy Dataset June 2010 sip:alice@somewhere.example session information audio audio/PCMU audio/1016 audio/GSM host.somewhere.example:49562 video video/H261 video/H263 host.somewhere.example:51234 7.2.2. Example 2 In this example, a session info document is created that represents two session descriptions (i.e., an offer and answer). This session info document would be created, for example, by a UA that has received an answer from another UA and is now contacting a policy server. Local SDP session description: v=0 o=alice 2890844526 2890844526 IN IP4 host.somewhere.example s= c=IN IP4 host.somewhere.example t=0 0 m=audio 49562 RTP/AVP 0 1 3 a=rtpmap:0 PCMU/8000 a=rtpmap:1 1016/8000 a=rtpmap:3 GSM/8000 m=video 51234 RTP/AVP 31 34 a=rtpmap:31 H261/90000 a=rtpmap:34 H263/90000 Remote SDP session description: Hilt, et al. Expires December 14, 2010 [Page 25] Internet-Draft Media Policy Dataset June 2010 v=0 o=bob 2890844730 2890844730 IN IP4 host.anywhere.example s= c=IN IP4 host.anywhere.example t=0 0 m=audio 52124 RTP/AVP 0 3 a=rtpmap:0 PCMU/8000 a=rtpmap:3 GSM/8000 m=video 50286 RTP/AVP 31 a=rtpmap:31 H261/90000 MPDF document that represents the local and the remote session description: sip:alice@somewhere.example session information audio audio/PCMU audio/GSM host.somewhere.example:49562 host.anywhere.example:52124 video video/H261 host.somewhere.example:51234 host.anywhere.example:50286 The following MPDF document is a modified version of the above document, which can be returned by a policy server. This document reflects a policy that defines a maximum session bandwidth of 192 kbit and a maximum bandwidth for the H261 video stream of 128 kbit. Hilt, et al. Expires December 14, 2010 [Page 26] Internet-Draft Media Policy Dataset June 2010 sip:alice@somewhere.example modified session information audio audio/PCMU audio/GSM host.somewhere.example:49562 host.anywhere.example:52124 video video/H261 host.somewhere.example:51234 host.anywhere.example:50286 128 192 8. Relax NG Definition This section needs to be updated. ?xml version="1.0"?> Hilt, et al. Expires December 14, 2010 [Page 27] Internet-Draft Media Policy Dataset June 2010 Hilt, et al. Expires December 14, 2010 [Page 28] Internet-Draft Media Policy Dataset June 2010 Hilt, et al. Expires December 14, 2010 [Page 29] Internet-Draft Media Policy Dataset June 2010 Hilt, et al. Expires December 14, 2010 [Page 30] Internet-Draft Media Policy Dataset June 2010 Hilt, et al. Expires December 14, 2010 [Page 31] Internet-Draft Media Policy Dataset June 2010 Hilt, et al. Expires December 14, 2010 [Page 32] Internet-Draft Media Policy Dataset June 2010 Hilt, et al. Expires December 14, 2010 [Page 33] Internet-Draft Media Policy Dataset June 2010 9. Security Considerations Session policy information can be sensitive information. The protocol used to distribute session policy information SHOULD ensure privacy, message integrity and authentication. Furthermore, the protocol SHOULD provide access controls which restrict who can see who else's session policy information. 10. IANA Considerations This document registers a new MIME type, application/ media-policy-dataset+xml, and a new XML namespace. 10.1. MIME Registration MIME media type name: application MIME subtype name: media-policy-dataset+xml Mandatory parameters: none Optional parameters: Same as charset parameter application/xml as specified in RFC 3023 [RFC3023]. Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023 [RFC3023]. Security considerations: See Section 10 of RFC 3023 [RFC3023] and Section 9 of this specification. Interoperability considerations: none. Published specification: This document. Applications which use this media type: This document type has been used to convey media policy information between SIP user agents and a domain. Additional Information: Magic Number: None File Extension: .mpf or .xml Hilt, et al. Expires December 14, 2010 [Page 34] Internet-Draft Media Policy Dataset June 2010 Macintosh file type code: "TEXT" Personal and email address for further information: Volker Hilt, Intended usage: COMMON Author/Change controller: The IETF. 10.2. URN Sub-Namespace Registration This section registers a new XML namespace, as per the guidelines in [RFC3688] URI: The URI for this namespace is urn:ietf:params:xml:ns:mediadataset. Registrant Contact: IETF, SIPPING working group, , Volker Hilt, XML: BEGIN Media Policy Dataset Namespace

Namespace for Media Policy Datasets

urn:ietf:params:xml:ns:mediadataset

See RFCXXXX.

END 11. References 11.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Hilt, et al. Expires December 14, 2010 [Page 35] Internet-Draft Media Policy Dataset June 2010 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998. [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001. [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with Session Description Protocol (SDP)", RFC 3264, June 2002. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006. [RFC4574] Levin, O. and G. Camarillo, "The Session Description Protocol (SDP) Label Attribute", RFC 4574, August 2006. [RFC4855] Casner, S., "Media Type Registration of RTP Payload Formats", RFC 4855, February 2007. [RFC4975] Campbell, B., Mahy, R., and C. Jennings, "The Message Session Relay Protocol (MSRP)", RFC 4975, September 2007. [RFC4976] Jennings, C., Mahy, R., and A. Roach, "Relay Extensions for the Message Sessions Relay Protocol (MSRP)", RFC 4976, September 2007. [RFC5766] Mahy, R., Matthews, P., and J. Rosenberg, "Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)", RFC 5766, April 2010. [W3C.REC-xml-20040204] Yergeau, F., Maler, E., Bray, T., Paoli, J., and C. Sperberg-McQueen, "Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium FirstEdition REC-xml-20040204, February 2004, . [W3C.REC-xml-names-19990114] Hollander, D., Layman, A., and T. Bray, "Namespaces in XML", World Wide Web Consortium FirstEdition REC-xml- names-19990114, January 1999, Hilt, et al. Expires December 14, 2010 [Page 36] Internet-Draft Media Policy Dataset June 2010 . 11.2. Informative References [I-D.ietf-sip-session-policy-framework] Hilt, V., Camarillo, G., and J. Rosenberg, "A Framework for Session Initiation Protocol (SIP) Session Policies", draft-ietf-sip-session-policy-framework-07 (work in progress), February 2010. [I-D.ietf-sipping-config-framework] Channabasappa, S., "A Framework for Session Initiation Protocol User Agent Profile Delivery", draft-ietf-sipping-config-framework-17 (work in progress), February 2010. [RFC2648] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, August 1999. [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. [RFC4629] Ott, H., Bormann, C., Sullivan, G., Wenger, S., and R. Even, "RTP Payload Format for ITU-T Rec", RFC 4629, January 2007. [RFC4856] Casner, S., "Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences", RFC 4856, February 2007. Appendix A. Acknowledgements Many thanks to Allison Mankin, Dan Petrie, Martin Dolly, Adam Roach and Ben Campbell for the discussions and suggestions. Many thanks to Roni Even and Mary Barnes for reviewing the draft and to Jari Urpalainen for helping with the Relax NG schema. Hilt, et al. Expires December 14, 2010 [Page 37] Internet-Draft Media Policy Dataset June 2010 Authors' Addresses Volker Hilt Bell Labs/Alcatel-Lucent 791 Holmdel-Keyport Rd Holmdel, NJ 07733 USA Email: volkerh@bell-labs.com Dale R. Worley Nortel Networks Corp. 600 Technology Park Dr. Billerica, MA 01821 US Email: dworley@nortel.com Gonzalo Camarillo Ericsson Hirsalantie 11 Jorvas 02420 Finland Email: Gonzalo.Camarillo@ericsson.com Jonathan Rosenberg jdrosen.net Monmouth, NJ USA Email: jdrosen@jdrosen.net Hilt, et al. Expires December 14, 2010 [Page 38]