draft-ietf-mmusic-msrp-usage-data-channel-12.txt   draft-ietf-mmusic-msrp-usage-data-channel-13.txt 
MMUSIC K. Drage, Ed. MMUSIC K. Drage, Ed.
Internet-Draft M. Makaraju Internet-Draft M. Makaraju
Intended status: Standards Track J. Stoetzer-Bradler Intended status: Standards Track J. Stoetzer-Bradler
Expires: February 11, 2020 R. Ejzak Expires: February 27, 2020 R. Ejzak
J. Marcon J. Marcon
Unaffiliated Unaffiliated
J. Recio, Ed. J. Recio, Ed.
CoSMo Software August 26, 2019
August 10, 2019
MSRP over Data Channels MSRP over Data Channels
draft-ietf-mmusic-msrp-usage-data-channel-12 draft-ietf-mmusic-msrp-usage-data-channel-13
Abstract Abstract
This document specifies how the Message Session Relay Protocol (MSRP) This document specifies how the Message Session Relay Protocol (MSRP)
can be instantiated as a data channel sub-protocol, using the SDP can be instantiated as a data channel sub-protocol, using the SDP
offer/answer exchange-based generic data channel negotiation offer/answer exchange-based generic data channel negotiation
framework. Two network configurations are documented: a WebRTC end- framework. Two network configurations are documented: a WebRTC end-
to-end configuration (connecting two MSRP over data channel to-end configuration (connecting two MSRP over data channel
endpoints), and a gateway configuration (connecting an MSRP over data endpoints), and a gateway configuration (connecting an MSRP over data
channel endpoint with an MSRP over TCP or TLS endpoint). channel endpoint with an MSRP over TCP or TLS endpoint).
skipping to change at page 1, line 41 skipping to change at page 1, line 40
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 February 11, 2020. This Internet-Draft will expire on February 27, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 24 skipping to change at page 2, line 23
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Principles . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Principles . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. MSRP Data Channel . . . . . . . . . . . . . . . . . . . . 5 4.1. MSRP Data Channel . . . . . . . . . . . . . . . . . . . . 5
4.2. Session Mapping . . . . . . . . . . . . . . . . . . . . . 5 4.2. Session Mapping . . . . . . . . . . . . . . . . . . . . . 5
4.3. MSRP URI . . . . . . . . . . . . . . . . . . . . . . . . 5 4.3. MSRP URI . . . . . . . . . . . . . . . . . . . . . . . . 5
4.4. msrp-scheme . . . . . . . . . . . . . . . . . . . . . . . 5 4.4. msrp-scheme . . . . . . . . . . . . . . . . . . . . . . . 5
5. End-to-End Configuration . . . . . . . . . . . . . . . . . . 5 5. End-to-End Configuration . . . . . . . . . . . . . . . . . . 5
5.1. Basic MSRP Support . . . . . . . . . . . . . . . . . . . 6 5.1. Basic MSRP Support . . . . . . . . . . . . . . . . . . . 6
5.1.1. Session Negotiation . . . . . . . . . . . . . . . . . 6 5.1.1. SDP Considerations . . . . . . . . . . . . . . . . . 6
5.1.1.1. Use of the dcmap Attribute . . . . . . . . . . . 6 5.1.1.1. Use of the dcmap Attribute . . . . . . . . . . . 6
5.1.1.2. Use of the dcsa Attribute . . . . . . . . . . . . 6 5.1.1.2. Use of the dcsa Attribute . . . . . . . . . . . . 6
5.1.1.3. Use of the setup Attribute . . . . . . . . . . . 7 5.1.1.3. Use of the dcsa embedded setup Attribute . . . . 7
5.1.1.4. Example SDP Negotiation . . . . . . . . . . . . . 8 5.1.1.4. Example SDP Negotiation . . . . . . . . . . . . . 7
5.1.2. Session Opening . . . . . . . . . . . . . . . . . . . 8 5.1.2. Session Opening . . . . . . . . . . . . . . . . . . . 8
5.1.3. Data Framing . . . . . . . . . . . . . . . . . . . . 9 5.1.3. Data Framing . . . . . . . . . . . . . . . . . . . . 8
5.1.4. Data Sending and Reporting . . . . . . . . . . . . . 9 5.1.4. Data Sending and Reporting . . . . . . . . . . . . . 9
5.1.5. Session Closing . . . . . . . . . . . . . . . . . . . 9 5.1.5. Session Closing . . . . . . . . . . . . . . . . . . . 9
5.2. Support for MSRP File Transfer Function . . . . . . . . . 9 5.2. Support for MSRP File Transfer Function . . . . . . . . . 9
6. Gateway Configuration . . . . . . . . . . . . . . . . . . . . 10 6. Gateway Configuration . . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
7.1. Subprotocol Identifier MSRP . . . . . . . . . . . . . . . 11 7.1. Subprotocol Identifier MSRP . . . . . . . . . . . . . . . 11
7.2. setup Attribute . . . . . . . . . . . . . . . . . . . . . 11 7.2. setup Attribute . . . . . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
10. CHANGE LOG . . . . . . . . . . . . . . . . . . . . . . . . . 12 10. CHANGE LOG . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.1. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-11' . . . . . . . . . . . . . . . . . . . . . . 12 channel-12' . . . . . . . . . . . . . . . . . . . . . . 12
10.2. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.2. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-10' . . . . . . . . . . . . . . . . . . . . . . 12 channel-11' . . . . . . . . . . . . . . . . . . . . . . 12
10.3. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.3. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-09' . . . . . . . . . . . . . . . . . . . . . . 12 channel-10' . . . . . . . . . . . . . . . . . . . . . . 12
10.4. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.4. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-08' . . . . . . . . . . . . . . . . . . . . . . 13 channel-09' . . . . . . . . . . . . . . . . . . . . . . 12
10.5. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.5. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-07' . . . . . . . . . . . . . . . . . . . . . . 13 channel-08' . . . . . . . . . . . . . . . . . . . . . . 12
10.6. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.6. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-06' . . . . . . . . . . . . . . . . . . . . . . 13 channel-07' . . . . . . . . . . . . . . . . . . . . . . 12
10.7. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.7. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-05' . . . . . . . . . . . . . . . . . . . . . . 13 channel-06' . . . . . . . . . . . . . . . . . . . . . . 13
10.8. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.8. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-04' . . . . . . . . . . . . . . . . . . . . . . 13 channel-05' . . . . . . . . . . . . . . . . . . . . . . 13
10.9. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.9. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-03' . . . . . . . . . . . . . . . . . . . . . . 13 channel-04' . . . . . . . . . . . . . . . . . . . . . . 13
10.10. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.10. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-02' . . . . . . . . . . . . . . . . . . . . . . 14 channel-03' . . . . . . . . . . . . . . . . . . . . . . 13
10.11. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.11. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-01' . . . . . . . . . . . . . . . . . . . . . . 14 channel-02' . . . . . . . . . . . . . . . . . . . . . . 13
10.12. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.12. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-00' . . . . . . . . . . . . . . . . . . . . . . 16 channel-01' . . . . . . . . . . . . . . . . . . . . . . 14
10.13. Changes against 'draft-ejzak-mmusic-msrp-usage-data- 10.13. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-00' . . . . . . . . . . . . . . . . . . . . . . 15
10.14. Changes against 'draft-ejzak-mmusic-msrp-usage-data-
channel-01' . . . . . . . . . . . . . . . . . . . . . . 16 channel-01' . . . . . . . . . . . . . . . . . . . . . . 16
10.14. Changes against '-00' . . . . . . . . . . . . . . . . . 17 10.15. Changes against '-00' . . . . . . . . . . . . . . . . . 16
11. Normative References . . . . . . . . . . . . . . . . . . . . 17 11. Normative References . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
The Message Session Relay Protocol (MSRP) [RFC4975] is a protocol for The Message Session Relay Protocol (MSRP) [RFC4975] is a protocol for
transmitting a series of related instant messages in the context of a transmitting a series of related instant messages in the context of a
session. In addition to instant messaging, MSRP can also be used for session. In addition to instant messaging, MSRP can also be used for
image sharing or file transfer. MSRP is currently defined to work image sharing or file transfer. MSRP is currently defined to work
over TCP and TLS connections, and over a WebSocket subprotocol over TCP and TLS connections, and over a WebSocket subprotocol
specified by [RFC7977]. specified by [RFC7977].
skipping to change at page 6, line 7 skipping to change at page 6, line 7
data channel is always secured using DTLS as described in data channel is always secured using DTLS as described in
[I-D.ietf-rtcweb-data-channel]. [I-D.ietf-rtcweb-data-channel].
5. End-to-End Configuration 5. End-to-End Configuration
This section describes the network configuration where each MSRP This section describes the network configuration where each MSRP
endpoint is running MSRP over a data channel. endpoint is running MSRP over a data channel.
5.1. Basic MSRP Support 5.1. Basic MSRP Support
5.1.1. Session Negotiation 5.1.1. SDP Considerations
The generic SDP considerations, including the SDP Offer/Answer
procedures, for negotiating a WebRTC data channel are defined in
[I-D.ietf-mmusic-data-channel-sdpneg]. This section defines the SDP
considerations that are specific to an MSRP data channel.
5.1.1.1. Use of the dcmap Attribute 5.1.1.1. Use of the dcmap Attribute
The SDP offer SHALL include a dcmap attribute line (defined in An offerer and answerer MUST, in each offer and answer, include a
[I-D.ietf-mmusic-data-channel-sdpneg]) within the media description dcmap attribute line ([I-D.ietf-mmusic-data-channel-sdpneg]) within
of the SCTP association for each MSRP data channel session to be the media description of the SCTP association for each MSRP data
negotiated. channel session to be negotiated.
The attribute includes the following data channel parameters: The attribute includes the following data channel parameters:
o "label=" labelstring o "label=" labelstring
o "subprotocol=" "MSRP" o "subprotocol=" "MSRP"
The labelstring is set by the MSRP application according to The labelstring is set by the MSRP application according to
[I-D.ietf-mmusic-data-channel-sdpneg]. Ordered and reliable data
channels MUST always be used, so that the "max-retr" and "max-time"
parameters SHALL NOT be used. If the "ordered" parameter is used,
then its value MUST be equal to "true".
Rest of the SDP offer/answer procedures are per
[I-D.ietf-mmusic-data-channel-sdpneg]. [I-D.ietf-mmusic-data-channel-sdpneg].
The following is an example of the dcmap attribute for an MSRP The offerer and answerer MUST NOT include the max-retr and the max-
session to be negotiated with stream-id=2 and label="chat": time attribute parameters in the dcmap attribute.
The offerer and answerer MAY include the ordered attribute parameter
in the dcmap attribute. If included, the attribute parameter value
MUST be set to "true".
Below is an example of the dcmap attribute for an MSRP session to be
negotiated with stream-id=2 and label="chat":
a=dcmap:2 label="chat";subprotocol="MSRP" a=dcmap:2 label="chat";subprotocol="MSRP"
5.1.1.2. Use of the dcsa Attribute 5.1.1.2. Use of the dcsa Attribute
The SDP offer SHALL also include within the media description for the An offerer and answerer MUST, in each offer and answer, include a
SCTP association, a dcsa attribute line (defined in dcsa attribute line ([I-D.ietf-mmusic-data-channel-sdpneg]) within
[I-D.ietf-mmusic-data-channel-sdpneg]) for each MSRP-specific SDP the media description for the SCTP association for each MSRP-specific
attribute to be negotiated for each MSRP data channel being SDP attribute to be negotiated for each MSRP data channel being
negotiated. negotiated.
The MSRP-specific items that can be negotiated include at least all An offerer and answerer MUST include a dcsa attribute for the
of the following well-known attributes: following MSRP-specific SDP attributes:
o defined in [RFC4975]: "path", "accept-types", "accept-wrapped- o defined in [RFC4975]: "path".
types", "max-size"
o defined in [RFC4566]: "sendonly", "recvonly", "inactive", and o defined in [RFC6714]: "msrp-cema".
"sendrecv"
o defined in [RFC6135]: "setup" o defined in [RFC6135]: "setup". See Section 5.1.1.3
o defined in [RFC5547]: all the parameters related to MSRP file It is considered a protocol error if one or more of the dcsa embedded
transfer. See Section 5.2. attributes listed above are not included in an offer or answer.
MSRP Connection Establishment for Media Anchoring (MSRP-CEMA) An offerer and answerer MAY include a dcsa attribute for the
[RFC6714] is outside of the scope of this document. The msrp-cema following MSRP-specific SDP attributes, following the procedures
attribute SHALL NOT be present. defined for each attributes:
As described in Section 5.1.2 the path attribute is not used for o defined in [RFC4975]: "accept-types", "accept-wrapped-types" and
transport establiment. "max-size"
The SDP answer SHALL include zero or more corresponding dcsa o defined in [RFC4566]: "sendonly", "recvonly", "inactive" and
attribute lines for each negotiated MSRP session, according to the "sendrecv"
MSRP-specific attribute negotiation rules in the corresponding
specifications.
A new SDP offer/answer MAY update the MSRP subprotocol attributes o defined in [RFC5547]: all the parameters related to MSRP file
while keeping the same subprotocol a=dcmap description. The transfer. See Section 5.2.
semantics for newly negotiated MSRP subprotocol attributes are per
[RFC4975].
5.1.1.3. Use of the setup Attribute A subsequent offer or answer MAY update the previously negotiated
MSRP subprotocol attributes while keeping the same subprotocol
a=dcmap description. The semantics for newly negotiated MSRP
subprotocol attributes are per [RFC4975].
A dsca embedded setup attribute, as defined in [RFC4145], MUST be 5.1.1.3. Use of the dcsa embedded setup Attribute
used for MSRP sessions over data channels. It is used to negotiate
which MSRP session endpoint assumes the active role as per As described in Section 5.1.1.2, the usage of a dsca embedded setup
Section 4.2.2 of [RFC6135] and Section 5.4 of [RFC4975]. It has no attribute is mandated for MSRP sessions over data channels. It is
relationship with the DTLS connection establishment roles. used to negotiate which MSRP session endpoint assumes the active role
as per Section 4.2.2 of [RFC6135] and Section 5.4 of [RFC4975]. It
has no relationship with the DTLS connection establishment roles
[I-D.ietf-mmusic-sctp-sdp].
The dcsa embedded setup attribute is of the form "a=dcsa:x The dcsa embedded setup attribute is of the form "a=dcsa:x
setup:<role>", with x being the data channel's SCTP stream setup:<role>", with x being the data channel's SCTP stream
identifier, so that such attribute is explicitly associated with an identifier, so that such attribute is explicitly associated with an
MSRP session over a specific data channel. MSRP session over a specific data channel.
It is considered an error if an MSRP over data channel description
does not contain a dcsa embedded setup attribute.
The SDP setup attribute can also be used in WebRTC data channel
related SDP media descriptions as a media level attribute, which is
associated with the corresponding UDP/DTLS/SCTP or TCP/DTLS/SCTP "m"
line. Such an "a=setup" attribute is used as specified in
[I-D.ietf-mmusic-sctp-sdp] in order to negotiate the establishment
roles of the DTLS connection and has no relationship with the MSRP
session.
5.1.1.4. Example SDP Negotiation 5.1.1.4. Example SDP Negotiation
The following is an example of an "m" line for data channels in an The following is an example of an "m" line for data channels in an
SDP offer that includes the attributes needed to establish two MSRP SDP offer that includes the attributes needed to establish two MSRP
sessions: one for chat and one for file transfer. The example is sessions: one for chat and one for file transfer. The example is
derived from a combination of examples in [RFC4975] and [RFC5547]. derived from a combination of examples in [RFC4975] and [RFC5547].
m=application 54111 UDP/DTLS/SCTP webrtc-datachannel m=application 54111 UDP/DTLS/SCTP webrtc-datachannel
c=IN IP4 198.51.100.79 c=IN IP4 198.51.100.79
a=max-message-size:100000 a=max-message-size:100000
a=sctp-port:5000 a=sctp-port:5000
a=setup:actpass a=setup:actpass
a=fingerprint:SHA-1 \ a=fingerprint:SHA-1 \
4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
a=tls-id:4a756565cddef001be82 a=tls-id:4a756565cddef001be82
a=dcmap:0 label="chat";subprotocol="MSRP" a=dcmap:0 label="chat";subprotocol="MSRP"
a=dcsa:0 msrp-cema
a=dcsa:0 setup:active a=dcsa:0 setup:active
a=dcsa:0 accept-types:message/cpim text/plain a=dcsa:0 accept-types:message/cpim text/plain
a=dcsa:0 path:msrps://bob.example.com:54111/si438dsaodes;dc a=dcsa:0 path:msrps://bob.example.com:54111/si438dsaodes;dc
a=dcmap:2 label="file transfer";subprotocol="MSRP" a=dcmap:2 label="file transfer";subprotocol="MSRP"
a=dcsa:2 sendonly a=dcsa:2 sendonly
a=dcsa:2 msrp-cema
a=dcsa:2 setup:active a=dcsa:2 setup:active
a=dcsa:2 accept-types:message/cpim a=dcsa:2 accept-types:message/cpim
a=dcsa:2 accept-wrapped-types:* a=dcsa:2 accept-wrapped-types:*
a=dcsa:2 path:msrps://bob.example.com:54111/jshA7we;dc a=dcsa:2 path:msrps://bob.example.com:54111/jshA7we;dc
a=dcsa:2 file-selector:name:"picture1.jpg" \ a=dcsa:2 file-selector:name:"picture1.jpg" \
type:image/jpeg size:1463440 hash:sha-1:\ type:image/jpeg size:1463440 hash:sha-1:\
FF:27:0D:81:14:F1:8A:C3:35:3B:36:64:2A:62:C9:3E:D3:6B:51:B4 FF:27:0D:81:14:F1:8A:C3:35:3B:36:64:2A:62:C9:3E:D3:6B:51:B4
a=dcsa:2 file-transfer-id:rjEtHAcYVZ7xKwGYpGGwyn5gqsSaU7Ep a=dcsa:2 file-transfer-id:rjEtHAcYVZ7xKwGYpGGwyn5gqsSaU7Ep
a=dcsa:2 file-disposition:attachment a=dcsa:2 file-disposition:attachment
a=dcsa:2 file-date:creation:"Mon, 12 Jan 2018 15:01:31 +0800" a=dcsa:2 file-date:creation:"Mon, 12 Jan 2018 15:01:31 +0800"
skipping to change at page 10, line 30 skipping to change at page 10, line 23
session over a data channel with a peer that does not support data session over a data channel with a peer that does not support data
channel transport in one of two ways. channel transport in one of two ways.
In one model, the gateway performs as a MSRP B2BUA to interwork all In one model, the gateway performs as a MSRP B2BUA to interwork all
the procedures as necessary between the endpoints. No further the procedures as necessary between the endpoints. No further
specification is needed for this model. specification is needed for this model.
Alternately, the gateway can use CEMA procedures to provide transport Alternately, the gateway can use CEMA procedures to provide transport
level interworking between MSRP endpoints using different transport level interworking between MSRP endpoints using different transport
protocols as follows. For example, if the gateway is implemented on protocols as follows. For example, if the gateway is implemented on
an Session Border Controller, it can use CEMA towars the inside an Session Border Controller, it can use CEMA towards the inside
network, using a non-data channel transport; but the gateway can not network, using a non-data channel transport; but the gateway can not
use CEMA towards endpoints using data channel transport. Path use CEMA towards endpoints using data channel transport. Path
attributes SHALL NOT be used for transport level interworking. attributes SHALL NOT be used for transport level interworking.
When the gateway performs transport level interworking between MSRP When the gateway performs transport level interworking between MSRP
endpoints, all of the procedures in Section 5 apply to each peer, endpoints, all of the procedures in Section 5 apply to each peer,
with the following additions: with the following additions:
o The endpoint establishing an MSRP session using data channel o The endpoint establishing an MSRP session using data channel
transport SHALL NOT request inclusion of any relays, although it transport SHALL NOT request inclusion of any relays, although it
skipping to change at page 12, line 35 skipping to change at page 12, line 24
9. Acknowledgments 9. Acknowledgments
The authors wish to acknowledge the borrowing of ideas from another The authors wish to acknowledge the borrowing of ideas from another
internet draft by Peter Dunkley and Gavin Llewellyn, and to thank internet draft by Peter Dunkley and Gavin Llewellyn, and to thank
Flemming Andreasen, Christian Groves, Christer Holmberg, Paul Flemming Andreasen, Christian Groves, Christer Holmberg, Paul
Kyzivat, Jonathan Lennox, Uwe Rauschenbach, Albrecht Schwarz and Kyzivat, Jonathan Lennox, Uwe Rauschenbach, Albrecht Schwarz and
Keith Drage for their invaluable comments. Keith Drage for their invaluable comments.
10. CHANGE LOG 10. CHANGE LOG
10.1. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-11' 10.1. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-12'
o Make CEMA mandatory, clarify SDP procedures.
10.2. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-11'
o Additional clarifications on cema and path attribute after mail o Additional clarifications on cema and path attribute after mail
list feedback. list feedback.
10.2. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-10' 10.3. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-10'
o Corrections and clarifications on cema and path attributes after o Corrections and clarifications on cema and path attributes after
mail list feedback. mail list feedback.
10.3. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-09' 10.4. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-09'
o Corrected area to ART. o Corrected area to ART.
10.4. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-08' 10.5. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-08'
o Updated reference to 4566bis. o Updated reference to 4566bis.
o Expanded motivation paragraphs in introduction. o Expanded motivation paragraphs in introduction.
10.5. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-07' 10.6. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-07'
o Move security considerations after IANA considerations, following o Move security considerations after IANA considerations, following
RFC7322 suggested order. RFC7322 suggested order.
o Update references to use xml.resource.org citation database. o Update references to use xml.resource.org citation database.
o Reformat of the section discussing setup parameter o Reformat of the section discussing setup parameter
o Align examples with latest [I-D.ietf-mmusic-data-channel-sdpneg] o Align examples with latest [I-D.ietf-mmusic-data-channel-sdpneg]
draft. draft.
o Edit section 6 for clarity. o Edit section 6 for clarity.
o Security requirements. o Security requirements.
o Clarify comment on unrecognized transports and session opening. o Clarify comment on unrecognized transports and session opening.
o Update year, add editor. o Update year, add editor.
10.6. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-06' 10.7. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-06'
o Modification of Keith's address information. o Modification of Keith's address information.
10.7. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-05' 10.8. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-05'
o Modification of Juergen's address information. o Modification of Juergen's address information.
10.8. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-04' 10.9. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-04'
o Addition of [I-D.ietf-mmusic-rfc4566bis] to list of normative o Addition of [I-D.ietf-mmusic-rfc4566bis] to list of normative
references. references.
o Addition of Section 7.2 as per section 8.2.4 of o Addition of Section 7.2 as per section 8.2.4 of
[I-D.ietf-mmusic-rfc4566bis]. [I-D.ietf-mmusic-rfc4566bis].
10.9. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-03' 10.10. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-03'
o Addition of IANA registration related Section 7.1. o Addition of IANA registration related Section 7.1.
10.10. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-02' 10.11. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-02'
o Addition of "a=setup:actpass", "a=connection:new", o Addition of "a=setup:actpass", "a=connection:new",
"a=fingerprint:..." and "a=dcsa:x setup=active" SDP attributes to "a=fingerprint:..." and "a=dcsa:x setup=active" SDP attributes to
the SDP example in Section 5.1.1.4. the SDP example in Section 5.1.1.4.
o Addition of [RFC4145] and [I-D.ietf-mmusic-sctp-sdp] to list of o Addition of [RFC4145] and [I-D.ietf-mmusic-sctp-sdp] to list of
normative references. normative references.
o Addition of new Section 5.1.1.3 describing how the active MSRP o Addition of new Section 5.1.1.3 describing how the active MSRP
session endpoint role is negotiated. session endpoint role is negotiated.
skipping to change at page 14, line 33 skipping to change at page 14, line 21
opened by the active MSRP endpoint which sends an MSRP SEND opened by the active MSRP endpoint which sends an MSRP SEND
message (empty or not) to the other MSRP endpoint." Replacement message (empty or not) to the other MSRP endpoint." Replacement
of this sentence with "As soon as this data channel is opened, the of this sentence with "As soon as this data channel is opened, the
MSRP session is actually opened by the active MSRP endpoint. In MSRP session is actually opened by the active MSRP endpoint. In
order to do this the active MSRP endpoint sends an MSRP SEND order to do this the active MSRP endpoint sends an MSRP SEND
message (empty or not) to the other MSRP endpoint." message (empty or not) to the other MSRP endpoint."
o Addition of setup attribute specific behavior descriptions of data o Addition of setup attribute specific behavior descriptions of data
channel to TCP or TLS interworking gateways in Section 6. channel to TCP or TLS interworking gateways in Section 6.
10.11. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-01' 10.12. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-01'
o In the abstract replacement of the first sentence "This document o In the abstract replacement of the first sentence "This document
specifies how the Message Session Relay Protocol (MSRP) can be specifies how the Message Session Relay Protocol (MSRP) can be
instantiated as a data channel sub-protocol, using the SDP offer/ instantiated as a data channel sub-protocol, using the SDP offer/
answer exchange-based external negotiation defined in answer exchange-based external negotiation defined in
[I-D.ietf-mmusic-data-channel-sdpneg]" with "This document [I-D.ietf-mmusic-data-channel-sdpneg]" with "This document
specifies how the Message Session Relay Protocol (MSRP) can be specifies how the Message Session Relay Protocol (MSRP) can be
instantiated as a data channel sub-protocol, using the SDP offer/ instantiated as a data channel sub-protocol, using the SDP offer/
answer exchange-based generic data channel negotiation framework" answer exchange-based generic data channel negotiation framework"
in order to remove the reference from the abstract text. in order to remove the reference from the abstract text.
skipping to change at page 16, line 7 skipping to change at page 15, line 41
procedure defined in [I-D.ietf-mmusic-data-channel-sdpneg]." with procedure defined in [I-D.ietf-mmusic-data-channel-sdpneg]." with
'The closure of an MSRP session MUST be signaled via an SDP offer/ 'The closure of an MSRP session MUST be signaled via an SDP offer/
answer exchange which removes the "a=dcmap:" and "a=dcsa:" answer exchange which removes the "a=dcmap:" and "a=dcsa:"
attribute lines associated with the MSRP session from the attribute lines associated with the MSRP session from the
associated DTLS/SCTP based media description. This results in the associated DTLS/SCTP based media description. This results in the
associated data channel being closed as well as per associated data channel being closed as well as per
[I-D.ietf-mmusic-data-channel-sdpneg], where the actual data [I-D.ietf-mmusic-data-channel-sdpneg], where the actual data
channel closure procedure is typically initiated by the SDP channel closure procedure is typically initiated by the SDP
answerer right after having accepted the SDP offer.'. answerer right after having accepted the SDP offer.'.
10.12. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-00' 10.13. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-00'
o Additional reference to [I-D.ietf-mmusic-data-channel-sdpneg] in o Additional reference to [I-D.ietf-mmusic-data-channel-sdpneg] in
list of normative references. list of normative references.
o Replacement of previous document title "MSRP over SCTP/DTLS data o Replacement of previous document title "MSRP over SCTP/DTLS data
channels" with "MSRP over Data Channels" in order to align with channels" with "MSRP over Data Channels" in order to align with
the terminology used in [I-D.ietf-mmusic-data-channel-sdpneg]. the terminology used in [I-D.ietf-mmusic-data-channel-sdpneg].
o In Section 3 "WebRTC data channel" was defined as "A bidirectional o In Section 3 "WebRTC data channel" was defined as "A bidirectional
channel consisting of paired SCTP outbound and inbound streams." channel consisting of paired SCTP outbound and inbound streams."
skipping to change at page 16, line 39 skipping to change at page 16, line 24
o In the gateway configuration section (Section 6) replacement of o In the gateway configuration section (Section 6) replacement of
the first sentence "This section describes the network the first sentence "This section describes the network
configuration where one endpoint runs MSRP over a WebRTC SCTP/DTLS configuration where one endpoint runs MSRP over a WebRTC SCTP/DTLS
connection, the other MSRP endpoint runs MSRP over one or more connection, the other MSRP endpoint runs MSRP over one or more
TLS/TCP connections, and the two endpoints interwork via an MSRP TLS/TCP connections, and the two endpoints interwork via an MSRP
gateway" with "This section describes the network configuration gateway" with "This section describes the network configuration
where one MSRP endpoint uses data channels as MSRP transport, the where one MSRP endpoint uses data channels as MSRP transport, the
other MSRP endpoint uses TLS/TCP connections as MSRP transport, other MSRP endpoint uses TLS/TCP connections as MSRP transport,
and the two MSRP endpoints interwork via an MSRP gateway". and the two MSRP endpoints interwork via an MSRP gateway".
10.13. Changes against 'draft-ejzak-mmusic-msrp-usage-data-channel-01' 10.14. Changes against 'draft-ejzak-mmusic-msrp-usage-data-channel-01'
o Removed empty spaces after ";" in the examples' "a=dcmap" o Removed empty spaces after ";" in the examples' "a=dcmap"
attribute lines. attribute lines.
o In all examples, the "m" line proto value "DTLS/SCTP" was replaced o In all examples, the "m" line proto value "DTLS/SCTP" was replaced
with "UDP/DTLS/SCTP" and the "a=fmtp" attribute lines were with "UDP/DTLS/SCTP" and the "a=fmtp" attribute lines were
replaced with "a=max-message-size" attribute lines, as per draft- replaced with "a=max-message-size" attribute lines, as per draft-
ietf-mmusic-sctp-sdp-12. ietf-mmusic-sctp-sdp-12.
10.14. Changes against '-00' 10.15. Changes against '-00'
o Transport parameter change for MSRP to allow MSRP RFC transports. o Transport parameter change for MSRP to allow MSRP RFC transports.
o Clarification on SDP offer/answer and removing duplicated o Clarification on SDP offer/answer and removing duplicated
procedures and refer them to draft-ejzak-mmusic-data-channel- procedures and refer them to draft-ejzak-mmusic-data-channel-
sdpneg-02. sdpneg-02.
11. Normative References 11. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 19, line 4 skipping to change at page 18, line 39
Transport for the Message Session Relay Protocol (MSRP)", Transport for the Message Session Relay Protocol (MSRP)",
RFC 7977, DOI 10.17487/RFC7977, September 2016, RFC 7977, DOI 10.17487/RFC7977, September 2016,
<https://www.rfc-editor.org/info/rfc7977>. <https://www.rfc-editor.org/info/rfc7977>.
Authors' Addresses Authors' Addresses
Keith Drage (editor) Keith Drage (editor)
Unaffiliated Unaffiliated
Email: drageke@ntlworld.com Email: drageke@ntlworld.com
Maridi R. Makaraju (Raju) Maridi R. Makaraju (Raju)
Unaffiliated Unaffiliated
Email: mmraju@gmail.com Email: mmraju@gmail.com
Juergen Stoetzer-Bradler Juergen Stoetzer-Bradler
Unaffiliated Unaffiliated
Email: Juergen.S-B.ietf@email.de Email: Juergen.S-B.ietf@email.de
Richard Ejzak Richard Ejzak
Unaffiliated Unaffiliated
Email: richard.ejzak@gmail.com Email: richard.ejzak@gmail.com
Jerome Marcon Jerome Marcon
Unaffiliated Unaffiliated
Jose M. Recio (editor) Jose M. Recio (editor)
CoSMo Software
Email: jose@ch3m4.com Email: jose@ch3m4.com
 End of changes. 57 change blocks. 
97 lines changed or deleted 99 lines changed or added

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