draft-ietf-mediactrl-mrb-17.txt   draft-ietf-mediactrl-mrb-18.txt 
Network Working Group C. Boulton Network Working Group C. Boulton
Internet-Draft NS-Technologies Internet-Draft NS-Technologies
Intended status: Standards Track L. Miniero Intended status: Standards Track L. Miniero
Expires: August 8, 2013 Meetecho Expires: August 9, 2013 Meetecho
G. Munson G. Munson
AT&T AT&T
February 4, 2013 February 5, 2013
Media Resource Brokering Media Resource Brokering
draft-ietf-mediactrl-mrb-17 draft-ietf-mediactrl-mrb-18
Abstract Abstract
The MediaCtrl work group in the IETF has proposed an architecture for The MediaCtrl work group in the IETF has proposed an architecture for
controlling media services. The Session Initiation Protocol (SIP) is controlling media services. The Session Initiation Protocol (SIP) is
used as the signalling protocol which provides many inherent used as the signalling protocol which provides many inherent
capabilities for message routing. In addition to such signalling capabilities for message routing. In addition to such signalling
properties, a need exists for intelligent, application level media properties, a need exists for intelligent, application level media
service selection based on non-static signalling properties. This is service selection based on non-static signalling properties. This is
especially true when considered in conjunction with deployment especially true when considered in conjunction with deployment
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 August 8, 2013. This Internet-Draft will expire on August 9, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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
skipping to change at page 2, line 32 skipping to change at page 2, line 32
4.1. Query MRB . . . . . . . . . . . . . . . . . . . . . . . 9 4.1. Query MRB . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1. Hybrid Query MRB . . . . . . . . . . . . . . . . . . 10 4.1.1. Hybrid Query MRB . . . . . . . . . . . . . . . . . . 10
4.2. In-Line MRB . . . . . . . . . . . . . . . . . . . . . . 11 4.2. In-Line MRB . . . . . . . . . . . . . . . . . . . . . . 11
5. MRB Interface Definitions . . . . . . . . . . . . . . . . . . 14 5. MRB Interface Definitions . . . . . . . . . . . . . . . . . . 14
5.1. Media Server Resource Publish Interface . . . . . . . . 14 5.1. Media Server Resource Publish Interface . . . . . . . . 14
5.1.1. Control Package Definition . . . . . . . . . . . . . 15 5.1.1. Control Package Definition . . . . . . . . . . . . . 15
5.1.2. Element Definitions . . . . . . . . . . . . . . . . . 16 5.1.2. Element Definitions . . . . . . . . . . . . . . . . . 16
5.1.3. <mrbrequest> . . . . . . . . . . . . . . . . . . . . 17 5.1.3. <mrbrequest> . . . . . . . . . . . . . . . . . . . . 17
5.1.4. <mrbresponse> . . . . . . . . . . . . . . . . . . . . 19 5.1.4. <mrbresponse> . . . . . . . . . . . . . . . . . . . . 19
5.1.5. <mrbnotification> . . . . . . . . . . . . . . . . . . 20 5.1.5. <mrbnotification> . . . . . . . . . . . . . . . . . . 20
5.2. Media Service Resource Consumer Interface . . . . . . . 32 5.2. Media Service Resource Consumer Interface . . . . . . . 31
5.2.1. Query Mode / HTTP Consumer Interface Usage . . . . . 32 5.2.1. Query Mode / HTTP Consumer Interface Usage . . . . . 32
5.2.2. In-Line Aware Mode / SIP Consumer Interface Usage . . 33 5.2.2. In-Line Aware Mode / SIP Consumer Interface Usage . . 32
5.2.3. Consumer Interface Lease Mechanism . . . . . . . . . 36 5.2.3. Consumer Interface Lease Mechanism . . . . . . . . . 36
5.2.4. <mrbconsumer> . . . . . . . . . . . . . . . . . . . . 39 5.2.4. <mrbconsumer> . . . . . . . . . . . . . . . . . . . . 38
5.2.5. Media Service Resource Request . . . . . . . . . . . 39 5.2.5. Media Service Resource Request . . . . . . . . . . . 39
5.2.6. Media Service Resource Response . . . . . . . . . . . 51 5.2.6. Media Service Resource Response . . . . . . . . . . . 50
5.3. In-Line Unaware MRB Interface . . . . . . . . . . . . . 54 5.3. In-Line Unaware MRB Interface . . . . . . . . . . . . . 53
6. MRB acting as a B2BUA . . . . . . . . . . . . . . . . . . . . 56 6. MRB acting as a B2BUA . . . . . . . . . . . . . . . . . . . . 55
7. Multi-modal MRB Implementations . . . . . . . . . . . . . . . 57 7. Multi-modal MRB Implementations . . . . . . . . . . . . . . . 56
8. Relative Merits of Query Mode, IAMM, and IUMM . . . . . . . . 58 8. Relative Merits of Query Mode, IAMM, and IUMM . . . . . . . . 57
9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 60 9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 59
9.1. Publish Example . . . . . . . . . . . . . . . . . . . . 60 9.1. Publish Example . . . . . . . . . . . . . . . . . . . . 59
9.2. Consumer Example . . . . . . . . . . . . . . . . . . . . 65 9.2. Consumer Example . . . . . . . . . . . . . . . . . . . . 64
9.2.1. Query Example . . . . . . . . . . . . . . . . . . . . 65 9.2.1. Query Example . . . . . . . . . . . . . . . . . . . . 64
9.2.2. IAMM Example . . . . . . . . . . . . . . . . . . . . 68 9.2.2. IAMM Example . . . . . . . . . . . . . . . . . . . . 67
10. Media Service Resource Publisher Interface XML Schema . . . . 84 10. Media Service Resource Publisher Interface XML Schema . . . . 83
11. Media Service Resource Consumer Interface XML Schema . . . . 107 11. Media Service Resource Consumer Interface XML Schema . . . . 106
12. Security Considerations . . . . . . . . . . . . . . . . . . . 128 12. Security Considerations . . . . . . . . . . . . . . . . . . . 127
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 131 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 130
13.1. Media Control Channel Framework Package Registration . . 131 13.1. Media Control Channel Framework Package Registration . . 130
13.2. application/mrb-publish+xml Media Type . . . . . . . . . 131 13.2. application/mrb-publish+xml Media Type . . . . . . . . . 130
13.3. application/mrb-consumer+xml Media Type . . . . . . . . 132 13.3. application/mrb-consumer+xml Media Type . . . . . . . . 131
13.4. URN Sub-Namespace Registration for mrb-publish . . . . . 133 13.4. URN Sub-Namespace Registration for mrb-publish . . . . . 132
13.5. URN Sub-Namespace Registration for mrb-consumer . . . . 133 13.5. URN Sub-Namespace Registration for mrb-consumer . . . . 132
13.6. XML Schema Registration for mrb-publish . . . . . . . . 133 13.6. XML Schema Registration for mrb-publish . . . . . . . . 132
13.7. XML Schema Registration for mrb-consumer . . . . . . . . 134 13.7. XML Schema Registration for mrb-consumer . . . . . . . . 133
14. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 14. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
14.1. Changes from 13 Version . . . . . . . . . . . . . . . . 135 14.1. Changes from 13 Version . . . . . . . . . . . . . . . . 134
14.2. Changes from 12 Version . . . . . . . . . . . . . . . . 135 14.2. Changes from 12 Version . . . . . . . . . . . . . . . . 134
14.3. Changes from 11 Version . . . . . . . . . . . . . . . . 135 14.3. Changes from 11 Version . . . . . . . . . . . . . . . . 134
14.4. Changes from 10 Version . . . . . . . . . . . . . . . . 135 14.4. Changes from 10 Version . . . . . . . . . . . . . . . . 134
14.5. Changes from 09 Version . . . . . . . . . . . . . . . . 136 14.5. Changes from 09 Version . . . . . . . . . . . . . . . . 135
14.6. Changes from 08 Version . . . . . . . . . . . . . . . . 136 14.6. Changes from 08 Version . . . . . . . . . . . . . . . . 135
14.7. Changes from 07 Version . . . . . . . . . . . . . . . . 136 14.7. Changes from 07 Version . . . . . . . . . . . . . . . . 135
14.8. Changes from 06 Version . . . . . . . . . . . . . . . . 137 14.8. Changes from 06 Version . . . . . . . . . . . . . . . . 136
14.9. Changes from 05 Version . . . . . . . . . . . . . . . . 137 14.9. Changes from 05 Version . . . . . . . . . . . . . . . . 136
14.10. Changes from 04 Version . . . . . . . . . . . . . . . . 137 14.10. Changes from 04 Version . . . . . . . . . . . . . . . . 136
14.11. Changes from 03 Version . . . . . . . . . . . . . . . . 137 14.11. Changes from 03 Version . . . . . . . . . . . . . . . . 136
14.12. Changes from 02 Version . . . . . . . . . . . . . . . . 138 14.12. Changes from 02 Version . . . . . . . . . . . . . . . . 137
14.13. Changes from 01 Version . . . . . . . . . . . . . . . . 138 14.13. Changes from 01 Version . . . . . . . . . . . . . . . . 137
14.14. Changes from 00 Version . . . . . . . . . . . . . . . . 138 14.14. Changes from 00 Version . . . . . . . . . . . . . . . . 137
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 139 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 138
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 140 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 139
16.1. Normative References . . . . . . . . . . . . . . . . . . 140 16.1. Normative References . . . . . . . . . . . . . . . . . . 139
16.2. Informative References . . . . . . . . . . . . . . . . . 141 16.2. Informative References . . . . . . . . . . . . . . . . . 140
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 143 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 142
1. Introduction 1. Introduction
As IP based multimedia infrastructures mature, the complexity and As IP based multimedia infrastructures mature, the complexity and
demands from deployments increase. Such complexity will result in a demands from deployments increase. Such complexity will result in a
wide variety of capabilities from a range of vendors that should all wide variety of capabilities from a range of vendors that should all
be interoperable using the architecture and protocols produced by the be interoperable using the architecture and protocols produced by the
MediaCtrl work group. It should be possible for a controlling entity MediaCtrl work group. It should be possible for a controlling entity
to be assisted in Media Server selection so that the most appropriate to be assisted in Media Server selection so that the most appropriate
resource is selected for a particular operation. The importance resource is selected for a particular operation. The importance
skipping to change at page 31, line 42 skipping to change at page 31, line 42
5.1.5.21. <encryption> 5.1.5.21. <encryption>
The <encryption> element allows a Media Server to declare support for The <encryption> element allows a Media Server to declare support for
encrypting RTP media streams using RFC 3711 [RFC3711]. The element encrypting RTP media streams using RFC 3711 [RFC3711]. The element
MAY be present. If the element is present, then the Media Server MAY be present. If the element is present, then the Media Server
supports DTLS-SRTP [RFC5763]. supports DTLS-SRTP [RFC5763].
The <encryption> element has no attributes. The <encryption> element has no attributes.
The <encryption> element has zero or more of the following child The <encryption> element has no child elements.
elements:
<keying-mechanism>: has no attributes. The element provides the
name of a keying mechanism the Media Server supports for
encrypting RTP media streams.
The presence of at least one <keying-mechanism> child element would
indicate that the Media Server does support RTP media stream
encryption as specified by the child element itself. An empty
<encryption> element would otherwise indicate the Media Server does
not support RTP encryption at all.
5.2. Media Service Resource Consumer Interface 5.2. Media Service Resource Consumer Interface
The Media Server Consumer interface provides the ability for clients The Media Server Consumer interface provides the ability for clients
of an MRB, such as Application Servers, to request an appropriate of an MRB, such as Application Servers, to request an appropriate
Media Server to satisfy specific criteria. The interface allows a Media Server to satisfy specific criteria. The interface allows a
client to pass detailed meta-information to the MRB to help select an client to pass detailed meta-information to the MRB to help select an
appropriate Media Server. The MRB is then able to make an informed appropriate Media Server. The MRB is then able to make an informed
decision and provide the client with an appropriate media server decision and provide the client with an appropriate media server
resource. The MRB Consumer interface includes both 1) In-Line Aware resource. The MRB Consumer interface includes both 1) In-Line Aware
skipping to change at page 45, line 35 skipping to change at page 45, line 22
5.2.5.1.2.8. <encryption> 5.2.5.1.2.8. <encryption>
The <encryption> element allows a Consumer client to request support The <encryption> element allows a Consumer client to request support
for encrypting RTP media streams using RFC 3711 [RFC3711]. The for encrypting RTP media streams using RFC 3711 [RFC3711]. The
element MAY be present. If the element is present, then the Media element MAY be present. If the element is present, then the Media
Server supports DTLS-SRTP [RFC5763]. Server supports DTLS-SRTP [RFC5763].
The <encryption> element has no attributes. The <encryption> element has no attributes.
The <encryption> element has zero or more of the following child The <encryption> element has no child elements:
elements:
<keying-mechanism>: has no attributes. The element provides the
name of a keying mechanism the Client requires for encrypting RTP
media streams.
The presence of at least one <keying-mechanism> child element would
indicate that the Consumer client does request RTP media stream
encryption as specified by the child element itself. An empty
<encryption> element would otherwise indicate the Consumer client
does not require RTP encryption at all.
5.2.5.1.2.9. <application-data> 5.2.5.1.2.9. <application-data>
The <application-data> element provides an arbitrary string of The <application-data> element provides an arbitrary string of
characters as IVR application level data. This data is meant to only characters as IVR application level data. This data is meant to only
have meaning at the application level logic and as such is not have meaning at the application level logic and as such is not
otherwise restricted by this specification. The set of allowed otherwise restricted by this specification. The set of allowed
characters are the same as those in XML (viz., tab, carriage return, characters are the same as those in XML (viz., tab, carriage return,
line feed, and the legal characters of Unicode and ISO/IEC 10646 [see line feed, and the legal characters of Unicode and ISO/IEC 10646 [see
http://www.w3.org/TR/xml/ section 2.2]). The element MAY be present. http://www.w3.org/TR/xml/ section 2.2]). The element MAY be present.
skipping to change at page 51, line 20 skipping to change at page 50, line 45
5.2.5.1.3.8. <encryption> 5.2.5.1.3.8. <encryption>
The <encryption> element allows a Consumer client to request support The <encryption> element allows a Consumer client to request support
for encrypting mixed RTP media streams using RFC 3711 [RFC3711]. The for encrypting mixed RTP media streams using RFC 3711 [RFC3711]. The
element MAY be present. If the element is present, then the Media element MAY be present. If the element is present, then the Media
Server supports DTLS-SRTP [RFC5763]. Server supports DTLS-SRTP [RFC5763].
The <encryption> element has no attributes. The <encryption> element has no attributes.
The <encryption> element has zero or more of the following child The <encryption> element has no child elements.
elements:
<keying-mechanism>: has no attributes. The element provides the
name of a keying mechanism the Consumer client requires for
encrypting mixed RTP media streams.
The presence of at least one <keying-mechanism> child element would
indicate that the Consumer client does require mixed RTP media stream
encryption as specified by the child element itself. An empty
<encryption> element would otherwise indicate the client does not
require RTP encryption at all.
5.2.6. Media Service Resource Response 5.2.6. Media Service Resource Response
This section provides the element definitions for use in Consumer This section provides the element definitions for use in Consumer
interface responses. The responses are carried in the interface responses. The responses are carried in the
<mediaResourceResponse> element. <mediaResourceResponse> element.
5.2.6.1. <mediaResourceResponse> element 5.2.6.1. <mediaResourceResponse> element
The <mediaResourceResponse> element provides information for clients The <mediaResourceResponse> element provides information for clients
skipping to change at page 65, line 24 skipping to change at page 64, line 24
<A3>Napoli</A3> <A3>Napoli</A3>
<A6>Via Claudio</A6> <A6>Via Claudio</A6>
<HNO>21</HNO> <HNO>21</HNO>
<LMK>University of Napoli Federico II</LMK> <LMK>University of Napoli Federico II</LMK>
<NAM>Dipartimento di Informatica e Sistemistica</NAM> <NAM>Dipartimento di Informatica e Sistemistica</NAM>
<PC>80210</PC> <PC>80210</PC>
</civicAddress> </civicAddress>
</media-server-location> </media-server-location>
<label>TestbedPrototype-01</label> <label>TestbedPrototype-01</label>
<media-server-address>sip:MS1@ms.example.net</media-server-address> <media-server-address>sip:MS1@ms.example.net</media-server-address>
<encryption> <encryption/>
<keying-mechanism>DTLS-SRTP</keying-mechanism>
</encryption>
</mrbnotification> </mrbnotification>
</mrbpublish> </mrbpublish>
B2. MRB -> MS (200 to CONTROL) B2. MRB -> MS (200 to CONTROL)
------------------------------ ------------------------------
CFW 03fff52e7b7a 200 CFW 03fff52e7b7a 200
9.2. Consumer Example 9.2. Consumer Example
As specified in Section 5.2, the Consumer interface can be involved As specified in Section 5.2, the Consumer interface can be involved
skipping to change at page 104, line 11 skipping to change at page 103, line 11
<!-- media-server-address --> <!-- media-server-address -->
<xsd:element name="media-server-address" type="xsd:anyURI" /> <xsd:element name="media-server-address" type="xsd:anyURI" />
<!-- encryption --> <!-- encryption -->
<xsd:complexType name="encryptionType"> <xsd:complexType name="encryptionType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:element ref="keying-mechanism"
minOccurs="0" maxOccurs="unbounded" />
<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:anyAttribute namespace="##other" processContents="lax" /> <xsd:anyAttribute namespace="##other" processContents="lax" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="encryption" type="encryptionType" /> <xsd:element name="encryption" type="encryptionType" />
<xsd:element name="keying-mechanism" type="keying.datatype" />
<!-- <!--
#################################################### ####################################################
DATATYPES DATATYPES
#################################################### ####################################################
--> -->
<xsd:simpleType name="version.datatype"> <xsd:simpleType name="version.datatype">
<xsd:restriction base="xsd:NMTOKEN"> <xsd:restriction base="xsd:NMTOKEN">
skipping to change at page 106, line 4 skipping to change at page 104, line 49
</xsd:restriction> </xsd:restriction>
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="vxml.datatype"> <xsd:simpleType name="vxml.datatype">
<xsd:restriction base="xsd:NMTOKEN"/> <xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="label.datatype"> <xsd:simpleType name="label.datatype">
<xsd:restriction base="xsd:NMTOKEN" /> <xsd:restriction base="xsd:NMTOKEN" />
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="subscriptionid.datatype">
<xsd:restriction base="xsd:NMTOKEN" />
</xsd:simpleType>
<xsd:simpleType name="keying.datatype"> <xsd:simpleType name="subscriptionid.datatype">
<xsd:restriction base="xsd:NMTOKEN" /> <xsd:restriction base="xsd:NMTOKEN" />
</xsd:simpleType> </xsd:simpleType>
</xsd:schema> </xsd:schema>
Figure 13 Figure 13
11. Media Service Resource Consumer Interface XML Schema 11. Media Service Resource Consumer Interface XML Schema
This section gives the XML Schema Definition [W3C.REC-xmlschema-1- This section gives the XML Schema Definition [W3C.REC-xmlschema-1-
skipping to change at page 122, line 10 skipping to change at page 121, line 10
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="location" type="locationType" /> <xsd:element name="location" type="locationType" />
<!-- encryption --> <!-- encryption -->
<xsd:complexType name="encryptionType"> <xsd:complexType name="encryptionType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
<xsd:element ref="keying-mechanism"
minOccurs="0" maxOccurs="unbounded" />
<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:anyAttribute namespace="##other" processContents="lax" /> <xsd:anyAttribute namespace="##other" processContents="lax" />
</xsd:extension> </xsd:extension>
</xsd:complexContent> </xsd:complexContent>
</xsd:complexType> </xsd:complexType>
<xsd:element name="encryption" type="encryptionType" /> <xsd:element name="encryption" type="encryptionType" />
<xsd:element name="keying-mechanism" type="keying.datatype" />
<!-- application-data --> <!-- application-data -->
<xsd:element name="application-data" type="appdata.datatype" /> <xsd:element name="application-data" type="appdata.datatype" />
<!-- max-prepared-duration --> <!-- max-prepared-duration -->
<xsd:complexType name="max-prepared-durationType"> <xsd:complexType name="max-prepared-durationType">
<xsd:complexContent> <xsd:complexContent>
<xsd:extension base="Tcore"> <xsd:extension base="Tcore">
<xsd:sequence> <xsd:sequence>
skipping to change at page 127, line 30 skipping to change at page 126, line 27
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="vxml.datatype"> <xsd:simpleType name="vxml.datatype">
<xsd:restriction base="xsd:NMTOKEN"/> <xsd:restriction base="xsd:NMTOKEN"/>
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="appdata.datatype"> <xsd:simpleType name="appdata.datatype">
<xsd:restriction base="xsd:string" /> <xsd:restriction base="xsd:string" />
</xsd:simpleType> </xsd:simpleType>
<xsd:simpleType name="keying.datatype">
<xsd:restriction base="xsd:NMTOKEN" />
</xsd:simpleType>
</xsd:schema> </xsd:schema>
Figure 14 Figure 14
12. Security Considerations 12. Security Considerations
The MRB network entity has two primary interfaces, Publish and The MRB network entity has two primary interfaces, Publish and
Consumer, that carry sensitive information and must therefore be Consumer, that carry sensitive information and must therefore be
appropriately protected and secured. appropriately protected and secured.
skipping to change at page 141, line 18 skipping to change at page 140, line 18
(SRTP) Security Context Using Datagram Transport Layer (SRTP) Security Context Using Datagram Transport Layer
Security (DTLS)", RFC 5763, May 2010. Security (DTLS)", RFC 5763, May 2010.
[W3C.CR-wsdl20-20051215] [W3C.CR-wsdl20-20051215]
Chinnici, R., Moreau, J., Ryman, A., and S. Weerawarana, Chinnici, R., Moreau, J., Ryman, A., and S. Weerawarana,
"Web Services Description Language (WSDL) Version 2.0 Part "Web Services Description Language (WSDL) Version 2.0 Part
1: Core Language", W3C CR CR-wsdl20-20051215, 1: Core Language", W3C CR CR-wsdl20-20051215,
December 2005. December 2005.
[W3C.REC-soap12-part1-20030624] [W3C.REC-soap12-part1-20030624]
Gudgin, M., Mendelsohn, N., Nielsen, H., Moreau, J., and Gudgin, M., Mendelsohn, N., Hadley, M., Nielsen, H., and
M. Hadley, "SOAP Version 1.2 Part 1: Messaging Framework", J. Moreau, "SOAP Version 1.2 Part 1: Messaging Framework",
World Wide Web Consortium FirstEdition REC-soap12-part1- World Wide Web Consortium FirstEdition REC-soap12-part1-
20030624, June 2003, 20030624, June 2003,
<http://www.w3.org/TR/2003/REC-soap12-part1-20030624>. <http://www.w3.org/TR/2003/REC-soap12-part1-20030624>.
[W3C.REC-soap12-part2-20030624] [W3C.REC-soap12-part2-20030624]
Hadley, M., Mendelsohn, N., Gudgin, M., Moreau, J., and H. Hadley, M., Mendelsohn, N., Nielsen, H., Moreau, J., and
Nielsen, "SOAP Version 1.2 Part 2: Adjuncts", World Wide M. Gudgin, "SOAP Version 1.2 Part 2: Adjuncts", World Wide
Web Consortium FirstEdition REC-soap12-part2-20030624, Web Consortium FirstEdition REC-soap12-part2-20030624,
June 2003, June 2003,
<http://www.w3.org/TR/2003/REC-soap12-part2-20030624>. <http://www.w3.org/TR/2003/REC-soap12-part2-20030624>.
16.2. Informative References 16.2. Informative References
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network [RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network
Media Services with SIP", RFC 4240, December 2005. Media Services with SIP", RFC 4240, December 2005.
 End of changes. 21 change blocks. 
107 lines changed or deleted 57 lines changed or added

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