draft-ietf-mmusic-msrp-usage-data-channel-10.txt   draft-ietf-mmusic-msrp-usage-data-channel-11.txt 
MMUSIC K. Drage, Ed. MMUSIC K. Drage, Ed.
Internet-Draft Unaffiliated Internet-Draft Unaffiliated
Intended status: Standards Track M. Makaraju Intended status: Standards Track M. Makaraju
Expires: October 23, 2019 Nokia Expires: December 3, 2019 Nokia
J. Stoetzer-Bradler J. Stoetzer-Bradler
R. Ejzak R. Ejzak
J. Marcon J. Marcon
Unaffiliated Unaffiliated
J. Recio, Ed. J. Recio, Ed.
CoSMo Software CoSMo Software
April 21, 2019 June 1, 2019
MSRP over Data Channels MSRP over Data Channels
draft-ietf-mmusic-msrp-usage-data-channel-10 draft-ietf-mmusic-msrp-usage-data-channel-11
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 43 skipping to change at page 1, line 43
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 October 23, 2019. This Internet-Draft will expire on December 3, 2019.
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 26 skipping to change at page 2, line 26
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 . . . . . . . . . . . . . . . . . . . 5 5.1. Basic MSRP Support . . . . . . . . . . . . . . . . . . . 6
5.1.1. Session Negotiation . . . . . . . . . . . . . . . . . 6 5.1.1. Session Negotiation . . . . . . . . . . . . . . . . . 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 setup Attribute . . . . . . . . . . . 7
5.1.1.4. Example SDP Negotiation . . . . . . . . . . . . . 8 5.1.1.4. Example SDP Negotiation . . . . . . . . . . . . . 8
5.1.2. Session Opening . . . . . . . . . . . . . . . . . . . 8 5.1.2. Session Opening . . . . . . . . . . . . . . . . . . . 8
5.1.3. Data Framing . . . . . . . . . . . . . . . . . . . . 9 5.1.3. Data Framing . . . . . . . . . . . . . . . . . . . . 9
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-09' . . . . . . . . . . . . . . . . . . . . . . 12 channel-10' . . . . . . . . . . . . . . . . . . . . . . 12
10.2. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.2. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-08' . . . . . . . . . . . . . . . . . . . . . . 12 channel-09' . . . . . . . . . . . . . . . . . . . . . . 12
10.3. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.3. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-07' . . . . . . . . . . . . . . . . . . . . . . 12 channel-08' . . . . . . . . . . . . . . . . . . . . . . 12
10.4. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.4. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-06' . . . . . . . . . . . . . . . . . . . . . . 13 channel-07' . . . . . . . . . . . . . . . . . . . . . . 13
10.5. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.5. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-05' . . . . . . . . . . . . . . . . . . . . . . 13 channel-06' . . . . . . . . . . . . . . . . . . . . . . 13
10.6. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.6. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-04' . . . . . . . . . . . . . . . . . . . . . . 13 channel-05' . . . . . . . . . . . . . . . . . . . . . . 13
10.7. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.7. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-03' . . . . . . . . . . . . . . . . . . . . . . 13 channel-04' . . . . . . . . . . . . . . . . . . . . . . 13
10.8. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.8. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-02' . . . . . . . . . . . . . . . . . . . . . . 13 channel-03' . . . . . . . . . . . . . . . . . . . . . . 13
10.9. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.9. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-01' . . . . . . . . . . . . . . . . . . . . . . 14 channel-02' . . . . . . . . . . . . . . . . . . . . . . 13
10.10. Changes against 'draft-ietf-mmusic-msrp-usage-data- 10.10. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-01' . . . . . . . . . . . . . . . . . . . . . . 14
10.11. Changes against 'draft-ietf-mmusic-msrp-usage-data-
channel-00' . . . . . . . . . . . . . . . . . . . . . . 15 channel-00' . . . . . . . . . . . . . . . . . . . . . . 15
10.11. Changes against 'draft-ejzak-mmusic-msrp-usage-data- 10.12. Changes against 'draft-ejzak-mmusic-msrp-usage-data-
channel-01' . . . . . . . . . . . . . . . . . . . . . . 16 channel-01' . . . . . . . . . . . . . . . . . . . . . . 16
10.12. Changes against '-00' . . . . . . . . . . . . . . . . . 16 10.13. Changes against '-00' . . . . . . . . . . . . . . . . . 16
11. Normative References . . . . . . . . . . . . . . . . . . . . 16 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 a WebSocket subprotocol specified over TCP and TLS connections, and over a WebSocket subprotocol
by [RFC4975]. specified by [RFC7977].
This document defines the negotiation and transport of this MSRP This document defines the negotiation and transport of this MSRP
protocol over data channels, where a data channel is a bi-directional protocol over data channels, where a data channel is a bi-directional
communication channel running on top of SCTP/DTLS (as per communication channel running on top of SCTP/DTLS (as per
[I-D.ietf-rtcweb-data-channel]) and where MSRP is instantiated as a [I-D.ietf-rtcweb-data-channel]) and where MSRP is instantiated as a
sub-protocol of this data channel. The MSRP protocol negotiation sub-protocol of this data channel. The MSRP protocol negotiation
defined in this document is based on the generic SDP offer/answer defined in this document is based on the generic SDP offer/answer
exchange based data channel negotiation as specified in exchange based data channel negotiation as specified in
[I-D.ietf-mmusic-data-channel-sdpneg]. [I-D.ietf-mmusic-data-channel-sdpneg].
skipping to change at page 7, line 4 skipping to change at page 7, line 6
The MSRP-specific items that can be negotiated include at least all The MSRP-specific items that can be negotiated include at least all
of the following well-known attributes: of the following well-known attributes:
o defined in [RFC4975]: "path", "accept-types", "accept-wrapped- o defined in [RFC4975]: "path", "accept-types", "accept-wrapped-
types", "max-size" types", "max-size"
o defined in [RFC4566]: "sendonly", "recvonly", "inactive", and o defined in [RFC4566]: "sendonly", "recvonly", "inactive", and
"sendrecv" "sendrecv"
o defined in [RFC6135]: "setup" o defined in [RFC6135]: "setup"
o defined in [RFC6714]: "msrp-cema"
o defined in [RFC5547]: all the parameters related to MSRP file o defined in [RFC5547]: all the parameters related to MSRP file
transfer. See Section 5.2. transfer. See Section 5.2.
The msrp-cema attribute SHALL be assumed to be present for every MSRP This document describes directly connecting to a data channel
session using data channel transport, so the inclusion of the msrp- endpoint that is either a MSRP endpoint or an MSRP GW, as a result
cema attribute is OPTIONAL. This ensures that the data channel MSRP Connection Establishment for Media Anchoring (MSRP-CEMA)
transport for the MSRP session is established without using the path [RFC6714] is outside of the scope of this document. The msrp-cema
attribute. attribute SHALL NOT be present.
As described in Section 5.1.2 the path attribute is not used for
transport establiment.
The SDP answer SHALL include zero or more corresponding dcsa The SDP answer SHALL include zero or more corresponding dcsa
attribute lines for each negotiated MSRP session, according to the attribute lines for each negotiated MSRP session, according to the
MSRP-specific attribute negotiation rules in the corresponding MSRP-specific attribute negotiation rules in the corresponding
specifications. specifications.
A new SDP offer/answer MAY update the MSRP subprotocol attributes A new SDP offer/answer MAY update the MSRP subprotocol attributes
while keeping the same subprotocol a=dcmap description. The while keeping the same subprotocol a=dcmap description. The
semantics for newly negotiated MSRP subprotocol attributes are per semantics for newly negotiated MSRP subprotocol attributes are per
[RFC4975]. [RFC4975].
skipping to change at page 8, line 42 skipping to change at page 8, line 42
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"
a=dcsa:2 file-icon:cid:id2@bob.example.com a=dcsa:2 file-icon:cid:id2@bob.example.com
a=dcsa:2 file-range:1-1463440 a=dcsa:2 file-range:1-1463440
5.1.2. Session Opening 5.1.2. Session Opening
Section 5.1.1.3 describes how the active MSRP session endpoint role Section 5.1.1.3 describes how the active MSRP session endpoint role
is negotiated. The active MSRP session endpoint does not use the is negotiated. The active MSRP session endpoint uses the data
path attribute to open a transport connection to its peer. Instead, channel established for this MSRP session by the generic data channel
it uses the data channel established for this MSRP session by the opening procedure defined in [I-D.ietf-mmusic-data-channel-sdpneg].
generic data channel opening procedure defined in The path attribute SHALL NOT be used for transport negotiation.
[I-D.ietf-mmusic-data-channel-sdpneg].
As soon as this data channel is opened, the MSRP session is actually As soon as this data channel is opened, the MSRP session is actually
opened by the active MSRP session endpoint. In order to do this the opened by the active MSRP session endpoint. In order to do this the
active MSRP endpoint sends an MSRP SEND message (empty or not) to the active MSRP endpoint sends an MSRP SEND message (empty or not) to the
other MSRP endpoint. The msrp-cema attribute is implicitly other MSRP endpoint.
associated with every MSRP session using data channel transport.
5.1.3. Data Framing 5.1.3. Data Framing
Each text-based MSRP message is sent on the corresponding SCTP stream Each text-based MSRP message is sent on the corresponding SCTP stream
using standard MSRP framing and chunking procedures, as defined in using standard MSRP framing and chunking procedures, as defined in
[RFC4975], with each MSRP chunk delivered in a single SCTP user [RFC4975], with each MSRP chunk delivered in a single SCTP user
message. Therefore all sent MSRP chunks including the MSRP chunk message. Therefore all sent MSRP chunks including the MSRP chunk
header MUST have lengths of less than or equal to the value of the header MUST have lengths of less than or equal to the value of the
peer's "a=max-message-size" attribute, which is associated with the peer's "a=max-message-size" attribute, which is associated with the
data channel's SCTP association. data channel's SCTP association.
skipping to change at page 10, line 29 skipping to change at page 10, line 29
Specifically, a gateway can be configured to interwork an MSRP Specifically, a gateway can be configured to interwork an MSRP
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. protocols as follows. Path 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
MAY interoperate with a peer that signals the use of relays. MAY interoperate with a peer that signals the use of relays.
o The gateway receiving an SDP offer that includes a request to o The gateway receiving an SDP offer that includes a request to
skipping to change at page 12, line 24 skipping to change at page 12, line 35
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-09' 10.1. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-10'
o Corrections and clarifications on cema and path attributes after
mail list feedback.
10.2. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-09'
o Corrected area to ART. o Corrected area to ART.
10.2. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-08' 10.3. 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.3. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-07' 10.4. 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.4. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-06' 10.5. 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.5. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-05' 10.6. 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.6. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-04' 10.7. 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.7. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-03' 10.8. 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.8. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-02' 10.9. 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 5 skipping to change at page 14, line 24
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.9. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-01' 10.10. 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 15, line 26 skipping to change at page 15, line 43
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.10. Changes against 'draft-ietf-mmusic-msrp-usage-data-channel-00' 10.11. 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 9 skipping to change at page 16, line 28
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.11. Changes against 'draft-ejzak-mmusic-msrp-usage-data-channel-01' 10.12. 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.12. Changes against '-00' 10.13. 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 17, line 13 skipping to change at page 17, line 28
protocol-09 (work in progress), January 2015. protocol-09 (work in progress), January 2015.
[I-D.ietf-rtcweb-data-channel] [I-D.ietf-rtcweb-data-channel]
Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data
Channels", draft-ietf-rtcweb-data-channel-13 (work in Channels", draft-ietf-rtcweb-data-channel-13 (work in
progress), January 2015. progress), January 2015.
[I-D.ietf-mmusic-data-channel-sdpneg] [I-D.ietf-mmusic-data-channel-sdpneg]
Drage, K., Makaraju, M., Ejzak, R., Marcon, J., and R. Drage, K., Makaraju, M., Ejzak, R., Marcon, J., and R.
Even, "SDP-based Data Channel Negotiation", draft-ietf- Even, "SDP-based Data Channel Negotiation", draft-ietf-
mmusic-data-channel-sdpneg-25 (work in progress), March mmusic-data-channel-sdpneg-28 (work in progress), May
2019. 2019.
[I-D.ietf-mmusic-sctp-sdp] [I-D.ietf-mmusic-sctp-sdp]
Holmberg, C., Shpount, R., Loreto, S., and G. Camarillo, Holmberg, C., Shpount, R., Loreto, S., and G. Camarillo,
"Session Description Protocol (SDP) Offer/Answer "Session Description Protocol (SDP) Offer/Answer
Procedures For Stream Control Transmission Protocol (SCTP) Procedures For Stream Control Transmission Protocol (SCTP)
over Datagram Transport Layer Security (DTLS) Transport.", over Datagram Transport Layer Security (DTLS) Transport.",
draft-ietf-mmusic-sctp-sdp-26 (work in progress), April draft-ietf-mmusic-sctp-sdp-26 (work in progress), April
2017. 2017.
skipping to change at page 17, line 36 skipping to change at page 17, line 51
DOI 10.17487/RFC4145, September 2005, DOI 10.17487/RFC4145, September 2005,
<https://www.rfc-editor.org/info/rfc4145>. <https://www.rfc-editor.org/info/rfc4145>.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, DOI 10.17487/RFC4566, Description Protocol", RFC 4566, DOI 10.17487/RFC4566,
July 2006, <https://www.rfc-editor.org/info/rfc4566>. July 2006, <https://www.rfc-editor.org/info/rfc4566>.
[I-D.ietf-mmusic-rfc4566bis] [I-D.ietf-mmusic-rfc4566bis]
Begen, A., Kyzivat, P., Perkins, C., and M. Handley, "SDP: Begen, A., Kyzivat, P., Perkins, C., and M. Handley, "SDP:
Session Description Protocol", draft-ietf-mmusic- Session Description Protocol", draft-ietf-mmusic-
rfc4566bis-34 (work in progress), March 2019. rfc4566bis-35 (work in progress), May 2019.
[RFC4975] Campbell, B., Ed., Mahy, R., Ed., and C. Jennings, Ed., [RFC4975] Campbell, B., Ed., Mahy, R., Ed., and C. Jennings, Ed.,
"The Message Session Relay Protocol (MSRP)", RFC 4975, "The Message Session Relay Protocol (MSRP)", RFC 4975,
DOI 10.17487/RFC4975, September 2007, DOI 10.17487/RFC4975, September 2007,
<https://www.rfc-editor.org/info/rfc4975>. <https://www.rfc-editor.org/info/rfc4975>.
[RFC5547] Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S., [RFC5547] Garcia-Martin, M., Isomaki, M., Camarillo, G., Loreto, S.,
and P. Kyzivat, "A Session Description Protocol (SDP) and P. Kyzivat, "A Session Description Protocol (SDP)
Offer/Answer Mechanism to Enable File Transfer", RFC 5547, Offer/Answer Mechanism to Enable File Transfer", RFC 5547,
DOI 10.17487/RFC5547, May 2009, DOI 10.17487/RFC5547, May 2009,
skipping to change at page 18, line 11 skipping to change at page 18, line 27
for the Message Session Relay Protocol (MSRP)", RFC 6135, for the Message Session Relay Protocol (MSRP)", RFC 6135,
DOI 10.17487/RFC6135, February 2011, DOI 10.17487/RFC6135, February 2011,
<https://www.rfc-editor.org/info/rfc6135>. <https://www.rfc-editor.org/info/rfc6135>.
[RFC6714] Holmberg, C., Blau, S., and E. Burger, "Connection [RFC6714] Holmberg, C., Blau, S., and E. Burger, "Connection
Establishment for Media Anchoring (CEMA) for the Message Establishment for Media Anchoring (CEMA) for the Message
Session Relay Protocol (MSRP)", RFC 6714, Session Relay Protocol (MSRP)", RFC 6714,
DOI 10.17487/RFC6714, August 2012, DOI 10.17487/RFC6714, August 2012,
<https://www.rfc-editor.org/info/rfc6714>. <https://www.rfc-editor.org/info/rfc6714>.
[RFC7977] Dunkley, P., Llewellyn, G., Pascual, V., Salgueiro, G.,
and R. Ravindranath, "The WebSocket Protocol as a
Transport for the Message Session Relay Protocol (MSRP)",
RFC 7977, DOI 10.17487/RFC7977, September 2016,
<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)
Nokia Nokia
2000 Lucent Lane 2000 Lucent Lane
 End of changes. 38 change blocks. 
46 lines changed or deleted 60 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/