draft-ietf-mediactrl-sip-control-framework-09.txt   draft-ietf-mediactrl-sip-control-framework-10.txt 
Network Working Group C. Boulton Network Working Group C. Boulton
Internet-Draft NS-Technologies Internet-Draft NS-Technologies
Expires: August 23, 2009 T. Melanchuk Intended status: Standards Track T. Melanchuk
Rain Willow Communications Expires: August 30, 2009 Rain Willow Communications
S. McGlashan S. McGlashan
Hewlett-Packard Hewlett-Packard
February 19, 2009 February 26, 2009
Media Control Channel Framework Media Control Channel Framework
draft-ietf-mediactrl-sip-control-framework-09 draft-ietf-mediactrl-sip-control-framework-10
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 to IETF 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), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 23, 2009. This Internet-Draft will expire on August 30, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
This document describes a Framework and protocol for application This document describes a Framework and protocol for application
deployment where the application programming logic and media deployment where the application programming logic and media
processing are distributed. This implies that application processing are distributed. This implies that application
programming logic can seamlessly gain access to appropriate resources programming logic can seamlessly gain access to appropriate resources
that are not co-located on the same physical network entity. The that are not co-located on the same physical network entity. The
framework uses the Session Initiation Protocol (SIP) to establish an framework uses the Session Initiation Protocol (SIP) to establish an
application-level control mechanism between application servers and application-level control mechanism between application servers and
skipping to change at page 4, line 17 skipping to change at page 4, line 17
12.4. Control Framework Header Fields . . . . . . . . . . . . . 40 12.4. Control Framework Header Fields . . . . . . . . . . . . . 40
12.5. Control Framework Port . . . . . . . . . . . . . . . . . 41 12.5. Control Framework Port . . . . . . . . . . . . . . . . . 41
12.6. SDP Transport Protocol . . . . . . . . . . . . . . . . . 41 12.6. SDP Transport Protocol . . . . . . . . . . . . . . . . . 41
12.7. 'cfw-id' SDP Attribute . . . . . . . . . . . . . . . . . 41 12.7. 'cfw-id' SDP Attribute . . . . . . . . . . . . . . . . . 41
12.8. URN Sub-Namespace for 12.8. URN Sub-Namespace for
urn:ietf:params:xml:ns:control:framework-attributes . . . 42 urn:ietf:params:xml:ns:control:framework-attributes . . . 42
12.9. XML Schema Registration . . . . . . . . . . . . . . . . . 42 12.9. XML Schema Registration . . . . . . . . . . . . . . . . . 42
12.10. MIME Media Type Registration for 12.10. MIME Media Type Registration for
'application/framework-attributes+xml' . . . . . . . . . 43 'application/framework-attributes+xml' . . . . . . . . . 43
13. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 13. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
13.1. Changes from 08 Version . . . . . . . . . . . . . . . . . 43 13.1. Changes from 09 Version . . . . . . . . . . . . . . . . . 43
13.2. Changes from 07 Version . . . . . . . . . . . . . . . . . 44 13.2. Changes from 08 Version . . . . . . . . . . . . . . . . . 44
13.3. Changes from 06 Version . . . . . . . . . . . . . . . . . 44 13.3. Changes from 07 Version . . . . . . . . . . . . . . . . . 44
13.4. Changes from 05 Version . . . . . . . . . . . . . . . . . 44 13.4. Changes from 06 Version . . . . . . . . . . . . . . . . . 44
13.5. Changes from 04 Version . . . . . . . . . . . . . . . . . 44 13.5. Changes from 05 Version . . . . . . . . . . . . . . . . . 44
13.6. Changes from 03 Version . . . . . . . . . . . . . . . . . 44 13.6. Changes from 04 Version . . . . . . . . . . . . . . . . . 44
13.7. Changes from 02 Version . . . . . . . . . . . . . . . . . 45 13.7. Changes from 03 Version . . . . . . . . . . . . . . . . . 44
13.8. Changes from 01 Version . . . . . . . . . . . . . . . . . 45 13.8. Changes from 02 Version . . . . . . . . . . . . . . . . . 45
13.9. Changes from 00 Version . . . . . . . . . . . . . . . . . 45 13.9. Changes from 01 Version . . . . . . . . . . . . . . . . . 45
13.10. Changes from 00 Version . . . . . . . . . . . . . . . . . 45
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 46 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 46
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 46 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 46
16. Appendix: Common Package Components . . . . . . . . . . . . . 46 16. Appendix: Common Package Components . . . . . . . . . . . . . 46
16.1. Common Dialog/Multiparty Reference Schema . . . . . . . . 46 16.1. Common Dialog/Multiparty Reference Schema . . . . . . . . 46
17. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48 17. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
17.1. Normative References . . . . . . . . . . . . . . . . . . 48 17.1. Normative References . . . . . . . . . . . . . . . . . . 48
17.2. Informative References . . . . . . . . . . . . . . . . . 49 17.2. Informative References . . . . . . . . . . . . . . . . . 49
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 50 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 50
1. Introduction 1. Introduction
skipping to change at page 5, line 27 skipping to change at page 5, line 27
primary driver and use case for this work. It is intended that the primary driver and use case for this work. It is intended that the
framework contained in this document can be used for a variety of framework contained in this document can be used for a variety of
device control scenarios (for example, conference control). device control scenarios (for example, conference control).
This document does not define a particular SIP protocol extension for This document does not define a particular SIP protocol extension for
the direct control of external components. Rather, other documents, the direct control of external components. Rather, other documents,
known as "Control Packages," extend the control framework described known as "Control Packages," extend the control framework described
by this document. Section 8 provides a comprehensive set of by this document. Section 8 provides a comprehensive set of
guidelines for creating such Control Packages. guidelines for creating such Control Packages.
Current IETF device control protocols, such as megaco [RFC3525], Current IETF device control protocols, such as megaco [RFC5125],
while excellent for controlling media gateways that bridge separate while excellent for controlling media gateways that bridge separate
networks, are troublesome for supporting media-rich applications in networks, are troublesome for supporting media-rich applications in
SIP networks. This is because megaco duplicates many of the SIP networks. This is because megaco duplicates many of the
functions inherent in SIP. Rather than using a single protocol for functions inherent in SIP. Rather than using a single protocol for
session establishment and application media processing, application session establishment and application media processing, application
developers need to translate between two separate mechanisms. developers need to translate between two separate mechanisms.
Moreover, the model provided by the framework presented here, using Moreover, the model provided by the framework presented here, using
SIP, better matches the application programming model than does SIP, better matches the application programming model than does
megaco. megaco.
skipping to change at page 28, line 32 skipping to change at page 28, line 32
9.1. Control Framework Formal Syntax 9.1. Control Framework Formal Syntax
The Control Framework interactions use the UTF-8 transformation The Control Framework interactions use the UTF-8 transformation
format as defined in [RFC3629]. The syntax in this section uses the format as defined in [RFC3629]. The syntax in this section uses the
Augmented Backus-Naur Form (ABNF) as defined in [RFC5234]. Augmented Backus-Naur Form (ABNF) as defined in [RFC5234].
control-req-or-resp = control-request / control-response control-req-or-resp = control-request / control-response
control-request = control-req-start *headers CRLF [control-content] control-request = control-req-start *headers CRLF [control-content]
control-response = control-resp-start *headers CRLF [control-content] control-response = control-resp-start *headers CRLF [control-content]
control-req-start = pCFW SP transact-id SP method CRLF control-req-start = pCFW SP trans-id SP method CRLF
control-resp-start = pCFW SP transact-id SP status-code [SP comment] CRLF control-resp-start = pCFW SP trans-id SP status-code [SP comment] CRLF
comment = utf8text comment = utf8text
pCFW = %x43.46.57; CFW in caps pCFW = %x43.46.57; CFW in caps
transact-id = alpha-num-token trans-id = alpha-num-token
method = mCONTROL / mREPORT / mSYNC / mK-ALIVE / other-method method = mCONTROL / mREPORT / mSYNC / mK-ALIVE / other-method
mCONTROL = %x43.4F.4E.54.52.4F.4C; CONTROL in caps mCONTROL = %x43.4F.4E.54.52.4F.4C; CONTROL in caps
mREPORT = %x52.45.50.4F.52.54; REPORT in caps mREPORT = %x52.45.50.4F.52.54; REPORT in caps
mSYNC = %x53.59.4E.43; SYNC in caps mSYNC = %x53.59.4E.43; SYNC in caps
mK-ALIVE = %x4B.2D.41.4C.49.56.45;K-ALIVE in caps mK-ALIVE = %x4B.2D.41.4C.49.56.45;K-ALIVE in caps
other-method = 1*UPALPHA other-method = 1*UPALPHA
status-code = 3*DIGIT ; any code defined in this and other documents status-code = 3*DIGIT ; any code defined in this and other documents
headers = header-name CRLF headers = header-name CRLF
skipping to change at page 29, line 22 skipping to change at page 29, line 22
/Keep-alive /Keep-alive
/ext-header) /ext-header)
Content-Length = "Content-Length:" SP 1*DIGIT Content-Length = "Content-Length:" SP 1*DIGIT
Control-Package = "Control-Package:" SP 1*alpha-num-token Control-Package = "Control-Package:" SP 1*alpha-num-token
Status = "Status:" SP ("update" / "terminate" ) Status = "Status:" SP ("update" / "terminate" )
Timeout = "Timeout:" SP 1*DIGIT Timeout = "Timeout:" SP 1*DIGIT
Seq = "Seq:" SP 1*DIGIT Seq = "Seq:" SP 1*DIGIT
Dialog-id = "Dialog-ID:" SP dialog-id-string Dialog-id = "Dialog-ID:" SP dialog-id-string
Packages = "Packages:" SP package-name *(COMMA package-name) Packages = "Packages:" SP package-name *(COMMA package-name)
Supported = "Supported:" SP supported-alphanum *(COMMA supported-alphanum) Supported = "Supported:" SP supprtd-alphanum *(COMMA supprtd-alphanum)
Keep-alive = "Keep-Alive:" SP kalive-seconds Keep-alive = "Keep-Alive:" SP kalive-seconds
dialog-id-string = alpha-num-token dialog-id-string = alpha-num-token
package-name = alpha-num-token package-name = alpha-num-token
supported-alphanum = alpha-num-token supprtd-alphanum = alpha-num-token
kalive-seconds = 1*DIGIT kalive-seconds = 1*DIGIT
alpha-num-token = ALPHANUM 3*31alpha-num-tokent-char alpha-num-token = ALPHANUM 3*31alpha-num-tokent-char
alpha-num-tokent-char = ALPHANUM / "." / "-" / "+" / "%" / "=" / "/" alpha-num-tokent-char = ALPHANUM / "." / "-" / "+" / "%" / "=" / "/"
control-content = *OCTET control-content = *OCTET
Content-Type = "Content-Type:" SP media-type Content-Type = "Content-Type:" SP media-type
media-type = type "/" subtype *( ";" gen-param ) media-type = type "/" subtype *( ";" gen-param )
type = token type = token
skipping to change at page 30, line 33 skipping to change at page 30, line 32
UTF8-CONT = %x80-BF UTF8-CONT = %x80-BF
The following table details a summary of the headers that can be The following table details a summary of the headers that can be
contained in Control Framework interactions. The "where" columns contained in Control Framework interactions. The "where" columns
details where headers can be used: details where headers can be used:
R: header field may only appear in requests; R: header field may only appear in requests;
r: header field may only appear in responses; r: header field may only appear in responses;
Blank indicates the header field may appear in either requests or responses. Blank indicates the header field may appear in either requests or
responses.
2xx, 4xx, etc.: A numerical value or range indicates response 2xx, 4xx, etc.: A numerical value or range indicates response
codes with which the header field can be used; codes with which the header field can be used;
An empty entry in the "where" column indicates that the header An empty entry in the "where" column indicates that the header
field may be present in all requests and responses. field may be present in all requests and responses.
The remaining columns list the specified methods and the presence of The remaining columns list the specified methods and the presence of
a specific header: a specific header:
skipping to change at page 39, line 16 skipping to change at page 39, line 16
initial IANA registration for control packages will be empty. The initial IANA registration for control packages will be empty. The
remainder of the text in this section gives an example of the type of remainder of the text in this section gives an example of the type of
information to be maintained by the IANA; it also demonstrates all information to be maintained by the IANA; it also demonstrates all
three possible permutations of package type, contact, and reference. three possible permutations of package type, contact, and reference.
The table below lists the control packages defined in the "Media The table below lists the control packages defined in the "Media
Control Channel Framework". Control Channel Framework".
Package Name Contact Reference Package Name Contact Reference
------------ ------- --------- ------------ ------- ---------
example1 [Boulton] example1 [contact@example.org]
example2 [Boulton] [RFCXXX] example2 [contact@example.org] [RFCXXXX]
example3 [RFCXXX] example3 [RFCXXXX]
12.1.1. Control Package Registration Template 12.1.1. Control Package Registration Template
To: ietf-sip-control@iana.org To: ietf-sip-control@iana.org
Subject: Registration of new Channel Framework package Subject: Registration of new Channel Framework package
Package Name: Package Name:
(Package names must conform to the syntax described in (Package names must conform to the syntax described in
section 8.1.) section 8.1.)
skipping to change at page 39, line 43 skipping to change at page 39, line 43
Person & email address to contact for further information: Person & email address to contact for further information:
12.2. Control Framework Method Names 12.2. Control Framework Method Names
This specification establishes the Methods sub-registry under Control This specification establishes the Methods sub-registry under Control
Framework Parameters and initiates its population as follows. New Framework Parameters and initiates its population as follows. New
parameters in this sub-registry must be published in an RFC (either parameters in this sub-registry must be published in an RFC (either
as an IETF submission or RFC Editor submission). as an IETF submission or RFC Editor submission).
CONTROL - [RFCXXX] CONTROL - [RFCXXXX]
REPORT - [RFCXXX] REPORT - [RFCXXXX]
SYNC - [RFCXXX] SYNC - [RFCXXXX]
The following information MUST be provided in an RFC publication in The following information MUST be provided in an RFC publication in
order to register a new Control Framework method:
o The method name. o The method name.
o The RFC number in which the method is registered. o The RFC number in which the method is registered.
12.3. Control Framework Status Codes 12.3. Control Framework Status Codes
This specification establishes the Status-Code sub-registry under This specification establishes the Status-Code sub-registry under
Channel Framework Parameters. New parameters in this sub-registry Channel Framework Parameters. New parameters in this sub-registry
must be published in an RFC (either as an IETF submission or RFC must be published in an RFC (either as an IETF submission or RFC
Editor submission). Its initial population is defined in Section 9. Editor submission). Its initial population is defined in Section 9.
It takes the following format: It takes the following format:
skipping to change at page 41, line 35 skipping to change at page 41, line 35
Specifications defining new protocol values must define the rules for Specifications defining new protocol values must define the rules for
the associated media format namespace. The 'TCP/CFW', 'TCP/TLS/CFW', the associated media format namespace. The 'TCP/CFW', 'TCP/TLS/CFW',
'SCTP/CFW' and 'SCTP/TLS/CFW' protocol values allow only one value in 'SCTP/CFW' and 'SCTP/TLS/CFW' protocol values allow only one value in
the format field (fmt), which is a single occurrence of "*". Actual the format field (fmt), which is a single occurrence of "*". Actual
format determination is made using the control package extension format determination is made using the control package extension
specific payloads. specific payloads.
12.7. 'cfw-id' SDP Attribute 12.7. 'cfw-id' SDP Attribute
Contact name: Chris Boulton cboulton@avaya.com. Contact name: Chris Boulton chris@ns-technologies.com.
Attribute name: "cfw-id". Attribute name: "cfw-id".
Type of attribute Media level. Type of attribute Media level.
Subject to charset: Not. Subject to charset: Not.
Purpose of attribute: The 'cfw-id' attribute indicates Purpose of attribute: The 'cfw-id' attribute indicates
an identifier that can be used to correlate the control an identifier that can be used to correlate the control
channel with the SIP dialog used to negotiate it, when channel with the SIP dialog used to negotiate it, when
skipping to change at page 42, line 15 skipping to change at page 42, line 15
12.8. URN Sub-Namespace for 12.8. URN Sub-Namespace for
urn:ietf:params:xml:ns:control:framework-attributes urn:ietf:params:xml:ns:control:framework-attributes
This section registers a new XML namespace, This section registers a new XML namespace,
"urn:ietf:params:xml:ns:control:framework-attributes", per the "urn:ietf:params:xml:ns:control:framework-attributes", per the
guidelines in RFC 3688 [RFC3688]. guidelines in RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:control:framework-attributes URI: urn:ietf:params:xml:ns:control:framework-attributes
Registrant Contact: IETF, MEDIACTRL working group, Registrant Contact: IETF, MEDIACTRL working group,
(mediactrl@ietf.org), Chris Boulton (cboulton@avaya.com). (mediactrl@ietf.org), Chris Boulton (chris@ns-technologies.com).
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head> <head>
<title>Media Control Channel attributes</title> <title>Media Control Channel attributes</title>
</head> </head>
<body> <body>
<h1>Namespace for Media Control Channel attributes</h1> <h1>Namespace for Media Control Channel attributes</h1>
<h2>urn:ietf:params:xml:ns:control:framework-attributes</h2> <h2>urn:ietf:params:xml:ns:control:framework-attributes</h2>
[NOTE TO IANA/RFC-EDITOR: Please replace XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX
with the RFC number for this specification.] with the RFC number for this specification.
<p>See RFCXXXX</p> <p>See RFCXXXX</p>
</body> </body>
</html> </html>
END END
12.9. XML Schema Registration 12.9. XML Schema Registration
This section registers an XML schema as per the guidelines in RFC This section registers an XML schema as per the guidelines in RFC
3688 [RFC3688]. 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:control:framework-attributes URI: urn:ietf:params:xml:ns:control:framework-attributes
Registrant Contact: IETF, MEDIACTRL working group, (mediactrl@ietf.org), Registrant Contact: IETF, MEDIACTRL working group,
Chris Boulton (cboulton@avaya.com). (mediactrl@ietf.org), Chris Boulton (chris@ns-technologies.com).
Schema: The XML for this schema can be found as the entirety of Schema: The XML for this schema can be found as the entirety of
Section 16 of this document. Section 16 of this document.
12.10. MIME Media Type Registration for 'application/ 12.10. MIME Media Type Registration for 'application/
framework-attributes+xml' framework-attributes+xml'
This section registers the "application/framework-attributes+xml" This section registers the "application/framework-attributes+xml"
MIME type. MIME type.
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of MIME media type application/framework-attributes+xml Subject: Registration of MIME media type
application/framework-attributes+xml
MIME media type name: application MIME media type name: application
MIME subtype name: framework-attributes+xml MIME subtype name: framework-attributes+xml
Required parameters: (none) Required parameters: (none)
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of enclosed XML. Default is Indicates the character encoding of enclosed XML. Default is
UTF-8. UTF-8.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See RFC characters, depending on the character encoding used. See RFC
3023 [RFC3023], section 3.2. 3023 [RFC3023], section 3.2.
Security considerations: No known security considerations outside Security considerations: No known security considerations outside
of those provided by core Media Control Channel Framework. of those provided by core Media Control Channel Framework.
Interoperability considerations: This content type provides common Interoperability considerations: This content type provides common
constructs for related Media Control Channel packages. constructs for related Media Control Channel packages.
Published specification: RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please Published specification: RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please
replace XXXX with the RFC number for this specification.] replace XXXX with the RFC number for this specification.]
Applications which use this media type: Implementations of appropriate Applications which use this media type: Implementations of
Media Control Channel packages. appropriate Media Control Channel packages.
Additional Information: Magic Number(s): (none) Additional Information: Magic Number(s): (none)
File extension(s): .xml File extension(s): .xml
Macintosh File Type Code(s): (none) Macintosh File Type Code(s): (none)
Person & email address to contact for further information: Chris Person & email address to contact for further information: Chris
Boulton <cboulton@avaya.com> Boulton <chris@ns-technologies.com>
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author/Change controller: The IETF Author/Change controller: The IETF
Other information: None. Other information: None.
13. Changes 13. Changes
Note to RFC Editor: Please remove this whole section. Note to RFC Editor: Please remove this whole section.
13.1. Changes from 08 Version 13.1. Changes from 09 Version
o Editorial fixes for strict idnits checking: RFC status, syntax,
references, line length.
13.2. Changes from 08 Version
o Altered definition of 'Transaction-Timeout'. o Altered definition of 'Transaction-Timeout'.
o Removed 'random' reference in preference for globally unique. o Removed 'random' reference in preference for globally unique.
o Clarified passive entity behavior on Keep-Alive timeout. o Clarified passive entity behavior on Keep-Alive timeout.
o Input of Chair comments for final publication. o Input of Chair comments for final publication.
o Removed extra CRLF in ABNF after 'headers'. o Removed extra CRLF in ABNF after 'headers'.
o Clarified 481 behavior. o Clarified 481 behavior.
o Removed definition for extended transaction lifetime o Removed definition for extended transaction lifetime
13.2. Changes from 07 Version 13.3. Changes from 07 Version
o Added '*' to SDP 'm=' line in examples. o Added '*' to SDP 'm=' line in examples.
13.3. Changes from 06 Version 13.4. Changes from 06 Version
o Added 202 Timeout entry to table. o Added 202 Timeout entry to table.
o Fixed some general nits and language. o Fixed some general nits and language.
o Fixed ABNF to be 'control-content = *OCTET'. o Fixed ABNF to be 'control-content = *OCTET'.
o Added general qualifier to sections 6.3.3.1 and 6.3.3.2 so that o Added general qualifier to sections 6.3.3.1 and 6.3.3.2 so that
rules for either tearing down or reconnecting are applied. rules for either tearing down or reconnecting are applied.
13.4. Changes from 05 Version 13.5. Changes from 05 Version
o Reworded 'must' used in Introduction. o Reworded 'must' used in Introduction.
o Added urn namespace definition in IANA section. o Added urn namespace definition in IANA section.
o Added XML schema registration in IANA section. o Added XML schema registration in IANA section.
o Added MIME registration in IANA section. o Added MIME registration in IANA section.
13.5. Changes from 04 Version 13.6. Changes from 04 Version
o Fixed nits as reported by Brian Weis. o Fixed nits as reported by Brian Weis.
o Amended Security text as per secdir review. o Amended Security text as per secdir review.
o Removed optional 'label' part of dialog identifier as per interim o Removed optional 'label' part of dialog identifier as per interim
call. call.
o Added clarifying text at the beginning of section 4 to help o Added clarifying text at the beginning of section 4 to help
describe what the section is about. describe what the section is about.
o Added text at the beginning of section 8 clarifying that the o Added text at the beginning of section 8 clarifying that the
template is not the basis for packages BUT only needs to be template is not the basis for packages BUT only needs to be
included as part of a Control Package. included as part of a Control Package.
13.6. Changes from 03 Version 13.7. Changes from 03 Version
o Removed comment from XML schema in appendix. o Removed comment from XML schema in appendix.
o Changed dialog-id-string in section 9.1 to be dialog-id-string = o Changed dialog-id-string in section 9.1 to be dialog-id-string =
alpha-num-token. alpha-num-token.
o Changed status-code in section 9.1 to status-code = 3*DIGIT o Changed status-code in section 9.1 to status-code = 3*DIGIT
o Aligned use of Keep-Alive header terms in document. o Aligned use of Keep-Alive header terms in document.
o Added text to clarify connection and session relationship - as per o Added text to clarify connection and session relationship - as per
thread with Roni on use of 'new' and 'existing'. thread with Roni on use of 'new' and 'existing'.
o Use of K-Alive control message now aligned. o Use of K-Alive control message now aligned.
o Clarified that a CONTROL with no payload should be dealt with at o Clarified that a CONTROL with no payload should be dealt with at
the package level. the package level.
o Scrubbed ABNF + XML. o Scrubbed ABNF + XML.
13.7. Changes from 02 Version 13.8. Changes from 02 Version
o RAI review version. See comments. o RAI review version. See comments.
o Fixed broken IANA subsections ordering + naming. o Fixed broken IANA subsections ordering + naming.
13.8. Changes from 01 Version 13.9. Changes from 01 Version
o Restructured text for readability. o Restructured text for readability.
o Changed SYNCH method name to SYNC. o Changed SYNCH method name to SYNC.
o Removed 'pending' state to be replaced by 'update' with no o Removed 'pending' state to be replaced by 'update' with no
payload. payload.
o Replaced construction of dialog-id with new SDP parameter and o Replaced construction of dialog-id with new SDP parameter and
revised text. revised text.
o Removed problem with K-Alive mechanism. K-Alive timers are now o Removed problem with K-Alive mechanism. K-Alive timers are now
separate from any other Control messages as the delay in separate from any other Control messages as the delay in
processing allows for un-sync on both sides. processing allows for un-sync on both sides.
o Added transaction timeout of 5 seconds - as per meeting. o Added transaction timeout of 5 seconds - as per meeting.
o Added Upper Limit for transaction timeout on REPORT to 15 seconds. o Added Upper Limit for transaction timeout on REPORT to 15 seconds.
o Added Content-Type to table and missing examples etc. o Added Content-Type to table and missing examples etc.
o Simplified Security Section as per meeting feedback. o Simplified Security Section as per meeting feedback.
o Added proposed 'holdconn' text. o Added proposed 'holdconn' text.
o Added Default port text - as per meeting. o Added Default port text - as per meeting.
o Added Audit text. o Added Audit text.
13.9. Changes from 00 Version 13.10. Changes from 00 Version
o Aligned tokens to be 'CFW' (removed ESCS). o Aligned tokens to be 'CFW' (removed ESCS).
o Content-Length not mandatory for messages with no payload. o Content-Length not mandatory for messages with no payload.
o Corrected changes to call flows from legacy versions. o Corrected changes to call flows from legacy versions.
o Use of term 'Active UA' in section 7 + others. o Use of term 'Active UA' in section 7 + others.
o Added 'notify' to status header of ABNF. o Added 'notify' to status header of ABNF.
o Changed 481 to be transaction specific. o Changed 481 to be transaction specific.
o Added '423' duplicate transaction ID response. o Added '423' duplicate transaction ID response.
o Added '405' method not allowed. o Added '405' method not allowed.
o Added IANA section. o Added IANA section.
skipping to change at page 46, line 16 skipping to change at page 46, line 21
o Organised 'Editors Notes' for discussion on the mailing list. o Organised 'Editors Notes' for discussion on the mailing list.
o Fixed ABNF in relation to extra CRLF on Content-Type. o Fixed ABNF in relation to extra CRLF on Content-Type.
14. Contributors 14. Contributors
Asher Shiratzky from Radvision provided valuable support and Asher Shiratzky from Radvision provided valuable support and
contributions to the early versions of this document. contributions to the early versions of this document.
15. Acknowledgments 15. Acknowledgments
The authors would like to thank Ian Evans and Michael Bardzinski of The authors would like to thank Ian Evans of Avaya and Michael
Avaya, Adnan Saleem of Radisys, and Dave Morgan for useful review and Bardzinski of NS-Technologies, Adnan Saleem of Radisys, and Dave
input to this work. Eric Burger contributed to the early phases of Morgan for useful review and input to this work. Eric Burger
this work. contributed to the early phases of this work.
Expert review was also provided by Spencer Dawkins, Krishna Prasad Expert review was also provided by Spencer Dawkins, Krishna Prasad
Kalluri, Lorenzo Miniero, and Roni Even. Hadriel Kaplan provided Kalluri, Lorenzo Miniero, and Roni Even. Hadriel Kaplan provided
expert guidance on the dialog association mechanism. Lorenzo Miniero expert guidance on the dialog association mechanism. Lorenzo Miniero
has constantly provided excellent feedback based on his work. has constantly provided excellent feedback based on his work.
Ben Campbell carried out the RAI expert review on this draft and Ben Campbell carried out the RAI expert review on this draft and
provided a great deal of invaluable input. Brian Weis carried out a provided a great deal of invaluable input. Brian Weis carried out a
thorough security review. Text from Eric Burger was used in the thorough security review. Text from Eric Burger was used in the
introduction in the explanation for using SIP. introduction in the explanation for using SIP.
skipping to change at page 48, line 7 skipping to change at page 48, line 7
Package, any control XML referenced by the attribute applies to all Package, any control XML referenced by the attribute applies to all
related media dialogs. Unlike the dialog attribute, the related media dialogs. Unlike the dialog attribute, the
'conferenceid' attribute does not need to be constructed based on the 'conferenceid' attribute does not need to be constructed based on the
overlying SIP dialog. The 'conferenceid' attribute value is system overlying SIP dialog. The 'conferenceid' attribute value is system
specific and should be selected with relevant context and uniqueness. specific and should be selected with relevant context and uniqueness.
The full schema follows: The full schema follows:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="urn:ietf:params:xml:ns:control:framework-attributes" <xsd:schema
targetNamespace="urn:ietf:params:xml:ns:control:framework-attributes"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:ietf:params:xml:ns::control:framework-attributes" xmlns="urn:ietf:params:xml:ns::control:framework-attributes"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:attributeGroup name="framework-attributes"> <xsd:attributeGroup name="framework-attributes">
<xsd:annotation> <xsd:annotation>
<xsd:documentation>SIP Connection and Conf Identifiers</xsd:documentation> <xsd:documentation>
SIP Connection and Conf Identifiers
</xsd:documentation>
</xsd:annotation> </xsd:annotation>
<xsd:attribute name="connectionid" type="xsd:string"/> <xsd:attribute name="connectionid" type="xsd:string"/>
<xsd:attribute name="conferenceid" type="xsd:string"/> <xsd:attribute name="conferenceid" type="xsd:string"/>
</xsd:attributeGroup> </xsd:attributeGroup>
</xsd:schema> </xsd:schema>
17. References 17. References
skipping to change at page 49, line 26 skipping to change at page 49, line 29
[RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in [RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
the Session Description Protocol (SDP)", RFC 4145, the Session Description Protocol (SDP)", RFC 4145,
September 2005. September 2005.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[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.
[RFC5167] Dolly, M. and R. Even, "Media Server Control Protocol
Requirements", RFC 5167, March 2008.
[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.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
skipping to change at page 50, line 5 skipping to change at page 49, line 52
Burger, E., "Media Server Control Language and Protocol Burger, E., "Media Server Control Language and Protocol
Thoughts", draft-burger-mscl-thoughts-01 (work in Thoughts", draft-burger-mscl-thoughts-01 (work in
progress), June 2006. progress), June 2006.
[I-D.ietf-sip-outbound] [I-D.ietf-sip-outbound]
Jennings, C. and R. Mahy, "Managing Client Initiated Jennings, C. and R. Mahy, "Managing Client Initiated
Connections in the Session Initiation Protocol (SIP)", Connections in the Session Initiation Protocol (SIP)",
draft-ietf-sip-outbound-16 (work in progress), draft-ietf-sip-outbound-16 (work in progress),
October 2008. October 2008.
[RFC3525] Groves, C., Pantaleo, M., Anderson, T., and T. Taylor, [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
"Gateway Control Protocol Version 1", RFC 3525, June 2003. Types", RFC 3023, January 2001.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. Applications", STD 64, RFC 3550, July 2003.
[RFC3725] Rosenberg, J., Peterson, J., Schulzrinne, H., and G. [RFC3725] Rosenberg, J., Peterson, J., Schulzrinne, H., and G.
Camarillo, "Best Current Practices for Third Party Call Camarillo, "Best Current Practices for Third Party Call
Control (3pcc) in the Session Initiation Protocol (SIP)", Control (3pcc) in the Session Initiation Protocol (SIP)",
BCP 85, RFC 3725, April 2004. BCP 85, RFC 3725, April 2004.
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
"Indicating User Agent Capabilities in the Session "Indicating User Agent Capabilities in the Session
Initiation Protocol (SIP)", RFC 3840, August 2004. Initiation Protocol (SIP)", RFC 3840, August 2004.
[RFC3841] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller [RFC3841] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller
Preferences for the Session Initiation Protocol (SIP)", Preferences for the Session Initiation Protocol (SIP)",
RFC 3841, August 2004. RFC 3841, August 2004.
[RFC5125] Taylor, T., "Reclassification of RFC 3525 to Historic",
RFC 5125, February 2008.
[RFC5167] Dolly, M. and R. Even, "Media Server Control Protocol
Requirements", RFC 5167, March 2008.
Authors' Addresses Authors' Addresses
Chris Boulton Chris Boulton
NS-Technologies NS-Technologies
Email: chris@ns-technologies.com Email: chris@ns-technologies.com
Tim Melanchuk Tim Melanchuk
Rain Willow Communications Rain Willow Communications
 End of changes. 40 change blocks. 
63 lines changed or deleted 77 lines changed or added

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