draft-ietf-mediactrl-mrb-04.txt   draft-ietf-mediactrl-mrb-05.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: October 1, 2010 University of Napoli Expires: November 15, 2010 University of Napoli
March 30, 2010 May 14, 2010
Media Resource Brokering Media Resource Brokering
draft-ietf-mediactrl-mrb-04 draft-ietf-mediactrl-mrb-05
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
architectures that include 1:M and M:N combinations of Application architectures that include 1:M and M:N combinations of Application
Servers and Media Servers. This document introduces a Media Resource Servers and Media Servers. This document introduces a Media Resource
Broker (MRB) entity which manages the availability of Media Servers Broker (MRB) entity which manages the availability of Media Servers
and the media resource demands of Application Servers. The document and the media resource demands of Application Servers. The document
includes potential deployment options for an MRB and appropriate includes potential deployment options for an MRB and appropriate
interfaces to Application Servers and Media Servers. interfaces to Application Servers and Media Servers.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on November 15, 2010.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 1, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 7 2. Conventions and Terminology . . . . . . . . . . . . . . . . . 7
3. Problem Discussion . . . . . . . . . . . . . . . . . . . . . 8 3. Problem Discussion . . . . . . . . . . . . . . . . . . . . . 8
4. Deployment Scenario Options . . . . . . . . . . . . . . . . . 9 4. Deployment Scenario Options . . . . . . . . . . . . . . . . . 9
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
skipping to change at page 3, line 14 skipping to change at page 3, line 9
9. Security Considerations . . . . . . . . . . . . . . . . . . . 109 9. Security Considerations . . . . . . . . . . . . . . . . . . . 109
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 110 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 110
10.1. Control Package Registration . . . . . . . . . . . . . . 110 10.1. Control Package Registration . . . . . . . . . . . . . . 110
10.2. application/mrb-publish+xml MIME Type . . . . . . . . . . 110 10.2. application/mrb-publish+xml MIME Type . . . . . . . . . . 110
10.3. application/mrb-consumer+xml MIME Type . . . . . . . . . 111 10.3. application/mrb-consumer+xml MIME Type . . . . . . . . . 111
10.4. URN Sub-Namespace Registration for mrb-publish . . . . . 112 10.4. URN Sub-Namespace Registration for mrb-publish . . . . . 112
10.5. URN Sub-Namespace Registration for mrb-consumer . . . . . 112 10.5. URN Sub-Namespace Registration for mrb-consumer . . . . . 112
10.6. XML Schema Registration for mrb-publish . . . . . . . . . 112 10.6. XML Schema Registration for mrb-publish . . . . . . . . . 112
10.7. XML Schema Registration for mrb-consumer . . . . . . . . 112 10.7. XML Schema Registration for mrb-consumer . . . . . . . . 112
11. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 11. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
11.1. Changes from 03 Version . . . . . . . . . . . . . . . . . 114 11.1. Changes from 04 Version . . . . . . . . . . . . . . . . . 114
11.2. Changes from 02 Version . . . . . . . . . . . . . . . . . 114 11.2. Changes from 03 Version . . . . . . . . . . . . . . . . . 114
11.3. Changes from 01 Version . . . . . . . . . . . . . . . . . 114 11.3. Changes from 02 Version . . . . . . . . . . . . . . . . . 114
11.4. Changes from 00 Version . . . . . . . . . . . . . . . . . 115 11.4. Changes from 01 Version . . . . . . . . . . . . . . . . . 115
11.5. Changes from 00 Version . . . . . . . . . . . . . . . . . 115
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 116 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 116
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 117 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 117
13.1. Normative References . . . . . . . . . . . . . . . . . . 117 13.1. Normative References . . . . . . . . . . . . . . . . . . 117
13.2. Informative References . . . . . . . . . . . . . . . . . 118 13.2. Informative References . . . . . . . . . . . . . . . . . 118
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 120 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 120
1. Introduction 1. Introduction
The topic of Media Resource management has been in discussion for a The topic of Media Resource management has been in discussion for a
number of years with varying proprietary solutions being used today. number of years with varying proprietary solutions being used today.
skipping to change at page 32, line 41 skipping to change at page 32, line 41
o A SIP ACK to the 2xx class response will then be sent back to the o A SIP ACK to the 2xx class response will then be sent back to the
MRB. MRB.
5.2.3. Consumer Interface Lease Mechanism 5.2.3. Consumer Interface Lease Mechanism
The Consumer interface defined in Section 5.2 and Section 8 allows a The Consumer interface defined in Section 5.2 and Section 8 allows a
client to request an appropriate media resource based on information client to request an appropriate media resource based on information
included in the request (either a HTTP POST or SIP INVITE message). included in the request (either a HTTP POST or SIP INVITE message).
In case of success, the response that is returned to the client MUST In case of success, the response that is returned to the client MUST
contain a <session-info> element in either the SIP 2xx class or HTTP contain a <session-info> element in either the SIP 2xx class or HTTP
200 response. The information contained in the <session-info> 200 response. The information contained in the <response-session-
element allows a Consumer client to monitor the life time of the info> element allows a Consumer client to monitor the life time of
resources it has successfully requested, as well as amending them. the resources it has successfully requested, as well as amending
them.
Before delving into the details of such lease mechanism, though, it's Before delving into the details of such lease mechanism, though, it's
worthwhile to first clarify its role within the context of the worthwhile to first clarify its role within the context of the
Consumer interface. As explained in Section 5.1, the knowledge the Consumer interface. As explained in Section 5.1, the knowledge the
MRB has of the resources of all the MS it handles is imperfect. As MRB has of the resources of all the MS it handles is imperfect. As
such, how an MRB actually manages such resources depends on how it is such, how an MRB actually manages such resources depends on how it is
implemented: one may choose to have the MRB keeping track and state implemented: one may choose to have the MRB keeping track and state
of the allocated resources, or simply depend on the MS themselves to of the allocated resources, or simply depend on the MS themselves to
provide the information by means of the publishing interface provide the information by means of the publishing interface
notifications. Further information may be inferred by the notifications. Further information may be inferred by the
signalling, in case the MRB is in the path of call legs. This means signalling, in case the MRB is in the path of call legs. This means
that the MRB may or may not be able to enforce the leasing mechanism that the MRB may or may not be able to enforce the leasing mechanism
it provides: such functionality is demanded, if necessary, to the it provides: such functionality is demanded, if necessary, to the
actual deployment of a compliant entity, with the help of the actual deployment of a compliant entity, with the help of the
information herein provided. information herein provided.
That said, the <mediaResourceResponse> element returned from the MRB That said, the <mediaResourceResponse> element returned from the MRB
contains a <session-info> element if the request is successful. The contains a <response-session-info> element if the request is
<session-info> element has the following child elements which provide successful. The <response-session-info> element has the following
the appropriate resource session information: child elements which provide the appropriate resource session
information:
o <session-id> is a unique identifier that enables a Consumer client o <session-id> is a unique identifier that enables a Consumer client
and MRB to correlate future media resource requests related to an and MRB to correlate future media resource requests related to an
initial media resource request. The <session-id> MUST be included initial media resource request. The <session-id> MUST be included
in all future related requests (see <session-id> use later in this in all future related requests (see <session-id> use later in this
section when constructing a subsequent request). section when constructing a subsequent request).
o <seq> is a numeric value returned to the Consumer client. On o <seq> is a numeric value returned to the Consumer client. On
issuing any future requests related to the media resource session issuing any future requests related to the media resource session
(as determined by the <session-id> element) the consumer client (as determined by the <session-id> element) the consumer client
MUST increment the value returned in the <seq> element and include MUST increment the value returned in the <seq> element and include
in the request (see <seq> use later in this section when in the request (see <seq> use later in this section when
constructing a subsequent request). constructing a subsequent request).
o <expires> provide a value which represents the number of seconds o <expires> provides a value which represents the number of seconds
the request for media resources is deemed alive. The Consumer the request for media resources is deemed alive. The Consumer
client should issue a refresh of the request, as discussed later client should issue a refresh of the request, as discussed later
in this section, if the expires timer is due to fire and the media in this section, if the expires timer is due to fire and the media
resources are still required. resources are still required.
o <media-server-address> provides a value which represents the SIP
URI where the assigned MS can be contacted to make use of the
required media resources.
The <mediaResourceRequest> element is used in subsequent Consumer The <mediaResourceRequest> element is used in subsequent Consumer
interface requests if the client wishes to manipulate the session. interface requests if the client wishes to manipulate the session.
The Consumer client MUST include the <session-info> element which The Consumer client MUST include the <session-info> element which
enables the receiving MRB to determine an existing media resource enables the receiving MRB to determine an existing media resource
allocation session. The <session-info> element has the following allocation session. The <session-info> element has the following
child elements which provide the appropriate resource session child elements which provide the appropriate resource session
information to the MRB: information to the MRB:
o <session-id> is a unique identifier that allows a Consumer client o <session-id> is a unique identifier that allows a Consumer client
to indicate the appropriate existing media resource session to be to indicate the appropriate existing media resource session to be
skipping to change at page 36, line 8 skipping to change at page 36, line 13
element, <session-info> and <packages>. element, <session-info> and <packages>.
5.2.4.1.1.1. <session-info> element 5.2.4.1.1.1. <session-info> element
The <session-info> element is included in Consumer requests when an The <session-info> element is included in Consumer requests when an
update is being made to an existing media resource session. The update is being made to an existing media resource session. The
ability to change and remove an existing media resource session is ability to change and remove an existing media resource session is
described in more detail in Section 5.2.3. The element MAY be described in more detail in Section 5.2.3. The element MAY be
present. present.
The <max-prepared-duration> element has no attributes. The <session-info> element has no attributes.
The <max-prepared-duration> element has the following child elements: The <session-info> element has the following child elements:
session-id: is a unique identifier that explicitly references an session-id: is a unique identifier that explicitly references an
existing media resource session on the MRB. The identifier is existing media resource session on the MRB. The identifier is
included to update the existing session and is described in more included to update the existing session and is described in more
detail in Section 5.2.3. detail in Section 5.2.3.
seq: is used in association with the <session-id> element in a seq: is used in association with the <session-id> element in a
subsequent request to update an existing media resource session on subsequent request to update an existing media resource session on
an MRB. The <seq> number is incremented from its original value an MRB. The <seq> number is incremented from its original value
returned in response to the initial request for media resources. returned in response to the initial request for media resources.
skipping to change at page 47, line 44 skipping to change at page 47, line 44
Section 5.2.3, where the leasing mechanism, together with its related Section 5.2.3, where the leasing mechanism, together with its related
scenarios, is described. scenarios, is described.
The <mediaResourceResponse> element only has <response-session-info> The <mediaResourceResponse> element only has <response-session-info>
as a child element. This element is used to describe the response of as a child element. This element is used to describe the response of
a Consumer interface query and is covered in the following sub- a Consumer interface query and is covered in the following sub-
section. section.
5.2.5.1.1. <response-session-info> element 5.2.5.1.1. <response-session-info> element
The <response-session-info> element is included in Consumer responses The <response-session-info> element is included in Consumer
when an update has been made to an existing media resource session. responses. This applies to responses to both requests for new
resources and requests to update an existing media resource session.
The ability to change and remove an existing media resource session The ability to change and remove an existing media resource session
is described in more detail in Section 5.2.3. The element MAY be is described in more detail in Section 5.2.3. The element MAY be
present. present: specifically, the element MUST be included in case the
request was successful, while it would not appear otherwise (e.g., in
case the request ended up with an error).
The <max-prepared-duration> element has no attributes. The <response-session-info> element has no attributes.
The <max-prepared-duration> element has the following child elements: The <response-session-info> element has the following child elements:
session-id: is a unique identifier that explicitly references an session-id: is a unique identifier that explicitly references an
existing media resource session on the MRB. The identifier is existing media resource session on the MRB. The identifier is
included to update the existing session and is described in more included to update the existing session and is described in more
detail in Section 5.2.3. detail in Section 5.2.3.
seq: is used in association with the <session-id> element in a seq: is used in association with the <session-id> element in a
subsequent request to update an existing media resource session on subsequent request to update an existing media resource session on
an MRB. The <seq> number is incremented from its original value an MRB. The <seq> number is incremented from its original value
returned in response to the initial request for media resources. returned in response to the initial request for media resources.
skipping to change at page 58, line 14 skipping to change at page 58, line 14
1. the Consumer request (1), in a <mediaResourceRequest> (HTTP POST, 1. the Consumer request (1), in a <mediaResourceRequest> (HTTP POST,
Content-Type 'application/mrb-consumer+xml'); Content-Type 'application/mrb-consumer+xml');
2. the Consumer response (2), in an <mediaResourceResponse> (HTTP 2. the Consumer response (2), in an <mediaResourceResponse> (HTTP
200 OK, Content-Type 'application/mrb-consumer+xml'). 200 OK, Content-Type 'application/mrb-consumer+xml').
1. AS -> MRB (HTTP POST, Consumer request) 1. AS -> MRB (HTTP POST, Consumer request)
------------------------------------------ ------------------------------------------
POST /Mrb/Consumer HTTP/1.1 POST /Mrb/Consumer HTTP/1.1
Content-Length: 1008 Content-Length: 870
Content-Type: application/mrb-consumer+xml Content-Type: application/mrb-consumer+xml
Host: mrb.example.net:8080 Host: mrb.example.net:8080
Connection: Keep-Alive Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.0.1 (java 1.5) User-Agent: Apache-HttpClient/4.0.1 (java 1.5)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<mrbconsumer version="1.0" xmlns="urn:ietf:params:xml:ns:mrb-consumer"> <mrbconsumer version="1.0" xmlns="urn:ietf:params:xml:ns:mrb-consumer">
<mediaResourceRequest> <mediaResourceRequest>
<generalInfo> <generalInfo>
<session-info>
<session-id>0GX1jCYZ8WBa</session-id>
<seq>1</seq>
</session-info>
<packages> <packages>
<package>msc-ivr/1.0</package> <package>msc-ivr/1.0</package>
<package>msc-mixer/1.0</package> <package>msc-mixer/1.0</package>
</packages> </packages>
</generalInfo> </generalInfo>
<ivrInfo> <ivrInfo>
<ivr-sessions> <ivr-sessions>
<rtp-codec name="audio/basic"> <rtp-codec name="audio/basic">
<decoding>10</decoding> <decoding>10</decoding>
<encoding>10</encoding> <encoding>10</encoding>
skipping to change at page 62, line 48 skipping to change at page 62, line 48
s=MediaCtrl s=MediaCtrl
c=IN IP4 as.example.com c=IN IP4 as.example.com
t=0 0 t=0 0
m=application 48035 TCP cfw m=application 48035 TCP cfw
a=connection:new a=connection:new
a=setup:active a=setup:active
a=cfw-id:vF0zD4xzUAW9 a=cfw-id:vF0zD4xzUAW9
a=ctrl-package:msc-mixer/1.0 a=ctrl-package:msc-mixer/1.0
a=ctrl-package:msc-ivr/1.0 a=ctrl-package:msc-ivr/1.0
------=_Part_0_19138361.1261662356915 =_Part
Content-Type: application/mrb-consumer+xml Content-Type: application/mrb-consumer+xml
<mrbconsumer version="1.0" \ <mrbconsumer version="1.0" \
xmlns="urn:ietf:params:xml:ns:mrb-consumer"> xmlns="urn:ietf:params:xml:ns:mrb-consumer">
<mediaResourceRequest> <mediaResourceRequest>
<generalInfo> <generalInfo>
<session-info>
<session-id>q79OYY0q4M6M</session-id>
<seq>1</seq>
</session-info>
<packages> <packages>
<package>msc-ivr/1.0</package> <package>msc-ivr/1.0</package>
<package>msc-mixer/1.0</package> <package>msc-mixer/1.0</package>
</packages> </packages>
</generalInfo> </generalInfo>
<ivrInfo> <ivrInfo>
<ivr-sessions> <ivr-sessions>
<rtp-codec name="audio/basic"> <rtp-codec name="audio/basic">
<decoding>10</decoding> <decoding>10</decoding>
<encoding>10</encoding> <encoding>10</encoding>
skipping to change at page 65, line 4 skipping to change at page 64, line 45
c=IN IP4 ms.example.net c=IN IP4 ms.example.net
t=0 0 t=0 0
m=application 7575 TCP cfw m=application 7575 TCP cfw
a=connection:new a=connection:new
a=setup:passive a=setup:passive
a=cfw-id:vF0zD4xzUAW9 a=cfw-id:vF0zD4xzUAW9
a=ctrl-package:msc-mixer/1.0 a=ctrl-package:msc-mixer/1.0
a=ctrl-package:msc-ivr/1.0 a=ctrl-package:msc-ivr/1.0
a=ctrl-package:mrb-publish/1.0 a=ctrl-package:mrb-publish/1.0
a=ctrl-package:msc-example-pkg/1.0 a=ctrl-package:msc-example-pkg/1.0
------=_Part_1_3022359.1261662358037
=_Part
Content-Type: application/mrb-consumer+xml Content-Type: application/mrb-consumer+xml
<mrbconsumer version="1.0" \ <mrbconsumer version="1.0" \
xmlns="urn:ietf:params:xml:ns:mrb-consumer"> xmlns="urn:ietf:params:xml:ns:mrb-consumer">
<mediaResourceResponse reason="Resource found" status="200"> <mediaResourceResponse reason="Resource found" status="200">
<response-session-info> <response-session-info>
<session-id>q79OYY0q4M6M</session-id> <session-id>q79OYY0q4M6M</session-id>
<seq>1</seq> <seq>1</seq>
<expires>3600</expires> <expires>3600</expires>
<media-server-address> <media-server-address>
sip:MediaServer@ms.example.net sip:MediaServer@ms.example.net
</media-server-address> </media-server-address>
</response-session-info> </response-session-info>
</mediaResourceResponse> </mediaResourceResponse>
skipping to change at page 114, line 9 skipping to change at page 114, line 9
Filename: mbr-consumer Filename: mbr-consumer
Registrant Contact: IETF, MEDIACTRL working group Registrant Contact: IETF, MEDIACTRL working group
(mediactrl@ietf.org) (mediactrl@ietf.org)
Schema: The XML for the schema is in Section 8 of this document. Schema: The XML for the schema is in Section 8 of this document.
11. Changes 11. Changes
Note to RFC Editor: Please remove this whole section. Note to RFC Editor: Please remove this whole section.
11.1. Changes from 03 Version 11.1. Changes from 04 Version
o Corrected some typos and leftovers in both 'session-info' and
'response-session-info' definitions.
o Clarified that 'response-session-info' is not only included in
reply to updates, but also to new requests; besides, clarified
that it is an optional element, in the sense that it is mandatory
in successful responses (200), while not needed otherwise (any
error).
o Corrected the Query example flow which included a 'session'info'
in a new request.
11.2. Changes from 03 Version
o Addressed comments per the Expert RAI Review by Ben Campbell. o Addressed comments per the Expert RAI Review by Ben Campbell.
o Several editorial changes (fixes, typos, nits). o Several editorial changes (fixes, typos, nits).
o Removed the 3xx class responses for the IAMM, per discussion in o Removed the 3xx class responses for the IAMM, per discussion in
Anaheim (feature had been added in the -02 version). Anaheim (feature had been added in the -02 version).
o Clarified that backslashes and XML indentation in the Examples are o Clarified that backslashes and XML indentation in the Examples are
only provided for readability. only provided for readability.
skipping to change at page 114, line 34 skipping to change at page 114, line 48
responses, in order to clarify when they are involved. responses, in order to clarify when they are involved.
o Added some text to better clarify the role of leasing in the o Added some text to better clarify the role of leasing in the
Consumer interface. Consumer interface.
o Added additional IANA considerations, that were missing in the o Added additional IANA considerations, that were missing in the
previous versions of the document. previous versions of the document.
o Added text to the security considerations. o Added text to the security considerations.
11.2. Changes from 02 Version 11.3. Changes from 02 Version
o Added examples in Section 6. o Added examples in Section 6.
o Fixed some nits in the schemas (encryption and required mixed=true o Fixed some nits in the schemas (encryption and required mixed=true
elements). elements).
o Completed review nit review comments from Gary Munson. o Completed review nit review comments from Gary Munson.
11.3. Changes from 01 Version 11.4. Changes from 01 Version
o Added description of lease mechanism. o Added description of lease mechanism.
o Added specific HTTP and SIP usage of Consumer interface. o Added specific HTTP and SIP usage of Consumer interface.
o Completed Publish interface schema + associated text. o Completed Publish interface schema + associated text.
o Included Consumer interface schema + associated text. o Included Consumer interface schema + associated text.
o Included supported-packages element. o Included supported-packages element.
skipping to change at page 115, line 17 skipping to change at page 115, line 32
o Removed announce-var element from doc. o Removed announce-var element from doc.
o Expanded Abstract. o Expanded Abstract.
o General scrub of text - input from Simon Romano. o General scrub of text - input from Simon Romano.
o Added IANA Considerations section. o Added IANA Considerations section.
o Added Security Considerations section. o Added Security Considerations section.
11.4. Changes from 00 Version 11.5. Changes from 00 Version
o Included In-line text based on strawman proposal. o Included In-line text based on strawman proposal.
o Included first attempt at publish interface based on design team o Included first attempt at publish interface based on design team
work. work.
12. Acknowledgments 12. Acknowledgments
The authors would like to thank the members of the Publish Interface The authors would like to thank the members of the Publish Interface
design team who provided valuable input into this document. The design team who provided valuable input into this document. The
skipping to change at page 118, line 16 skipping to change at page 118, line 16
Format for Presence Information Data Format Location Format for Presence Information Data Format Location
Object (PIDF-LO)", RFC 5139, February 2008. Object (PIDF-LO)", RFC 5139, February 2008.
[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]
Hadley, M., Gudgin, M., Mendelsohn, N., Moreau, J., and H. Nielsen, H., Gudgin, M., Hadley, M., Moreau, J., and N.
Nielsen, "SOAP Version 1.2 Part 1: Messaging Framework", Mendelsohn, "SOAP Version 1.2 Part 1: Messaging
World Wide Web Consortium FirstEdition REC-soap12-part1- Framework", World Wide Web Consortium FirstEdition REC-
20030624, June 2003, soap12-part1-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. Mendelsohn, N., Nielsen, H., Moreau, J., Gudgin, M., and
Nielsen, "SOAP Version 1.2 Part 2: Adjuncts", World Wide M. Hadley, "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>.
13.2. Informative References 13.2. Informative References
[I-D.ietf-mediactrl-ivr-control-package] [I-D.ietf-mediactrl-ivr-control-package]
McGlashan, S., Melanchuk, T., and C. Boulton, "An McGlashan, S., Melanchuk, T., and C. Boulton, "An
Interactive Voice Response (IVR) Control Package for the Interactive Voice Response (IVR) Control Package for the
Media Control Channel Framework", Media Control Channel Framework",
 End of changes. 29 change blocks. 
54 lines changed or deleted 66 lines changed or added

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