Network Working Group E. O'Tuathail
Request for Comments: 3288 Clipcode.com
Category: Standards Track M. Rose
Dover Beach Consulting, Inc.
June 2002
Network Working Group E. O'Tuathail
Request for Comments: 3288 Clipcode.com
Category: Standards Track M. Rose
Dover Beach Consulting, Inc.
June 2002
Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)
在块中使用简单对象访问协议（SOAP）可扩展交换协议（BEEP）
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.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This memo specifies a Simple Object Access Protocol (SOAP) binding to the Blocks Extensible Exchange Protocol core (BEEP). A SOAP binding describes how SOAP messages are transmitted in the network.
此备忘录指定绑定到块可扩展交换协议核心（BEEP）的简单对象访问协议（SOAP）。SOAP绑定描述了SOAP消息在网络中的传输方式。
The SOAP is an XML-based (extensible markup language) messaging protocol used to implement a wide variety of distributed messaging models. It defines a message format and describes a variety of message patterns, including, but not limited to, RPC, asynchronous event notification, unacknowledged messages, and forwarding via SOAP intermediaries.
SOAP是一种基于XML（可扩展标记语言）的消息传递协议，用于实现各种分布式消息传递模型。它定义了一种消息格式并描述了各种消息模式，包括但不限于RPC、异步事件通知、未确认消息和通过SOAP中介进行转发。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. BEEP Profile Identification . . . . . . . . . . . . . . . . 4
2.1 Profile Initialization . . . . . . . . . . . . . . . . . . . 5
3. SOAP Message Packages . . . . . . . . . . . . . . . . . . . 7
4. SOAP Message Patterns . . . . . . . . . . . . . . . . . . . 9
4.1 One-way Message . . . . . . . . . . . . . . . . . . . . . . 9
4.2 Request-Response Exchange . . . . . . . . . . . . . . . . . 9
4.3 Request/N-Responses Exchange . . . . . . . . . . . . . . . . 9
5. URL Schemes . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1 The soap.beep URL Scheme . . . . . . . . . . . . . . . . . . 10
5.1.1 Resolving IP/TCP Address Information . . . . . . . . . . . . 10
5.2 The soap.beeps URL Scheme . . . . . . . . . . . . . . . . . 11
6. Registration Templates . . . . . . . . . . . . . . . . . . . 12
6.1 SOAP Profile Feature Registration Template . . . . . . . . . 12
7. Initial Registrations . . . . . . . . . . . . . . . . . . . 13
7.1 Registration: The SOAP Profile . . . . . . . . . . . . . . . 13
7.2 Registration: The soap.beep URL Scheme . . . . . . . . . . . 14
7.3 Registration: The soap.beeps URL Scheme . . . . . . . . . . 15
7.4 Registration: The System (Well-Known) TCP port number for
SOAP over BEEP . . . . . . . . . . . . . . . . . . . . . . . 15
8. Security Considerations . . . . . . . . . . . . . . . . . . 16
References . . . . . . . . . . . . . . . . . . . . . . . . . 17
IANA Considerations . . . . . . . . . . . . . . . . . . . . 18
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 19
Full Copyright Statement . . . . . . . . . . . . . . . . . . 20
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. BEEP Profile Identification . . . . . . . . . . . . . . . . 4
2.1 Profile Initialization . . . . . . . . . . . . . . . . . . . 5
3. SOAP Message Packages . . . . . . . . . . . . . . . . . . . 7
4. SOAP Message Patterns . . . . . . . . . . . . . . . . . . . 9
4.1 One-way Message . . . . . . . . . . . . . . . . . . . . . . 9
4.2 Request-Response Exchange . . . . . . . . . . . . . . . . . 9
4.3 Request/N-Responses Exchange . . . . . . . . . . . . . . . . 9
5. URL Schemes . . . . . . . . . . . . . . . . . . . . . . . . 10
5.1 The soap.beep URL Scheme . . . . . . . . . . . . . . . . . . 10
5.1.1 Resolving IP/TCP Address Information . . . . . . . . . . . . 10
5.2 The soap.beeps URL Scheme . . . . . . . . . . . . . . . . . 11
6. Registration Templates . . . . . . . . . . . . . . . . . . . 12
6.1 SOAP Profile Feature Registration Template . . . . . . . . . 12
7. Initial Registrations . . . . . . . . . . . . . . . . . . . 13
7.1 Registration: The SOAP Profile . . . . . . . . . . . . . . . 13
7.2 Registration: The soap.beep URL Scheme . . . . . . . . . . . 14
7.3 Registration: The soap.beeps URL Scheme . . . . . . . . . . 15
7.4 Registration: The System (Well-Known) TCP port number for
SOAP over BEEP . . . . . . . . . . . . . . . . . . . . . . . 15
8. Security Considerations . . . . . . . . . . . . . . . . . . 16
References . . . . . . . . . . . . . . . . . . . . . . . . . 17
IANA Considerations . . . . . . . . . . . . . . . . . . . . 18
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 19
Full Copyright Statement . . . . . . . . . . . . . . . . . . 20
This memo specifies how SOAP 1.1 envelopes[1] are transmitted using a BEEP profile[2]. In the W3C, the XMLP effort is evolving SOAP. Accordingly, this memo provides a mechanism for negotiating the use of new features.
此备忘录指定如何使用蜂鸣配置文件[2]传输SOAP 1.1信封[1]。在W3C中，XMLP工作正在演变为SOAP。因此，本备忘录提供了一种协商使用新功能的机制。
Throughout this memo, the term "envelope" refers to the "SOAP-Env:Envelope" element defined in Section 4 of [1]. Further, the terms "peer", "client", "server", "one-to-one", and "one-to-many" are used in the context of BEEP. In particular, Sections 2.1 and 2.1.1 of [2] discuss BEEP roles and exchange styles.
在本备忘录中，术语“信封”指的是[1]第4节中定义的“SOAP环境：信封”元素。此外，术语“对等”、“客户端”、“服务器”、“一对一”和“一对多”在BEEP的上下文中使用。具体而言，[2]的第2.1节和第2.1.1节讨论了BEEP角色和交换样式。
The BEEP profile for SOAP is identified as
SOAP的蜂鸣声配置文件标识为
http://iana.org/beep/soap
http://iana.org/beep/soap
in the BEEP "profile" element during channel creation.
在频道创建过程中，在“配置文件”元素中。
In BEEP, when the first channel is successfully created, the "serverName" attribute in the "start" element identifies the "virtual host" associated with the peer acting in the server role, e.g.,
在BEEP中，当成功创建第一个通道时，“start”元素中的“serverName”属性标识与充当服务器角色的对等方关联的“虚拟主机”，例如。，
<start number='1' serverName='stockquoteserver.example.com'>
<profile uri='http://iana.org/beep/soap' />
</start>
<start number='1' serverName='stockquoteserver.example.com'>
<profile uri='http://iana.org/beep/soap' />
</start>
The "serverName" attribute is analagous to HTTP's "Host" request-header field (c.f., Section 14.23 of [3]).
“serverName”属性与HTTP的“主机”请求头字段（c.f.[3]的第14.23节）非常相似。
There are two states in the BEEP profile for SOAP, "boot" and "ready":
SOAP的BEEP配置文件中有两种状态：“启动”和“准备就绪”：
o In the "boot" state, the peer requesting the creation of the channel sends a "bootmsg" (either during channel initialization or in a "MSG" message).
o 在“boot”状态下，请求创建通道的对等方发送“bootmsg”（在通道初始化期间或在“MSG”消息中）。
* If the other peer sends a "bootrpy" (either during channel initialization or in a "RPY" message), then the "ready" state is entered
* 如果另一个对等方发送“bootrpy”（在通道初始化期间或在“RPY”消息中），则进入“就绪”状态
* Otherwise, the other peer sends an "error" (either during channel initialization or in a "ERR" message), then no state change occurs.
* 否则，另一个对等方发送“错误”（在通道初始化期间或在“ERR”消息中），则不会发生状态更改。
o In the "ready" state, either peer begins a SOAP message pattern by sending a "MSG" message containing an envelope. The other peer completes the message pattern either by:
o 在“就绪”状态下，任一对等方通过发送包含信封的“MSG”消息开始SOAP消息模式。另一个对等方通过以下方式完成消息模式：
* sending back a "RPY" message containing an envelope; or,
* 发送回包含信封的“RPY”消息；或
* sending back zero or more "ANS" messages, each containing an envelope, followed by a "NUL" message.
* 发送回零条或多条“ANS”消息，每条消息包含一个信封，后跟一条“NUL”消息。
Regardless, no state change occurs.
无论如何，不会发生状态更改。
The boot message is used for two purposes:
启动消息用于两个目的：
resource identification: each channel bound to the BEEP profile for SOAP provides access to a single resource (a network data object or service).
资源标识：绑定到SOAP的BEEP配置文件的每个通道都提供对单个资源（网络数据对象或服务）的访问。
feature negotiation: if new features of SOAP (such as compression) emerge, their use can be negotiated.
特性协商：如果SOAP的新特性（如压缩）出现，可以协商它们的使用。
The DTD syntax for the boot message and its response are:
引导消息及其响应的DTD语法为：
<!ELEMENT bootmsg EMPTY>
<!ATTLIST bootmsg
resource CDATA #REQUIRED
features NMTOKENS "">
<!ELEMENT bootmsg EMPTY>
<!ATTLIST bootmsg
resource CDATA #REQUIRED
features NMTOKENS "">
<!ELEMENT bootrpy EMPTY>
<!ATTLIST bootrpy
features NMTOKENS "">
<!ELEMENT bootrpy EMPTY>
<!ATTLIST bootrpy
features NMTOKENS "">
The boot message contains a mandatory and an optional attribute:
启动消息包含一个强制属性和一个可选属性：
o the "resource" attribute, which is analagous to HTTP's "abs_path" Request-URI parameter (c.f., Section 5.1.2 of [3]); and,
o “resource”属性，与HTTP的“abs_path”请求URI参数相关（c.f.，第5.1.2节，共[3]）；和
o the "features" attribute, which, if present, contains one or more feature tokens, each indicating an optional feature of the BEEP profile for SOAP that is being requested for possible use over the channel.
o “features”属性（如果存在）包含一个或多个feature标记，每个标记表示正在请求通过通道使用的SOAP的蜂鸣配置文件的可选功能。
Section 6.1 defines a registration template for optional features.
第6.1节定义了可选功能的注册模板。
If the peer acting in the server role recognizes the requested resource, it replies with the boot response that contains one optional attribute:
如果担任服务器角色的对等方识别请求的资源，它将使用包含一个可选属性的引导响应进行响应：
o the "features" attribute, if present, contains a subset of the feature tokens in the boot message, indicating which features may be used over the channel. (If not present or empty, then no features may be used.)
o “features”属性（如果存在）在引导消息中包含功能令牌的子集，指示哪些功能可以通过通道使用。（如果不存在或为空，则不能使用任何功能。）
Otherwise, if the boot message is improperly formed, or if the requested resource isn't recognized, the peer acting in the server role replies with an error message (c.f., Section 7.1 of [2]).
否则，如果启动消息格式不正确，或者请求的资源无法识别，则担任服务器角色的对等方会回复错误消息（c.f.[2]第7.1节）。
Typically, the boot message and its response are exchanged during channel initialization (c.f., Section 2.3.1.2 of [2]).
通常，引导消息及其响应在通道初始化期间交换（c.f.[2]第2.3.1.2节）。
For example, here the boot message and its response are exchanged during channel initialization:
例如，此处引导消息及其响应在通道初始化期间交换：
C: <start number='1' serverName='stockquoteserver.example.com'>
C: <profile uri='http://iana.org/beep/soap'>
C: <![CDATA[<bootmsg resource='/StockQuote' />]]>
C: </profile>
C: </start>
C: <start number='1' serverName='stockquoteserver.example.com'>
C: <profile uri='http://iana.org/beep/soap'>
C: <![CDATA[<bootmsg resource='/StockQuote' />]]>
C: </profile>
C: </start>
S: <profile uri='http://iana.org/beep/soap'>
S: <![CDATA[<bootrpy />]]>
S: </profile>
S: <profile uri='http://iana.org/beep/soap'>
S: <![CDATA[<bootrpy />]]>
S: </profile>
The channel bound to the BEEP profile for SOAP is now in the "ready" state.
绑定到SOAP的BEEP配置文件的通道现在处于“就绪”状态。
Alternatively, here is an example in which the boot exchange is unsuccessful:
或者，下面是引导交换失败的示例：
C: <start number='1' serverName='stockquoteserver.example.com'>
C: <profile uri='http://iana.org/beep/soap'>
C: <![CDATA[<bootmsg resource='/StockPick' />]]>
C: </profile>
C: </start>
C: <start number='1' serverName='stockquoteserver.example.com'>
C: <profile uri='http://iana.org/beep/soap'>
C: <![CDATA[<bootmsg resource='/StockPick' />]]>
C: </profile>
C: </start>
S: <profile uri='http://iana.org/beep/soap'>
S: <![CDATA[<error code='550'>resource not
S: supported</error>]]>
S: </profile>
S: <profile uri='http://iana.org/beep/soap'>
S: <![CDATA[<error code='550'>resource not
S: supported</error>]]>
S: </profile>
Although the channel was created successfully, it remains in the "boot" state.
虽然通道已成功创建，但仍处于“启动”状态。
The BEEP profile for SOAP transmits envelopes encoded as UTF-8 using the media type "application/xml"[4], e.g.,
SOAP的BEEP配置文件使用媒体类型“application/xml”[4]传输编码为UTF-8的信封，例如。，
MSG 1 1 . 0 364
Content-Type: application/xml
MSG 1 1 . 0 364
Content-Type: application/xml
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<m:GetLastTradePrice xmlns:m="Some-URI">
<symbol>DIS</symbol>
</m:GetLastTradePrice>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
END
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<m:GetLastTradePrice xmlns:m="Some-URI">
<symbol>DIS</symbol>
</m:GetLastTradePrice>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
END
In addition, the BEEP profile for SOAP also allows envelopes to be transmitted as the root part of a "multipart/related"[5] content, and with subordinate parts referenced using the rules of Section 3 of [6] (i.e., using either the "Content-ID:"[7] or "Content-Location:"[8] headers), e.g.,
此外，SOAP的BEEP配置文件还允许将信封作为“多部分/相关”[5]内容的根部分进行传输，并使用[6]第3节的规则（即，使用“内容ID:[7]或“内容位置：[8]头”）引用从属部分，例如。，
MSG 1 2 . 364 668
Content-Type: multipart/related; boundary="MIME_boundary";
type=application/xml;
start="<claim061400a.xml@claiming-it.com>"
MSG 1 2 . 364 668
Content-Type: multipart/related; boundary="MIME_boundary";
type=application/xml;
start="<claim061400a.xml@claiming-it.com>"
--MIME_boundary
Content-Type: application/xml
Content-ID: <claim061400a.xml@claiming-it.com>
--MIME_boundary
Content-Type: application/xml
Content-ID: <claim061400a.xml@claiming-it.com>
<?xml version='1.0' ?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
..
<theSignedForm href="cid:claim061400a.tiff@claiming-it.com" />
..
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version='1.0' ?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
..
<theSignedForm href="cid:claim061400a.tiff@claiming-it.com" />
..
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
--MIME_boundary
Content-Type: image/tiff
Content-Transfer-Encoding: binary
Content-ID: <claim061400a.tiff@claiming-it.com>
--MIME_boundary
Content-Type: image/tiff
Content-Transfer-Encoding: binary
Content-ID: <claim061400a.tiff@claiming-it.com>
...binary TIFF image... --MIME_boundary-- END
…二进制TIFF图像--MIME_边界—结束
Consistent with Section 2 of [6], it is strongly recommended that the multipart contain a "start" parameter, and that the root part contain a "Content-ID:" header. However, because BEEP provides an 8bit-wide path, a "transformative" Content-Transfer-Encoding (e.g., "base64" or "quoted-printable") should not be used. Further note that MIME[9] requires that the value of the "Content-ID" header be globally unique.
与[6]第2节一致，强烈建议多部分包含一个“start”参数，根部分包含一个“Content ID:”标题。但是，由于BEEP提供8位宽的路径，因此不应使用“转换性”内容传输编码（例如，“base64”或“可打印引用”）。进一步注意，MIME[9]要求“Content ID”头的值是全局唯一的。
A one-way message involves sending a message without any response being returned.
单向消息包括在不返回任何响应的情况下发送消息。
The BEEP profile for SOAP achieves this using a one-to-many exchange, in which the client sends a "MSG" message containing an envelope, and the server immediately sends back a "NUL" message, before processing the contents of the envelope.
SOAP的BEEP配置文件使用一对多交换来实现这一点，其中客户端发送包含信封的“MSG”消息，服务器在处理信封内容之前立即发回“NUL”消息。
A request/response exchange involves sending a request, which results in a response being returned.
请求/响应交换涉及发送请求，从而返回响应。
The BEEP profile for SOAP achieves this using a one-to-one exchange, in which the client sends a "MSG" message containing an envelope, and the server sends back a "RPY" message containing an envelope.
SOAP的BEEP配置文件使用一对一的交换来实现这一点，在这种交换中，客户端发送包含信封的“MSG”消息，服务器发送回包含信封的“RPY”消息。
Finally, the BEEP profile for SOAP does not use the "ERR" message for SOAP faults when performing one-to-one exchanges -- whatever response is generated by the server is always returned in the "RPY" message.
最后，SOAP的BEEP配置文件在执行一对一交换时不使用SOAP错误的“ERR”消息——服务器生成的任何响应总是在“RPY”消息中返回。
A request/N-responses exchange involves sending a request, which results in zero or more responses being returned.
请求/N-responses交换涉及发送请求，这将导致返回零个或多个响应。
The BEEP profile for SOAP achieves this using a one-to-many exchange, in which the client sends a "MSG" message containing an envelope, and the server sends back zero or more "ANS" messages, each containing an envelope, followed by a "NUL" message.
SOAP的BEEP配置文件使用一对多交换来实现这一点，在这种交换中，客户机发送一条包含信封的“MSG”消息，服务器发送回零条或多条“ANS”消息，每条消息包含一个信封，然后是一条“NUL”消息。
This memo defines two URL schemes, "soap.beep" and "soap.beeps", which identify the use of SOAP over BEEP over TCP. Note that, at present, a "generic" URL scheme for SOAP is not defined.
此备忘录定义了两个URL方案，“soap.beep”和“soap.beep”，它们标识了通过TCP使用soap over beep。请注意，目前尚未定义SOAP的“通用”URL方案。
The "soap.beep" URL scheme uses the "generic URI" syntax defined in Section 3 of [10], specifically:
“soap.beep”URL方案使用[10]第3节中定义的“通用URI”语法，具体如下：
o the value "soap.beep" is used for the scheme component; and,
o 值“soap.beep”用于方案组件；和
o the server-based naming authority defined in Section 3.2.2 of [10] is used for the authority component.
o [10]第3.2.2节中定义的基于服务器的命名权限用于权限组件。
o the path component maps to the "resource" component of the boot message sent during profile initialization (if absent, it defaults to "/").
o path组件映射到概要文件初始化期间发送的引导消息的“资源”组件（如果不存在，则默认为“/”。
The values of both the scheme and authority components are case-insensitive.
scheme和authority组件的值都不区分大小写。
For example, the URL
例如，URL
soap.beep://stockquoteserver.example.com/StockQuote
soap.beep://stockquoteserver.example.com/StockQuote
might result in the example shown in Section 2.1.
可能导致第2.1节中所示的示例。
The "soap.beep" URL scheme indicates the use of the BEEP profile for SOAP running over TCP/IP.
“soap.beep”URL方案表示对通过TCP/IP运行的soap使用beep配置文件。
If the authority component contains a domain name and a port number, e.g.,
如果授权组件包含域名和端口号，例如。，
soap.beep://stockquoteserver.example.com:1026
soap.beep://stockquoteserver.example.com:1026
then the DNS is queried for the A RRs corresponding to the domain name, and the port number is used directly.
然后向DNS查询与域名对应的A RRs，并直接使用端口号。
If the authority component contains a domain name and no port number, e.g.,
如果授权组件包含域名而没有端口号，例如。，
soap.beep://stockquoteserver.example.com
soap.beep://stockquoteserver.example.com
the SRV algorithm[11] is used with a service parameter of "soap-beep" and a protocol parameter of "tcp" to determine the IP/TCP addressing information. If no appropriate SRV RRs are found (e.g., for "_soap-beep._tcp.stockquoteserver.example.com"), then the DNS is queried for the A RRs corresponding to the domain name and the port number used is assigned by the IANA for the registration in Section 7.4.
SRV算法[11]与服务参数“soap beep”和协议参数“tcp”一起使用，以确定IP/tcp寻址信息。如果未找到合适的SRV RRs（例如，对于“\u soap-beep.\u tcp.stockquoteserver.example.com”），则会查询DNS以查找对应于域名的RRs，并且IANA会为第7.4节中的注册分配所用的端口号。
If the authority component contains an IP address, e.g.,
如果授权组件包含IP地址，例如。，
soap.beep://10.0.0.2:1026
soap.beep://10.0.0.2:1026
then the DNS is not queried, and the IP address is used directly. If a port number is present, it is used directly; otherwise, the port number used is assigned by the IANA for the registration in Section 7.4.
然后不查询DNS，直接使用IP地址。如果存在端口号，则直接使用该端口号；否则，IANA将为第7.4节中的注册分配使用的端口号。
While the use of literal IPv6 addresses in URLs is discouraged, if a literal IPv6 address is used in a "soap.beep" URL, it must conform to the syntax specified in [12].
虽然不鼓励在URL中使用文字IPv6地址，但如果在“soap.beep”URL中使用文字IPv6地址，则该地址必须符合[12]中指定的语法。
The "soap.beeps" URL scheme is identical, in all ways, to the "soap.beep" URL scheme specified in Section 5.1, with the exception that prior to starting the BEEP profile for SOAP, the BEEP session must be tuned for privacy. In particular, note that both URL schemes use the identical algorithms and parameters for address resolution as specified in Section 5.1.1 (e.g., the same service name for SRV lookups, the same port number for TCP, and so on).
“soap.beep”URL方案在所有方面都与第5.1节中指定的“soap.beep”URL方案相同，但在启动soap的beep配置文件之前，必须对beep会话进行隐私调整。特别要注意的是，两种URL方案使用第5.1.1节中规定的相同算法和地址解析参数（例如，SRV查找使用相同的服务名称，TCP使用相同的端口号，等等）。
There are two ways to perform privacy tuning on a BEEP session, either:
有两种方法可以在蜂鸣音会话上执行隐私调整，或者：
o a transport security profile may be successfully started; or,
o 可以成功启动传输安全配置文件；或
o a user authentication profile that supports transport security may be successfully started.
o 支持传输安全的用户身份验证配置文件可能已成功启动。
Regardless, upon completion of the negotiation process, a tuning reset occurs in which both BEEP peers issue a new greeting. Consult Section 3 of [2] for an example of how a BEEP peer may choose to issue different greetings based on whether privacy is in use.
无论如何，在协商过程完成后，会发生一次调整重置，其中两个BEEP对等方发出一个新的问候语。请参阅[2]第3节，了解蜂鸣器对等方如何根据是否使用隐私权选择发出不同问候语的示例。
When a feature for the BEEP profile for SOAP is registered, the following information is supplied:
注册SOAP的BEEP配置文件的功能时，将提供以下信息：
Feature Identification: specify a string that identifies this feature. Unless the feature is registered with the IANA, the feature's identification must start with "x-".
特征标识：指定标识此特征的字符串。除非该功能已向IANA注册，否则该功能的标识必须以“x-”开头。
Feature Semantics: specify the semantics of the feature.
特征语义：指定特征的语义。
Contact Information: specify the electronic contact information for the author of the feature.
联系信息：指定功能作者的电子联系信息。
Profile Identification: http://iana.org/beep/soap
Profile Identification: http://iana.org/beep/soap
Messages exchanged during Channel Creation: bootmsg, bootrpy
通道创建期间交换的消息：bootmsg、bootrpy
Messages starting one-to-one exchanges: bootmsg, SOAP-Env:Envelope
开始一对一交换的消息：bootmsg、SOAP Env:Envelope
Messages in positive replies: bootrpy, SOAP-Env:Envelope
正面回复中的消息：bootrpy、SOAP Env:Envelope
Messages in negative replies: error
否定回复中的消息：错误
Messages in one-to-many exchanges: SOAP-Env:Envelope
一对多交换中的消息：SOAP Env:Envelope
Message Syntax: SOAP-Env:Envelope as defined in Section 4 of [1] and [6]
消息语法：SOAP Env:Envelope，定义见[1]和[6]的第4节
Message Semantics: c.f., [1]
消息语义：c.f.，[1]
Contact Information: Eamon O'Tuathail <eamon.otuathail@clipcode.com>,
Marshall Rose <mrose@dbc.mtview.ca.us>
Contact Information: Eamon O'Tuathail <eamon.otuathail@clipcode.com>,
Marshall Rose <mrose@dbc.mtview.ca.us>
URL scheme name: soap.beep
URL方案名称：soap.beep
URL scheme syntax: c.f., Section 5.1
URL方案语法：c.f.，第5.1节
Character encoding considerations: c.f., the "generic URI" syntax defined in Section 3 of [10]
字符编码注意事项：c.f.，[10]第3节中定义的“通用URI”语法
Intended usage: identifies a SOAP resource made available using the BEEP profile for SOAP
预期用途：标识使用SOAP的BEEP配置文件提供的SOAP资源
Applications using this scheme: c.f., "Intended usage", above
使用此方案的应用：c.f.，“预期用途”，如上
Interoperability considerations: n/a
互操作性注意事项：不适用
Security Considerations: c.f., Section 8
安全考虑：c.f.，第8节
Relevant Publications: c.f., [1], [6], and [2]
相关出版物：c.f.，[1]，[6]和[2]
Contact Information: Eamon O'Tuathail <eamon.otuathail@clipcode.com>,
Marshall Rose <mrose@dbc.mtview.ca.us>
Contact Information: Eamon O'Tuathail <eamon.otuathail@clipcode.com>,
Marshall Rose <mrose@dbc.mtview.ca.us>
Author/Change controller: the IESG
作者/变更控制员：IESG
URL scheme name: soap.beeps
URL方案名称：soap.beeps
URL scheme syntax: c.f., Section 5.2
URL方案语法：c.f.，第5.2节
Character encoding considerations: c.f., the "generic URI" syntax defined in Section 3 of [10]
字符编码注意事项：c.f.，[10]第3节中定义的“通用URI”语法
Intended usage: identifies a SOAP resource made available using the BEEP profile for SOAP after the BEEP session has been tuned for privacy
预期用途：标识一个SOAP资源，该资源在BEEP会话被调优为隐私之后，使用SOAP的BEEP配置文件可用
Applications using this scheme: c.f., "Intended usage", above
使用此方案的应用：c.f.，“预期用途”，如上
Interoperability considerations: n/a
互操作性注意事项：不适用
Security Considerations: c.f., Section 8
安全考虑：c.f.，第8节
Relevant Publications: c.f., [1], [6], and [2]
相关出版物：c.f.，[1]，[6]和[2]
Contact Information: Eamon O'Tuathail <eamon.otuathail@clipcode.com>,
Marshall Rose <mrose@dbc.mtview.ca.us>
Contact Information: Eamon O'Tuathail <eamon.otuathail@clipcode.com>,
Marshall Rose <mrose@dbc.mtview.ca.us>
Author/Change controller: the IESG
作者/变更控制员：IESG
7.4 Registration: The System (Well-Known) TCP port number for SOAP over BEEP
7.4 注册：SOAP over BEEP的系统（众所周知）TCP端口号
Protocol Number: TCP
协议编号：TCP
Message Formats, Types, Opcodes, and Sequences: c.f., Section 2.1
消息格式、类型、操作码和序列：c.f.，第2.1节
Functions: c.f., [1]
功能：c.f.，[1]
Use of Broadcast/Multicast: none
使用广播/多播：无
Proposed Name: SOAP over BEEP
建议名称：SOAP over BEEP
Short name: soap-beep
短名称：soap-beep
Contact Information: Eamon O'Tuathail <eamon.otuathail@clipcode.com>,
Marshall Rose <mrose@dbc.mtview.ca.us>
Contact Information: Eamon O'Tuathail <eamon.otuathail@clipcode.com>,
Marshall Rose <mrose@dbc.mtview.ca.us>
Although service provisioning is a policy matter, at a minimum, all implementations must provide the following tuning profiles:
尽管服务供应是一个策略问题，但至少所有实现都必须提供以下调优配置文件：
for authentication: http://iana.org/beep/SASL/DIGEST-MD5
for authentication: http://iana.org/beep/SASL/DIGEST-MD5
for confidentiality: http://iana.org/beep/TLS (using the
TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher)
for confidentiality: http://iana.org/beep/TLS (using the
TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher)
for both: http://iana.org/beep/TLS (using the
TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher supporting client-side
certificates)
for both: http://iana.org/beep/TLS (using the
TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher supporting client-side
certificates)
Further, implementations may choose to offer MIME-based security services providing message integrity and confidentiality, such as OpenPGP[13] or S/MIME[14].
此外，实现可以选择提供基于MIME的安全服务，提供消息完整性和机密性，例如OpenPGP[13]或S/MIME[14]。
Regardless, consult [2]'s Section 9 for a discussion of BEEP-specific security issues.
无论如何，请参阅[2]的第9节，以讨论特定于BEEP的安全问题。
References
工具书类
[1] Box, D., Ehnebuske, D., Kakivaya, G., Layman, A., Mendelsohn, N., Nielsen, H., Thatte, S. and D. Winer, "Simple Object Access Protocol (SOAP) 1.1", May 2000, <http://www.w3.org/TR/2000/ NOTE-SOAP-20000508>.
[1] Box，D.，Ehnebuske，D.，Kakivaya，G.，Layman，A.，Mendelsohn，N.，Nielsen，H.，Thatte，S.和D.Winer，“简单对象访问协议（SOAP）1.1”，2000年5月<http://www.w3.org/TR/2000/ 注-SOAP-2000058>。
[2] Rose, M., "The Blocks Extensible Exchange Protocol Core", RFC 3080, March 2001.
[2] Rose，M.，“块可扩展交换协议核心”，RFC 30802001年3月。
[3] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[3] 菲尔丁，R.，盖蒂斯，J.，莫格尔，J.，尼尔森，H.，马斯特，L.，利奇，P.和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC2616，1999年6月。
[4] Murata, M., St.Laurent, S. and D. Kohn, "XML Media Types", RFC 3023, January 2001.
[4] Murata，M.，St.Laurent，S.和D.Kohn，“XML媒体类型”，RFC 3023，2001年1月。
[5] Levinson, E., "The MIME Multipart/Related Content-type", RFC 2387, August 1998.
[5] Levinson，E.，“MIME多部分/相关内容类型”，RFC 2387，1998年8月。
[6] Barton, J., Thatte, S. and H. Nielsen, "SOAP Messages with Attachments", December 2000, <http://www.w3.org/TR/2000/NOTE-SOAP-attachments-20001211>.
[6] Barton，J.，Thatte，S.和H.Nielsen，“带附件的SOAP消息”，2000年12月<http://www.w3.org/TR/2000/NOTE-SOAP-attachments-20001211>.
[7] Levinson, E., "Content-ID and Message-ID Uniform Resource Locators", RFC 2392, August 1998.
[7] Levinson，E.，“内容ID和消息ID统一资源定位器”，RFC 2392，1998年8月。
[8] Palme, F., Hopmann, A., Shelness, N. and E. Stefferud, "MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)", RFC 2557, March 1999.
[8] Palme，F.，Hopmann，A.，Shelness，N.和E.Stefferud，“聚合文档的MIME封装，如HTML（MHTML）”，RFC 2557，1999年3月。
[9] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[9] Freed，N.和N.Borenstein，“多用途互联网邮件扩展（MIME）第一部分：互联网邮件正文格式”，RFC 20451996年11月。
[10] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[10] Berners Lee，T.，Fielding，R.和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。
[11] Gulbrandsen, A., Vixie, P. and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV)", RFC 2782, February 2000.
[11] Gulbrandsen，A.，Vixie，P.和L.Esibov，“用于指定服务位置（DNS SRV）的DNS RR”，RFC 2782，2000年2月。
[12] Haskin, D. and E. Allen, "IP Version 6 over PPP", RFC 2472, December 1998.
[12] Haskin，D.和E.Allen，“PPP上的IP版本6”，RFC 24721998年12月。
[13] Elkins, M., Del Torto, D., Levien, R. and T. Roessler, "MIME Security with OpenPGP", RFC 3156, August 2001.
[13] Elkins，M.，Del Torto，D.，Levien，R.和T.Roessler，“OpenPGP的MIME安全性”，RFC 3156，2001年8月。
[14] Ramsdell, B., "S/MIME Version 3 Message Specification", RFC 2633, June 1999.
[14] Ramsdell，B.，“S/MIME版本3消息规范”，RFC 2633，1999年6月。
IANA Considerations
IANA考虑
The IANA has registered the profile specified in Section 7.1 as:
IANA已将第7.1节中规定的配置文件注册为：
http://iana.org/beep/soap
http://iana.org/beep/soap
The IANA has registered "soap.beep" and "soap.beeps" as URL schemes, as specified in Section 7.2 and Section 7.3, respectively.
IANA已将“soap.beep”和“soap.beep”分别注册为URL方案，如第7.2节和第7.3节所述。
The IANA has also registered "SOAP over BEEP" as a TCP port number, as specified in Section 7.4.
IANA还将“SOAP over BEEP”注册为TCP端口号，如第7.4节所述。
Finally, the IANA maintains a list of SOAP profile features, c.f., Section 6.1. The IESG is responsible for assigning a designated expert to review the specification prior to the IANA making the assignment. Prior to contacting the IESG, developers of SOAP profile features must use the mailing list beepwg@lists.beepcore.org to solicit commentary.
最后，IANA维护了SOAP概要文件特性列表，c.f.，第6.1节。IESG负责指派一名指定专家在IANA做出指定之前审查规范。在联系IESG之前，SOAP概要文件特性的开发人员必须使用邮件列表beepwg@lists.beepcore.org征求评论。
Acknowledgements
致谢
The authors gratefully acknowledge the contributions of: Christopher Ferris, Huston Franklin, Alexey Melnikov, Bill Mills, and Roy T. Fielding.
作者衷心感谢克里斯托弗·费里斯、休斯顿·富兰克林、阿列克西·梅尔尼科夫、比尔·米尔斯和罗伊·T·菲尔丁的贡献。
Authors' Addresses
作者地址
Eamon O'Tuathail Clipcode.com 24 Thomastown Road Dun Laoghaire Dublin IE
Eamon O'Tuathail Clipcode.com都柏林老挝海尔托马斯敦路24号
Phone: +353 1 2350 424
EMail: eamon.otuathail@clipcode.com
URI: http://www.clipcode.com/
Phone: +353 1 2350 424
EMail: eamon.otuathail@clipcode.com
URI: http://www.clipcode.com/
Marshall T. Rose Dover Beach Consulting, Inc. POB 255268 Sacramento, CA 95865-5268 US
马歇尔T.罗斯多佛海滩咨询公司POB 255268萨克拉门托，加利福尼亚州95865-5268美国
Phone: +1 916 483 8878
EMail: mrose@dbc.mtview.ca.us
Phone: +1 916 483 8878
EMail: mrose@dbc.mtview.ca.us
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。