"MSRP协议规范RFC4975下载指南" 资源-CSDN下载

3星 · 超过75%的资源需积分: 50 179 浏览量 2014-06-18 22:46:38 上传评论收藏 90KB PDF 举报

MSRP（Message Session Relay Protocol，消息会话中继协议）是一种用于互联网社区的协议，于2007年9月由Estacado Systems的B. Campbell、Plantronics的R. Mahy以及CiscoSystems,Inc.的C. Jennings共同发布，文档编号RFC4975。MSRP在即时消息（Instant Messaging，IM）场景中提供了一种可靠的消息传输机制，允许通过会话传递一系列相关的即时消息。这种协议将消息会话视为媒体流处理，在通过诸如会话启动协议（Session Initiation Protocol，SIP）这样的集合或会话创建协议进行设置时，消息会话被看作与其他任何媒体流一样。 MSRP协议规范RFC4975详细定义了该协议的标准，它为互联网社区制定了一个标准跟踪协议，并请求讨论和改进意见。RFC4975包含11个主要章节，每章讨论了MSRP协议的不同方面和功能。 1. 引言部分简要介绍了MSRP协议的背景和用途。 2. 规范约定部分描述了文档中使用的约定和缩写。 3. MSRP适用范围部分说明了MSRP协议的应用场景和适用环境。 4. 协议概述部分为读者提供了一个关于MSRP如何工作的高级概述。 5. 关键概念部分包括MSRP的帧、寻址、事务和报告模型以及连接模型。 6. MSRP URI部分讨论了MSRP URI的格式、比较和解析。 7. 方法特定行为部分详述了请求和响应的构造，包括SEND请求、REPORT请求以及成功和失败报告的生成。 8. 使用MSRP与SIP和SDP结合使用部分描述了与会话描述协议（Session Description Protocol，SDP）一起使用MSRP的具体方法，包括SDP连接和媒体线路、URI协商、路径属性、SDP更新提议等。 9. 正式语法部分定义了MSRP协议的语法。 10. 响应码描述部分详细说明了MSRP协议中各种响应码（如200、400、403、408、413、415、423、481、501、506）的具体含义。 11. 示例部分提供了MSRP协议使用的实例，如基本即时消息会话。 MSRP协议主要为了解决即时消息交换过程中的消息可靠性和中继服务。MSRP通过在SIP会话中创建媒体流来实现消息的发送和接收。在MSRP中，会话被视为一条信息流，其中消息可以是多个部分中的一个，这种设计使得MSRP特别适合于需要传输大消息或长消息的场景。MSRP利用TCP和SCTP协议进行传输，并能够在两个或多个参与者之间创建稳定的消息传输会话。MSRP传输的每个消息都会被分配一个唯一的事务ID，以区分各个独立的消息。 MSRP协议的主要特点包括消息的可靠传输、支持长消息的分段传输、支持SIP和SDP的集成使用。此外，MSRP也支持对消息传输的控制，如向消息的发送者报告传输的成功或失败。在实际应用中，MSRP的使用使得即时消息的传输更加稳定和可靠，特别是在复杂的网络环境中。 MSRP协议的发展和优化是一个持续的过程，RFC4975作为最新的标准规范，为开发者提供了关于MSRP协议的详细说明和实现指导。随着即时消息通信技术的发展，MSRP协议在企业通信、互联网实时消息服务等领域具有广泛的应用前景。对于希望深入学习和掌握MSRP协议的人员来说，RFC4975是一个重要的参考文档。

资源推荐

资源详情

资源评论

Network Working Group B. Campbell, Ed.

Request for Comments: 4975 Estacado Systems

Category: Standards Track R. Mahy, Ed.

Plantronics

C. Jennings, Ed.

Cisco Systems, Inc.

September 2007

The Message Session Relay Protocol (MSRP)

Status of This Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Abstract

This document describes the Message Session Relay Protocol, a

protocol for transmitting a series of related instant messages in the

context of a session. Message sessions are treated like any other

media stream when set up via a rendezvous or session creation

protocol such as the Session Initiation Protocol.

Campbell, et al. Standards Track [Page 1]

RFC 4975 MSRP September 2007

Table of Contents

1. Introduction ....................................................4

2. Conventions .....................................................5

3. Applicability of MSRP ...........................................5

4. Protocol Overview ...............................................6

5. Key Concepts ....................................................9

5.1. MSRP Framing and Message Chunking ..........................9

5.2. MSRP Addressing ...........................................10

5.3. MSRP Transaction and Report Model .........................11

