draft-ietf-mediactrl-mixer-control-package-12.txt   draft-ietf-mediactrl-mixer-control-package-13.txt 
Network Working Group S. McGlashan Network Working Group S. McGlashan
Internet-Draft Hewlett-Packard Internet-Draft Hewlett-Packard
Intended status: Standards Track T. Melanchuk Intended status: Standards Track T. Melanchuk
Expires: May 15, 2011 Rain Willow Communications Expires: July 8, 2011 Rain Willow Communications
C. Boulton C. Boulton
NS-Technologies NS-Technologies
November 11, 2010 January 4, 2011
A Mixer Control Package for the Media Control Channel Framework A Mixer Control Package for the Media Control Channel Framework
draft-ietf-mediactrl-mixer-control-package-12 draft-ietf-mediactrl-mixer-control-package-13
Abstract Abstract
This document defines a Media Control Channel Framework Package for This document defines a Media Control Channel Framework Package for
managing mixers for media conferences and connections. The package managing mixers for media conferences and connections. The package
defines request elements for managing conference mixers, managing defines request elements for managing conference mixers, managing
mixers between conferences and/or connections, as well as associated mixers between conferences and/or connections, as well as associated
responses and notifications. The package also defines elements for responses and notifications. The package also defines elements for
auditing package capabilities and mixers. auditing package capabilities and mixers.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 15, 2011. This Internet-Draft will expire on July 8, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 11, line 34 skipping to change at page 11, line 34
an MS implementation receives a <mscmixer> element containing an MS implementation receives a <mscmixer> element containing
attributes or elements from another namespace which it does not attributes or elements from another namespace which it does not
support, the MS sends a 428 response (Section 4.6). support, the MS sends a 428 response (Section 4.6).
Extensible attributes and elements are not described in this section. Extensible attributes and elements are not described in this section.
In all other cases where there is a difference in constraints between In all other cases where there is a difference in constraints between
the XML schema and the textual description of elements in this the XML schema and the textual description of elements in this
section, the textual definition takes priority. section, the textual definition takes priority.
Some elements in this control package contain attributes whose value Some elements in this control package contain attributes whose value
is descriptive text. Since the descriptive text is for diagnostic is descriptive text primarily for diagnostic use. The implementation
use only, and is neither a protocol element nor intended for user can indicated the language used in the descriptive text by means of a
display, the descriptive text does not require a language indicator 'desclang' attribute ([RFC2277]). The desclang attribute can appear
such as a language tag ([RFC2277]) and thus does not carry one. on the root element as well as selected subordinate elements (see
These comprise: the reason attribute on <response> (Section 4.2.3), Section 4.1). The desclang attribute value on the root element
<unjoin-notify> (Section 4.2.4.2), <conferenceexit> (Section 4.2.4.3) applies to all desclang attributes in subordinate elements unless the
and <auditresponse> (Section 4.3.2). subordinate element has an explicit desclang attribute which
overrides it.
Usage examples are provided in Section 6. Usage examples are provided in Section 6.
4.1. <mscmixer> 4.1. <mscmixer>
The <mscmixer> element has the following attributes (in addition to The <mscmixer> element has the following attributes (in addition to
standard XML namespace attributes such as xmlns): standard XML namespace attributes such as xmlns):
version: a string specifying the mscmixer package version. The version: a string specifying the mscmixer package version. The
value is fixed as '1.0' for this version of the package. The value is fixed as '1.0' for this version of the package. The
attribute is mandatory. attribute is mandatory.
desclang: specifies the language used in descriptive text attributes
of subordinate elements (unless the subordinate element provides a
desclang attribute which overrides the value for its descriptive
text attributes). The descriptive text attributes on subordinate
elements include: the reason attribute on <response>
(Section 4.2.3), <unjoin-notify> (Section 4.2.4.2),
<conferenceexit> (Section 4.2.4.3) and <auditresponse>
(Section 4.3.2). A valid value is a language identifier
(Section 4.7.7). The attribute is optional. The default value is
i-default (BCP47 [RFC5646]).
The <mscmixer> element has the following defined child elements, only The <mscmixer> element has the following defined child elements, only
one of which can occur: one of which can occur:
1. mixer management elements defined in Section 4.2: 1. mixer management elements defined in Section 4.2:
<createconference> create and configure a new conference mixer. <createconference> create and configure a new conference mixer.
See Section 4.2.1.1 See Section 4.2.1.1
<modifyconference> modify the configuration of an existing <modifyconference> modify the configuration of an existing
conference mixer. See Section 4.2.1.2 conference mixer. See Section 4.2.1.2
skipping to change at page 12, line 49 skipping to change at page 13, line 19
For example, a request to the MS to create a conference mixer: For example, a request to the MS to create a conference mixer:
<mscmixer version="1.0" xmlns="urn:ietf:params:xml:ns:msc-mixer"> <mscmixer version="1.0" xmlns="urn:ietf:params:xml:ns:msc-mixer">
<createconference/> <createconference/>
</mscmixer> </mscmixer>
and a response from the MS that the conference was successfully and a response from the MS that the conference was successfully
created: created:
<mscmixer version="1.0" xmlns="urn:ietf:params:xml:ns:msc-mixer"> <mscmixer version="1.0" xmlns="urn:ietf:params:xml:ns:msc-mixer"
<response status="200" conferenceid="conference1"/> desclang="en">
<response status="200" conferenceid="conference1"
reason="conference created"/>
</mscmixer> </mscmixer>
4.2. Mixer Elements 4.2. Mixer Elements
This section defines the mixer management XML elements for this This section defines the mixer management XML elements for this
control package. These elements are divided into requests, responses control package. These elements are divided into requests, responses
and notifications. and notifications.
Request elements are sent to the MS to request a specific mixer Request elements are sent to the MS to request a specific mixer
operation to be executed. The following request elements are operation to be executed. The following request elements are
skipping to change at page 40, line 34 skipping to change at page 40, line 34
Responses to requests are indicated by a <response> element. Responses to requests are indicated by a <response> element.
The <response> element has following attributes: The <response> element has following attributes:
status: numeric code indicating the response status. Valid values status: numeric code indicating the response status. Valid values
are defined in Section 4.6. The attribute is mandatory. are defined in Section 4.6. The attribute is mandatory.
reason: string specifying a reason for the response status. The reason: string specifying a reason for the response status. The
attribute is optional. attribute is optional.
desclang: specifies the language used in the value of the the reason
attribute. A valid value is a language identifier
(Section 4.7.7). The attribute is optional. If not specified,
the value of the desclang attribute on <mscmixer> (Section 4.1)
applies.
conferenceid: string identifying the conference (see Section 16.1 of conferenceid: string identifying the conference (see Section 16.1 of
[I-D.ietf-mediactrl-sip-control-framework]). The attribute is [I-D.ietf-mediactrl-sip-control-framework]). The attribute is
optional. optional.
connectionid: string identifying the SIP dialog connection (see connectionid: string identifying the SIP dialog connection (see
Section 16.1 of [I-D.ietf-mediactrl-sip-control-framework]). The Section 16.1 of [I-D.ietf-mediactrl-sip-control-framework]). The
attribute is optional. attribute is optional.
For example, a response when a conference was created successfully: For example, a response when a conference was created successfully:
skipping to change at page 42, line 38 skipping to change at page 42, line 46
where new status codes are assigned using the Standards Action where new status codes are assigned using the Standards Action
process defined in [RFC5226]. The AS MUST treat any status code process defined in [RFC5226]. The AS MUST treat any status code
it does not recognize as being equivalent to 1 (join execution it does not recognize as being equivalent to 1 (join execution
error). The attribute is mandatory. error). The attribute is mandatory.
reason: a textual description providing a reason for the status reason: a textual description providing a reason for the status
code; e.g. details about an error. A valid value is a string (see code; e.g. details about an error. A valid value is a string (see
Section 4.7.4). The attribute is optional. There is no default Section 4.7.4). The attribute is optional. There is no default
value. value.
desclang: specifies the language used in the value of the the reason
attribute. A valid value is a language identifier
(Section 4.7.7). The attribute is optional. If not specified,
the value of the desclang attribute on <mscmixer> (Section 4.1)
applies.
id1: an identifier for either a connection or a conference. The id1: an identifier for either a connection or a conference. The
identifier MUST conform to the syntax defined in Section 16.1 of identifier MUST conform to the syntax defined in Section 16.1 of
[I-D.ietf-mediactrl-sip-control-framework] The attribute is [I-D.ietf-mediactrl-sip-control-framework] The attribute is
mandatory. mandatory.
id2: an identifier for either a connection or a conference. The id2: an identifier for either a connection or a conference. The
identifier MUST conform to the syntax defined in Section 16.1 of identifier MUST conform to the syntax defined in Section 16.1 of
[I-D.ietf-mediactrl-sip-control-framework] The attribute is [I-D.ietf-mediactrl-sip-control-framework] The attribute is
mandatory. mandatory.
skipping to change at page 43, line 41 skipping to change at page 44, line 5
where new status codes are assigned using the Standards Action where new status codes are assigned using the Standards Action
process defined in [RFC5226]. The AS MUST treat any status code process defined in [RFC5226]. The AS MUST treat any status code
it does not recognize as being equivalent to 1 (conference it does not recognize as being equivalent to 1 (conference
execution error). The attribute is mandatory. execution error). The attribute is mandatory.
reason: a textual description providing a reason for the status reason: a textual description providing a reason for the status
code; e.g. details about an error. A valid value is a string (see code; e.g. details about an error. A valid value is a string (see
Section 4.7.4). The attribute is optional. There is no default Section 4.7.4). The attribute is optional. There is no default
value. value.
desclang: specifies the language used in the value of the the reason
attribute. A valid value is a language identifier
(Section 4.7.7). The attribute is optional. If not specified,
the value of the desclang attribute on <mscmixer> (Section 4.1)
applies.
The <conferenceexit> element has no child elements. The <conferenceexit> element has no child elements.
When a MS sends a <conferenceexit> event, the identifier for the When a MS sends a <conferenceexit> event, the identifier for the
conference (conferenceid attribute) is no longer valid on the MS and conference (conferenceid attribute) is no longer valid on the MS and
can be reused for another conference. can be reused for another conference.
For example, the following notification event would be sent from the For example, the following notification event would be sent from the
MS when the conference with identifier "conference99" exits due to a MS when the conference with identifier "conference99" exits due to a
successful <destroyconference/>: successful <destroyconference/>:
skipping to change at page 46, line 18 skipping to change at page 46, line 29
request. request.
The <auditresponse> element has the following attributes: The <auditresponse> element has the following attributes:
status: numeric code indicating the audit response status. The status: numeric code indicating the audit response status. The
attribute is mandatory. Valid values are defined in Section 4.6. attribute is mandatory. Valid values are defined in Section 4.6.
reason: string specifying a reason for the status. The attribute is reason: string specifying a reason for the status. The attribute is
optional. optional.
desclang: specifies the language used in the value of the the reason
attribute. A valid value is a language identifier
(Section 4.7.7). The attribute is optional. If not specified,
the value of the desclang attribute on <mscmixer> (Section 4.1)
applies.
The <auditresponse> element has the following sequence of child The <auditresponse> element has the following sequence of child
elements: elements:
<capabilities> element (Section 4.3.2.1) describing capabilities of <capabilities> element (Section 4.3.2.1) describing capabilities of
the package. The element is optional. the package. The element is optional.
<mixers> element (Section 4.3.2.2) describing information about <mixers> element (Section 4.3.2.2) describing information about
managed mixers. The element is optional. managed mixers. The element is optional.
For example, a successful response to a <audit> request requesting For example, a successful response to a <audit> request requesting
skipping to change at page 58, line 29 skipping to change at page 58, line 29
The time unit identifiers are: "ms" (milliseconds) and "s" (seconds). The time unit identifiers are: "ms" (milliseconds) and "s" (seconds).
Examples include: "3s", "850ms", "0.7s", ".5s" and "+1.5s". Examples include: "3s", "850ms", "0.7s", ".5s" and "+1.5s".
4.7.6. MIME Media Type 4.7.6. MIME Media Type
A string formated as an IANA MIME media type ([MIME.mediatypes]). A string formated as an IANA MIME media type ([MIME.mediatypes]).
The ABNF ([RFC5234]) production for the string is: The ABNF ([RFC5234]) production for the string is:
type-name "/" subtype-name *(";" parameter-name) type-name "/" subtype-name *(";" parameter)
where "type-name" and "subtype-name" are defined in Section 4.2, and parameter = parameter-name "=" value
"parameter-name" in Section 4.3, of [RFC4288].
where "type-name" and "subtype-name" are defined in Section 4.2 of
[RFC4288], "parameter-name" is defined in Section 4.3 of [RFC4288]
and "value" is defined in Section 5.1 of [RFC2045].
4.7.7. Language Identifier
A language identifier labels information content as being of a
particular human language variant. Following the XML specification
for language identification [XML], a legal language identifier is
identified by a RFC5646 ([RFC5646]) and RFC4647 ([RFC4647]) code
where the language code is required and a country code or other
subtag identifier is optional.
5. Formal Syntax 5. Formal Syntax
This section defines the XML schema for the Mixer Control Package. This section defines the XML schema for the Mixer Control Package.
The schema is normative. The schema is normative.
The schema defines datatypes, attributes, and mixer elements in the The schema defines datatypes, attributes, and mixer elements in the
urn:ietf:params:xml:ns:msc-mixer namespace. In most elements the urn:ietf:params:xml:ns:msc-mixer namespace. In most elements the
order of child elements is significant. The schema is extensible: order of child elements is significant. The schema is extensible:
elements allow attributes and child elements from other namespaces. elements allow attributes and child elements from other namespaces.
skipping to change at page 59, line 31 skipping to change at page 59, line 31
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="urn:ietf:params:xml:ns:msc-mixer" <xsd:schema targetNamespace="urn:ietf:params:xml:ns:msc-mixer"
xmlns:fw="urn:ietf:params:xml:ns:control:framework-attributes" xmlns:fw="urn:ietf:params:xml:ns:control:framework-attributes"
elementFormDefault="qualified" elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="urn:ietf:params:xml:ns:msc-mixer" xmlns="urn:ietf:params:xml:ns:msc-mixer"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation> <xsd:annotation>
<xsd:documentation> <xsd:documentation>
IETF MediaCtrl Mixer 1.0 (20101020) IETF MediaCtrl Mixer 1.0 (20110104)
This is the schema of the Mixer control package. It This is the schema of the Mixer control package. It
defines request, response and notification elements for defines request, response and notification elements for
mixing. mixing.
The schema namespace is urn:ietf:params:xml:ns:msc-mixer The schema namespace is urn:ietf:params:xml:ns:msc-mixer
</xsd:documentation> </xsd:documentation>
</xsd:annotation> </xsd:annotation>
skipping to change at page 61, line 17 skipping to change at page 61, line 17
<xsd:element ref="response" /> <xsd:element ref="response" />
<xsd:element ref="event" /> <xsd:element ref="event" />
<xsd:element ref="audit" /> <xsd:element ref="audit" />
<xsd:element ref="auditresponse" /> <xsd:element ref="auditresponse" />
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:choice> </xsd:choice>
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="version" type="version.datatype" <xsd:attribute name="version" type="version.datatype"
use="required" /> use="required" />
<xsd:attribute name="desclang" type="xsd:language"
default="i-default" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="mscmixer" type="mscmixerType" /> <xsd:element name="mscmixer" type="mscmixerType" />
<!-- <!--
##################################################### #####################################################
CONFERENCE MANAGEMENT TYPES CONFERENCE MANAGEMENT TYPES
skipping to change at page 66, line 9 skipping to change at page 66, line 11
<xsd:complexType name="unjoinnotifyType"> <xsd:complexType name="unjoinnotifyType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="status" type="xsd:nonNegativeInteger" <xsd:attribute name="status" type="xsd:nonNegativeInteger"
use="required" /> use="required" />
<xsd:attribute name="reason" type="xsd:string" /> <xsd:attribute name="reason" type="xsd:string" />
<xsd:attribute name="desclang" type="xsd:language"/>
<xsd:attribute name="id1" type="xsd:string" <xsd:attribute name="id1" type="xsd:string"
use="required" /> use="required" />
<xsd:attribute name="id2" type="xsd:string" <xsd:attribute name="id2" type="xsd:string"
use="required" /> use="required" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="unjoin-notify" type="unjoinnotifyType" /> <xsd:element name="unjoin-notify" type="unjoinnotifyType" />
skipping to change at page 66, line 33 skipping to change at page 66, line 36
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="conferenceid" type="xsd:string" <xsd:attribute name="conferenceid" type="xsd:string"
use="required" /> use="required" />
<xsd:attribute name="status" <xsd:attribute name="status"
type="xsd:nonNegativeInteger" use="required" /> type="xsd:nonNegativeInteger" use="required" />
<xsd:attribute name="reason" type="xsd:string" /> <xsd:attribute name="reason" type="xsd:string" />
<xsd:attribute name="desclang" type="xsd:language"/>
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="conferenceexit" type="conferenceexitType" /> <xsd:element name="conferenceexit" type="conferenceexitType" />
<xsd:complexType name="responseType"> <xsd:complexType name="responseType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
skipping to change at page 67, line 4 skipping to change at page 67, line 8
<xsd:complexType name="responseType"> <xsd:complexType name="responseType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="status" type="status.datatype" <xsd:attribute name="status" type="status.datatype"
use="required" /> use="required" />
<xsd:attribute name="reason" type="xsd:string" /> <xsd:attribute name="reason" type="xsd:string" />
<xsd:attribute name="desclang" type="xsd:language"/>
<xsd:attributeGroup ref="fw:framework-attributes" /> <xsd:attributeGroup ref="fw:framework-attributes" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="response" type="responseType" /> <xsd:element name="response" type="responseType" />
<xsd:complexType name="subscribeType"> <xsd:complexType name="subscribeType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
skipping to change at page 71, line 45 skipping to change at page 71, line 49
<xsd:element ref="capabilities" minOccurs="0" <xsd:element ref="capabilities" minOccurs="0"
maxOccurs="1" /> maxOccurs="1" />
<xsd:element ref="mixers" minOccurs="0" <xsd:element ref="mixers" minOccurs="0"
maxOccurs="1" /> maxOccurs="1" />
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
</xsd:sequence> </xsd:sequence>
<xsd:attribute name="status" type="status.datatype" <xsd:attribute name="status" type="status.datatype"
use="required" /> use="required" />
<xsd:attribute name="reason" type="xsd:string" /> <xsd:attribute name="reason" type="xsd:string" />
<xsd:attribute name="desclang" type="xsd:language"/>
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="auditresponse" type="auditresponseType" /> <xsd:element name="auditresponse" type="auditresponseType" />
<!-- mixers --> <!-- mixers -->
<xsd:complexType name="mixersType"> <xsd:complexType name="mixersType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:element ref="conferenceaudit" minOccurs="0" <xsd:element ref="conferenceaudit" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
<xsd:element ref="joinaudit" minOccurs="0" <xsd:element ref="joinaudit" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
<xsd:any namespace="##other" minOccurs="0" <xsd:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax" /> maxOccurs="unbounded" processContents="lax" />
skipping to change at page 75, line 41 skipping to change at page 75, line 48
</xsd:complexType> </xsd:complexType>
<xsd:element name="params" type="paramsType" /> <xsd:element name="params" type="paramsType" />
<!-- param --> <!-- param -->
<!-- doesn't extend tCore since its content model is mixed --> <!-- doesn't extend tCore since its content model is mixed -->
<xsd:complexType name="paramType" mixed="true"> <xsd:complexType name="paramType" mixed="true">
<xsd:sequence/> <xsd:sequence/>
<xsd:attribute name="name" type="xsd:string" use="required" /> <xsd:attribute name="name" type="xsd:string" use="required" />
<xsd:attribute name="type" type="mime.datatype" <xsd:attribute name="type" type="mime.datatype"
default="text/plain" /> default="text/plain" />
<xsd:attribute name="encoding" type="xsd:string"/> <xsd:attribute name="encoding" type="xsd:string"/>
</xsd:complexType> </xsd:complexType>
<xsd:element name="param" type="paramType" /> <xsd:element name="param" type="paramType" />
<!-- <!--
#################################################### ####################################################
DATATYPES DATATYPES
#################################################### ####################################################
--> -->
<xsd:simpleType name="version.datatype"> <xsd:simpleType name="version.datatype">
<xsd:restriction base="xsd:NMTOKEN"> <xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="1.0" /> <xsd:enumeration value="1.0" />
</xsd:restriction> </xsd:restriction>
</xsd:simpleType> </xsd:simpleType>
skipping to change at page 91, line 9 skipping to change at page 91, line 9
Person & email address to contact for further information: Scott Person & email address to contact for further information: Scott
McGlashan <smcg.stds01@mcglashan.org> McGlashan <smcg.stds01@mcglashan.org>
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author/Change controller: The IETF Author/Change controller: The IETF
Other information: None. Other information: None.
9. Change Summary 9. Change Summary
Note to RFC Editor: Please remove this whole section. Note to RFC Editor: Please remove this whole section.
The following are the changes between the -13 and -12 versions
(addressing remaining IESG DISCUSS):
o 4.0, 4.1, etc: Added language tags to identify the language of
descriptive text attributes. A desclang attribute is added to the
root element and has a default value of i-default. Subordinate
elements with descriptive text attributes also have this attribute
defined - if it is not specified on the subordinate element, then
the desclang value on the root element applies. Added example of
desclang in 4.1.
o 5: Updated schema with desclang attributes
o Section 4.7.6: Corrected ABNF definition of IANA MIME media type
to allow parameter values.
The following are the changes between the -12 and -11 versions The following are the changes between the -12 and -11 versions
(primarily addressing IESG DISCUSS, comments and nits): (primarily addressing IESG DISCUSS, comments and nits):
o Introduction: Clarified that Control Framework is an equivalent o Introduction: Clarified that Control Framework is an equivalent
term for the Media Control Channel Framework. term for the Media Control Channel Framework.
o 4.2.4.2, 4.2.4.3, 4.5: Replaced reference to standards-tracks RFC o 4.2.4.2, 4.2.4.3, 4.5: Replaced reference to standards-tracks RFC
for assignment of new values, with reference to using Standards for assignment of new values, with reference to using Standards
Action process defined in RFC 5226. Action process defined in RFC 5226.
skipping to change at page 102, line 18 skipping to change at page 102, line 18
[I-D.ietf-mediactrl-sip-control-framework] [I-D.ietf-mediactrl-sip-control-framework]
Boulton, C., Melanchuk, T., and S. McGlashan, "Media Boulton, C., Melanchuk, T., and S. McGlashan, "Media
Control Channel Framework", Control Channel Framework",
draft-ietf-mediactrl-sip-control-framework-12 (work in draft-ietf-mediactrl-sip-control-framework-12 (work in
progress), September 2010. progress), September 2010.
[I-D.ietf-xcon-common-data-model] [I-D.ietf-xcon-common-data-model]
Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen, Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen,
"Conference Information Data Model for Centralized "Conference Information Data Model for Centralized
Conferencing (XCON)", draft-ietf-xcon-common-data-model-20 Conferencing (XCON)", draft-ietf-xcon-common-data-model-22
(work in progress), October 2010. (work in progress), December 2010.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996. Bodies", RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001. Types", RFC 3023, January 2001.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", BCP 13, RFC 4288, December 2005. Registration Procedures", BCP 13, RFC 4288, December 2005.
[RFC4574] Levin, O. and G. Camarillo, "The Session Description [RFC4574] Levin, O. and G. Camarillo, "The Session Description
Protocol (SDP) Label Attribute", RFC 4574, August 2006. Protocol (SDP) Label Attribute", RFC 4574, August 2006.
[RFC4647] Phillips, A. and M. Davis, "Matching of Language Tags",
BCP 47, RFC 4647, September 2006.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C M., Maler, E., [XML] Bray, T., Paoli, J., Sperberg-McQueen, C M., Maler, E.,
and F. Yergeau, "Extensible Markup Language (XML) 1.0 and F. Yergeau, "Extensible Markup Language (XML) 1.0
(Third Edition)", W3C Recommendation, February 2004. (Third Edition)", W3C Recommendation, February 2004.
[XMLSchema:Part2] [XMLSchema:Part2]
Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes Biron, P. and A. Malhotra, "XML Schema Part 2: Datatypes
Second Edition", W3C Recommendation, October 2004. Second Edition", W3C Recommendation, October 2004.
12.2. Informative References 12.2. Informative References
 End of changes. 30 change blocks. 
23 lines changed or deleted 102 lines changed or added

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