5.4. MSRP Connection Model .....................................12

6. MSRP URIs ......................................................14

6.1. MSRP URI Comparison .......................................15

6.2. Resolving MSRP Host Device ................................16

7. Method-Specific Behavior .......................................17

7.1. Constructing Requests .....................................17

7.1.1. Sending SEND Requests ..............................18

7.1.2. Sending REPORT Requests ............................21

7.1.3. Generating Success Reports .........................22

7.1.4. Generating Failure Reports .........................23

7.2. Constructing Responses ....................................24

7.3. Receiving Requests ........................................25

7.3.1. Receiving SEND Requests ............................25

7.3.2. Receiving REPORT Requests ..........................27

8. Using MSRP with SIP and SDP ....................................27

8.1. SDP Connection and Media-Lines ............................28

8.2. URI Negotiations ..........................................29

8.3. Path Attributes with Multiple URIs ........................30

8.4. Updated SDP Offers ........................................31

8.5. Connection Negotiation ....................................31

8.6. Content Type Negotiation ..................................32

8.7. Example SDP Exchange ......................................34

8.8. MSRP User Experience with SIP .............................35

8.9. SDP Direction Attribute and MSRP ..........................35

9. Formal Syntax ..................................................36

10. Response Code Descriptions ....................................38

10.1. 200 ......................................................38

10.2. 400 ......................................................38

10.3. 403 ......................................................38

10.4. 408 ......................................................39

10.5. 413 ......................................................39

10.6. 415 ......................................................39

10.7. 423 ......................................................39

10.8. 481 ......................................................39

10.9. 501 ......................................................39

10.10. 506 .....................................................40

Campbell, et al. Standards Track [Page 2]

RFC 4975 MSRP September 2007

11. Examples ......................................................40

11.1. Basic IM Session .........................................40

11.2. Message with XHTML Content ...............................42

11.3. Chunked Message ..........................................43

11.4. Chunked Message with Message/CPIM Payload ................43

11.5. System Message ...........................................44

11.6. Positive Report ..........................................44

11.7. Forked IM ................................................45

12. Extensibility .................................................48

13. CPIM Compatibility ............................................48

14. Security Considerations .......................................49

14.1. Secrecy of the MSRP URI ..................................50

14.2. Transport Level Protection ...............................50

14.3. S/MIME ...................................................51

14.4. Using TLS in Peer-to-Peer Mode ...........................52

14.5. Other Security Concerns ..................................53

15. IANA Considerations ...........................................55

15.1. MSRP Method Names ........................................55

15.2. MSRP Header Fields .......................................55

15.3. MSRP Status Codes ........................................56

15.4. MSRP Port ................................................56

15.5. URI Schema ...............................................56

15.5.1. MSRP Scheme .......................................56

15.5.2. MSRPS Scheme ......................................57

15.6. SDP Transport Protocol ...................................57

15.7. SDP Attribute Names ......................................58

15.7.1. Accept Types ......................................58

15.7.2. Wrapped Types .....................................58

15.7.3. Max Size ..........................................58

15.7.4. Path ..............................................58

16. Contributors and Acknowledgments ..............................59

17. References ....................................................59

17.1. Normative References .....................................59

17.2. Informative References ...................................60

Campbell, et al. Standards Track [Page 3]

RFC 4975 MSRP September 2007

1. Introduction

A series of related instant messages between two or more parties can

be viewed as part of a "message session", that is, a conversational

exchange of messages with a definite beginning and end. This is in

contrast to individual messages each sent independently. Messaging

schemes that track only individual messages can be described as

"page-mode" messaging, whereas messaging that is part of a "session"

with a definite start and end is called "session-mode" messaging.

Page-mode messaging is enabled in SIP via the SIP [4] MESSAGE method

[22]. Session-mode messaging has a number of benefits over page-mode

messaging, however, such as explicit rendezvous, tighter integration

with other media-types, direct client-to-client operation, and

brokered privacy and security.

This document defines a session-oriented instant message transport

protocol called the Message Session Relay Protocol (MSRP), whose

sessions can be negotiated with an offer or answer [3] using the

Session Description Protocol (SDP) [2]. The exchange is carried by

some signaling protocol, such as SIP [4]. This allows a

communication user agent to offer a messaging session as one of the

possible media-types in a session. For instance, Alice may want to

communicate with Bob. Alice doesn’t know at the moment whether Bob

has his phone or his IM client handy, but she’s willing to use

either. She sends an invitation to a session to the address of

record she has for Bob, sip:[email protected]. Her invitation offers

both voice and an IM session. The SIP services at example.com

forward the invitation to Bob at his currently registered clients.

Bob accepts the invitation at his IM client, and they begin a

threaded chat conversation.

When a user uses an Instant Messaging (IM) URL, RFC 3861 [32] defines

how DNS can be used to map this to a particular protocol to establish

the session such as SIP. SIP can use an offer/answer model to

transport the MSRP URIs for the media in SDP. This document defines

how the offer/answer exchange works to establish MSRP connections and

how messages are sent across the MSRP, but it does not deal with the

issues of mapping an IM URL to a session establishment protocol.

This session model allows message sessions to be integrated into

advanced communications applications with little to no additional

protocol development. For example, during the above chat session,

Bob decides Alice really needs to be talking to Carol. Bob can

transfer [21] Alice to Carol, introducing them into their own

messaging session. Messaging sessions can then be easily integrated

into call-center and dispatch environments using third-party call

control [20] and conferencing [19] applications.

Campbell, et al. Standards Track [Page 4]

RFC 4975 MSRP September 2007

This document specifies MSRP behavior only for peer-to-peer sessions,

that is, sessions crossing only a single hop. MSRP relay devices

[23] (referred to herein as "relays") are specified in a separate

document. An endpoint that implements this specification, but not

the relay specification, will be unable to introduce relays into the

message path, but will still be able to interoperate with peers that

do use relays.

2. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in RFC 2119 [5].

This document consistently refers to a "message" as a complete unit

of MIME or text content. In some cases, a message is split and

delivered in more than one MSRP request. Each of these portions of

the complete message is called a "chunk".

3. Applicability of MSRP

MSRP is not designed for use as a standalone protocol. MSRP MUST be

used only in the context of a rendezvous mechanism meeting the

following requirements:

o The rendezvous mechanism MUST provide both MSRP URIs associated

with an MSRP session to each of the participating endpoints. The

rendezvous mechanism MUST implement mechanisms to protect the

confidentiality of these URIs -- they MUST NOT be made available

to an untrusted third party or be easily discoverable.

o The rendezvous mechanism MUST provide mechanisms for the

negotiation of any supported MSRP extensions that are not

backwards compatible.

o The rendezvous mechanism MUST be able to natively transport im:

URIs or automatically translate im: URIs [27] into the addressing

identifiers of the rendezvous protocol.

To use a rendezvous mechanism with MSRP, an RFC MUST be prepared that

describes how it exchanges MSRP URIs and meets these requirements

listed here. This document provides such a description for the use

of MSRP in the context of SIP and SDP.

SIP meets these requirements for a rendezvous mechanism. The MSRP

URIs are exchanged using SDP in an offer/answer exchange via SIP.

Campbell, et al. Standards Track [Page 5]

剩余62页未读，继续阅读

评论收藏

内容反馈

zjhhailang

2014-11-18

要是有代码例子就好了
sinat_21323379

2014-09-26

很好，很有用！

zmh826596143

粉丝: 0

msrp协议规范

最新资源

msrp协议规范

MSRP_协议的分析、设计与实现.pdf

msrp文件源码

英文文本相似度/文本推理/文本匹配数据集——MSRP

基于SIP的msrp协议文件传输说明.doc

MSRP协议培训PPT

libMSRP (Confiance)-开源

LCQMC数据集.tar.gz

MSRP.zip_SIP Client MSRP_msrp_msrp sip_sip_sip msrp

RCS 5.1协议

MSRP-rfc4975.pdf

句子相似度评估数据集

语义相似度任务-LCQMC数据集下载lcqmc.zip

微软亚洲研究院语料库

RCS 6.0协议英文原版

MSRP for IMS-开源

SIP AND MSRP OVER WEBSOCKET

Protocol(MSRP).rar_Java编程_Java_

一个新型分布式无线传感器分层路由协议.pdf

opensips，asterisk，msrp，mediaproxy

imsdroid源码

基于多波长SRP的分布式WDM光网络光路建立研究.pdf

Spring2.5 and GWT 集成 --实现分页查询功能

直控零售协议（DOC格式）

Cisco Catalyst 3850系列交换机配置指南（适用IOS16.3.x）

基于IMS的远程多线程PGM研究与实现参考文献

人际交往与心理健康

WP_Evaluation_Agreement.doc

22-06-24 西安 linux（01） linux环境搭建、常用命令、vim编辑

openWRT中集成easyCWMP

最新资源