Network Working Group                                      M. Froumentin
Request for Comments: 4267                                           W3C
Category: Informational                                    November 2005
        
Network Working Group                                      M. Froumentin
Request for Comments: 4267                                           W3C
Category: Informational                                    November 2005
        
            The W3C Speech Interface Framework Media Types:
   application/voicexml+xml, application/ssml+xml, application/srgs,
  application/srgs+xml, application/ccxml+xml, and application/pls+xml
        
            The W3C Speech Interface Framework Media Types:
   application/voicexml+xml, application/ssml+xml, application/srgs,
  application/srgs+xml, application/ccxml+xml, and application/pls+xml
        

Status of This Memo

关于下段备忘

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (2005).

版权所有(C)互联网协会(2005年)。

Abstract

摘要

This document defines the media types for the languages of the W3C Speech Interface Framework, as designed by the Voice Browser Working Group in the following specifications: the Voice Extensible Markup Language (VoiceXML), the Speech Synthesis Markup Language (SSML), the Speech Recognition Grammar Specification (SRGS), the Call Control XML (CCXML), and the Pronunciation Lexicon Specification (PLS).

本文档定义了W3C语音接口框架语言的媒体类型,由语音浏览器工作组在以下规范中设计:语音可扩展标记语言(VoiceXML)、语音合成标记语言(SSML)、语音识别语法规范(SRGS)、呼叫控制XML(CCXML),以及发音词典规范(PLS)。

Table of Contents

目录

   1. Introduction ....................................................2
   2. Registration of application/voicexml+xml, application/ssml+xml,
      application/srgs+xml, application/ccxml+xml, and
      application/pls+xml .............................................3
      2.1. Encoding Considerations ....................................3
      2.2. Interoperability Considerations ............................3
      2.3. Published Specifications ...................................3
      2.4. Applications that Use These Media Types ....................4
      2.5. Security Considerations ....................................4
      2.6. Additional Information .....................................4
           2.6.1. Magic Numbers .......................................4
           2.6.2. File Extensions .....................................4
           2.6.3. Fragment Identifiers ................................5
           2.6.4. Macintosh File Type Code ............................5
           2.6.5. Person and Email Address to Contact for
                  Further Information .................................5
           2.6.6. Intended Usage ......................................5
           2.6.7. Change Controller ...................................5
        
   1. Introduction ....................................................2
   2. Registration of application/voicexml+xml, application/ssml+xml,
      application/srgs+xml, application/ccxml+xml, and
      application/pls+xml .............................................3
      2.1. Encoding Considerations ....................................3
      2.2. Interoperability Considerations ............................3
      2.3. Published Specifications ...................................3
      2.4. Applications that Use These Media Types ....................4
      2.5. Security Considerations ....................................4
      2.6. Additional Information .....................................4
           2.6.1. Magic Numbers .......................................4
           2.6.2. File Extensions .....................................4
           2.6.3. Fragment Identifiers ................................5
           2.6.4. Macintosh File Type Code ............................5
           2.6.5. Person and Email Address to Contact for
                  Further Information .................................5
           2.6.6. Intended Usage ......................................5
           2.6.7. Change Controller ...................................5
        
   3. Registration of application/srgs ................................5
      3.1. Encoding Considerations ....................................5
      3.2. Interoperability Considerations ............................5
      3.3. Published Specifications ...................................5
      3.4. Applications That Use This Media Type ......................6
      3.5. Security Considerations ....................................6
      3.6. Additional Information .....................................6
           3.6.1. Magic Numbers .......................................6
           3.6.2. File Extensions .....................................6
           3.6.3. Macintosh File Type Code ............................6
           3.6.4. Person and Email Address to Contact for
                  Further Information .................................7
           3.6.5. Intended Usage ......................................7
           3.6.6. Change Controller ...................................7
   4. IANA Considerations .............................................7
   5. Normative References ............................................7
        
   3. Registration of application/srgs ................................5
      3.1. Encoding Considerations ....................................5
      3.2. Interoperability Considerations ............................5
      3.3. Published Specifications ...................................5
      3.4. Applications That Use This Media Type ......................6
      3.5. Security Considerations ....................................6
      3.6. Additional Information .....................................6
           3.6.1. Magic Numbers .......................................6
           3.6.2. File Extensions .....................................6
           3.6.3. Macintosh File Type Code ............................6
           3.6.4. Person and Email Address to Contact for
                  Further Information .................................7
           3.6.5. Intended Usage ......................................7
           3.6.6. Change Controller ...................................7
   4. IANA Considerations .............................................7
   5. Normative References ............................................7
        
1. Introduction
1. 介绍

This specification defines the media types of the Voice Extensible Markup Language (VoiceXML), the Speech Synthesis Markup Language (SSML), the Speech Recognition Grammar Specification (SRGS), the Call Control XML (CCXML), and the Pronunciation Lexicon Specification (PLS), the specifications of the W3C Speech Interface Framework.

本规范定义了语音可扩展标记语言(VoiceXML)、语音合成标记语言(SSML)、语音识别语法规范(SRGS)、呼叫控制XML(CCXML)和语音词典规范(PLS)的媒体类型,即W3C语音接口框架的规范。

VoiceXML ([VoiceXML2.0]) is an Extensible Markup Language (XML) designed for creating audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony, and mixed initiative conversations. The associated media type defined in this document is "application/voicexml+xml".

VoiceXML([VoiceXML2.0])是一种可扩展标记语言(XML),设计用于创建音频对话框,其中包括合成语音、数字化音频、语音和DTMF键输入识别、语音输入录制、电话和混合主动对话。本文档中定义的相关媒体类型为“application/voicexml+xml”。

The Speech Synthesis Markup Language specification (SSML) defines an XML-based markup language for assisting the generation of synthetic speech in Web and other applications. The essential role of SSML is to provide authors of synthesizable content a standard way to control aspects of speech such as pronunciation, volume, pitch, and rate, across different synthesis-capable platforms. The associated media type defined in this document is "application/ssml+xml".

语音合成标记语言规范(SSML)定义了一种基于XML的标记语言,用于帮助在Web和其他应用程序中生成合成语音。SSML的基本作用是为可合成内容的作者提供一种标准方法,以跨不同的合成平台控制语音的各个方面,如发音、音量、音调和速率。本文档中定义的相关媒体类型为“应用程序/ssml+xml”。

The Speech Recognition Grammar Specification (SRGS) defines syntax for representing grammars for use in speech recognition so that developers can specify the words and patterns of words to be listened for by a speech recognizer. The syntax of the grammar format exists in two forms, an Augmented BNF (ABNF) Form and an XML Form. The respective media types defined in this document are "application/srgs" and "application/srgs+xml".

语音识别语法规范(SRGS)定义了用于表示语音识别中使用的语法的语法,以便开发人员可以指定语音识别器要听的单词和单词模式。语法格式的语法有两种形式,一种是扩充BNF(ABNF)形式,另一种是XML形式。本文档中定义的相应媒体类型为“应用程序/srgs”和“应用程序/srgs+xml”。

The Call Control EXtensible Markup Language (CCXML) is an XML designed to provide telephony call control support for dialog systems, such as VoiceXML. The associated media type defined in this document is "application/ccxml+xml".

呼叫控制可扩展标记语言(CCXML)是一种XML,旨在为对话系统(如VoiceXML)提供电话呼叫控制支持。本文档中定义的相关媒体类型为“应用程序/ccxml+xml”。

The Pronunciation Lexicon Specification (PLS) defines an XML syntax for specifying pronunciation lexicons to be used by speech recognition and speech synthesis engines in voice browser applications. The associated media type defined in this document is "application/pls+xml".

语音词典规范(PLS)定义了一种XML语法,用于指定语音浏览器应用程序中语音识别和语音合成引擎使用的语音词典。本文档中定义的相关媒体类型为“应用程序/pls+xml”。

2. Registration of application/voicexml+xml, application/ssml+xml, application/srgs+xml, application/ccxml+xml, and application/pls+xml

2. 注册应用程序/voicexml+xml、应用程序/ssml+xml、应用程序/srgs+xml、应用程序/ccxml+xml和应用程序/pls+xml

MIME media type name: application

MIME媒体类型名称:应用程序

   MIME subtype names: voicexml+xml, ssml+xml, srgs+xml, ccxml+xml,
   pls+xml
        
   MIME subtype names: voicexml+xml, ssml+xml, srgs+xml, ccxml+xml,
   pls+xml
        

Required parameters: none

所需参数:无

Optional parameters:

可选参数:

"charset": This parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in RFC 3023 [RFC3023].

“charset”:此参数与RFC 3023[RFC3023]中指定的“application/xml”媒体类型的charset参数具有相同的语义。

2.1. Encoding Considerations
2.1. 编码注意事项

Identical to those of "application/xml" as described in RFC 3023 [RFC3023], section 3.2.

与RFC 3023[RFC3023]第3.2节所述的“应用程序/xml”相同。

2.2. Interoperability Considerations
2.2. 互操作性注意事项

There are no known interoperability issues.

没有已知的互操作性问题。

2.3. Published Specifications
2.3. 公布的规格

Voice Extensible Markup Language 2.0 [VoiceXML2.0]

语音可扩展标记语言2.0[VoiceXML2.0]

Voice Extensible Markup Language 2.1 [VoiceXML2.1]

语音可扩展标记语言2.1[VoiceXML2.1]

Speech Synthesis Markup Language (SSML) Version 1.0 [SSML]

语音合成标记语言(SSML)1.0版[SSML]

Speech Recognition Grammar Specification Version 1.0 [SRGS]

语音识别语法规范1.0版[SRGS]

Voice Browser Call Control: CCXML Version 1.0 [CCXML]

语音浏览器呼叫控制:CCXML 1.0版[CCXML]

Pronunciation Lexicon Specification (PLS) Version 1.0 [PLS]

发音词典规范(PLS)1.0版[PLS]

2.4. Applications that Use These Media Types
2.4. 使用这些媒体类型的应用程序

Various W3C Speech Interface Framework implementations use these media types.

各种W3C语音接口框架实现都使用这些媒体类型。

2.5. Security Considerations
2.5. 安全考虑

Several instructions in the cited specifications may cause arbitrary Uniform Resource Identifiers (URIs) to be dereferenced. In this case, the security issues of [RFC3986], section 7, should be considered.

引用规范中的多条指令可能导致任意统一资源标识符(URI)被取消引用。在这种情况下,应考虑[RFC3986]第7节的安全问题。

In addition, because of the extensibility features of those specifications, it is possible that the registered media types may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of the specifications, this content will be ignored. Only in the case where the processor recognizes and processes the additional content, or where further processing of that content is dispatched to other processors, would security issues potentially arise. And in that case, they would fall outside the domain of this registration document.

此外,由于这些规范的可扩展性特征,注册的媒体类型可能描述具有超出此处所述安全含义的内容。但是,如果处理器仅遵循规范的规范语义,则此内容将被忽略。只有在处理者识别并处理附加内容的情况下,或者在将该内容的进一步处理分派给其他处理者的情况下,才可能出现安全问题。在这种情况下,它们将不属于本注册文件的范围。

2.6. Additional Information
2.6. 补充资料
2.6.1. Magic Numbers
2.6.1. 幻数

Although no byte sequences can be counted on to always be present, XML MIME entities in ASCII-compatible charsets (including UTF-8) often begin with hexadecimal 3C 3F 78 6D 6C ("<?xml"), and those in UTF-16 often begin with hexadecimal FE FF 00 3C 00 3F 00 78 00 6D 00 6C or FF FE 3C 00 3F 00 78 00 6D 00 6C 00 (the Byte Order Mark (BOM) followed by "<?xml"). For more information, see Appendix F of [XML].

虽然不能指望总是存在字节序列,但ASCII兼容字符集(包括UTF-8)中的XML MIME实体通常以十六进制3C 3F 78 6D 6C(“XML”)开头,而UTF-16中的XML MIME实体通常以十六进制FE FF 00 3C 00 3F 00 78 00 6D 00 6C或FF FE 3C 00 3F 00 78 00 6D 00 6C 00(字节顺序标记(BOM)开头后跟“<?xml”)。有关更多信息,请参见[XML]的附录F。

2.6.2. File Extensions
2.6.2. 文件扩展名

VoiceXML files: .vxml

VoiceXML文件:.vxml

SSML files: .ssml

SSML文件:.SSML

SRGS files (XML syntax): .grxml

SRGS文件(XML语法):.grxml

CCXML files: .ccxml

CCXML文件:.CCXML

PLS files: .pls

PLS文件:。PLS

2.6.3. Fragment Identifiers
2.6.3. 片段标识符

Identical to that of "application/xml" as described in RFC 3023 [RFC3023], section 5.

与RFC 3023[RFC3023]第5节中所述的“应用程序/xml”相同。

2.6.4. Macintosh File Type Code
2.6.4. Macintosh文件类型代码

"TEXT"

“文本”

2.6.5. Person and Email Address to Contact for Further Information
2.6.5. 联系人和电子邮件地址,以获取更多信息
   World Wide Web Consortium <web-human@w3.org>
        
   World Wide Web Consortium <web-human@w3.org>
        
2.6.6. Intended Usage
2.6.6. 预期用途

COMMON

常见的

2.6.7. Change Controller
2.6.7. 更改控制器

The Speech Interface Framework specifications set is a work product of the World Wide Web Consortium's Voice Browser Working Group. The W3C has change control over these specifications.

语音接口框架规范集是万维网联盟语音浏览器工作组的工作成果。W3C对这些规范具有变更控制权。

3. Registration of application/srgs
3. 申请登记/SRG

MIME media type name: application

MIME媒体类型名称:应用程序

MIME subtype names: srgs

MIME子类型名称:srgs

Required parameters: none

所需参数:无

Optional parameters: none

可选参数:无

3.1. Encoding Considerations
3.1. 编码注意事项

The ABNF Form of SRGS follows the character encoding handling defined for XML: an ABNF grammar processor must accept both the UTF-8 and UTF-16 encodings of ISO/IEC 10646 and may support other character encodings.

SRG的ABNF格式遵循为XML定义的字符编码处理:ABNF语法处理器必须同时接受ISO/IEC 10646的UTF-8和UTF-16编码,并且可以支持其他字符编码。

3.2. Interoperability Considerations
3.2. 互操作性注意事项

There are no known interoperability issues.

没有已知的互操作性问题。

3.3. Published Specifications
3.3. 公布的规格

Speech Recognition Grammar Specification Version 1.0 [SRGS]

语音识别语法规范1.0版[SRGS]

3.4. Applications That Use This Media Type
3.4. 使用此媒体类型的应用程序

Various SRGS implementations use this media type.

各种SRG实现都使用这种媒体类型。

3.5. Security Considerations
3.5. 安全考虑

Several instructions in SRGS may cause arbitrary URIs to be dereferenced. In this case, the security issues of [RFC3986], section 7, should be considered.

SRG中的多条指令可能会导致任意URI被取消引用。在这种情况下,应考虑[RFC3986]第7节的安全问题。

In addition, because of the extensibility features of SRGS, it is possible that the registered media types may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of the specifications, this content will be ignored. Only in the case where the processor recognizes and processes the additional content, or where further processing of that content is dispatched to other processors, would security issues potentially arise. In that case, they would fall outside the domain of this registration document.

此外,由于SRG的可扩展性特征,注册的媒体类型可能会描述具有超出此处所述安全含义的内容。但是,如果处理器仅遵循规范的规范语义,则此内容将被忽略。只有在处理者识别并处理附加内容的情况下,或者在将该内容的进一步处理分派给其他处理者的情况下,才可能出现安全问题。在这种情况下,它们将不属于本注册文件的范围。

3.6. Additional Information
3.6. 补充资料
3.6.1. Magic Numbers
3.6.1. 幻数

The ABNF self-identifying header must be present in any legal stand-alone ABNF Form grammar document. The first character of an ABNF document must be the "#" symbol (x23) unless preceded by an optional XML 1.0 byte order mark. The ABNF byte order mark follows the XML definition and requirements. For example, documents encoded in UTF-16 must begin with the byte order mark. The optional byte order mark and required "#" symbol must be followed immediately by the exact string "ABNF" (x41 x42 x4d x46) or the appropriate equivalent for the document's encoding (e.g., for UTF-16 little-endian: x23 x00 x41 x00 x42 x00 x4d x00 x46 x00). If the byte order mark is absent on a grammar encoded in UTF-16, then the grammar processor should perform auto-detection of character encoding in a manner analogous to auto-detection of character encoding in XML. Next follows a single-space character (x20) and the required version number, which is "1.0" for this specification (x31 x2e x30).

ABNF自识别头必须出现在任何合法的独立ABNF格式语法文档中。ABNF文档的第一个字符必须是“#”符号(x23),除非前面有可选的XML 1.0字节顺序标记。ABNF字节顺序标记遵循XML定义和要求。例如,以UTF-16编码的文档必须以字节顺序标记开头。可选的字节顺序标记和所需的“#”符号后面必须紧跟着精确的字符串“ABNF”(x41 x42 x4d x46)或文档编码的相应等效字符串(例如,对于UTF-16小端码:x23 x00 x41 x00 x42 x00 x4d x00 x46 x00)。如果UTF-16中编码的语法上没有字节顺序标记,那么语法处理器应该以类似于XML中字符编码的自动检测的方式执行字符编码的自动检测。接下来是一个空格字符(x20)和所需的版本号,对于本规范(x31 x2e x30),该版本号为“1.0”。

3.6.2. File Extensions
3.6.2. 文件扩展名

.gram

3.6.3. Macintosh File Type Code
3.6.3. Macintosh文件类型代码

"TEXT"

“文本”

3.6.4. Person and Email Address to Contact for Further Information
3.6.4. 联系人和电子邮件地址,以获取更多信息
   World Wide Web Consortium <web-human@w3.org>
        
   World Wide Web Consortium <web-human@w3.org>
        
3.6.5. Intended Usage
3.6.5. 预期用途

COMMON

常见的

3.6.6. Change Controller
3.6.6. 更改控制器

The SRGS specification is a work product of the World Wide Web Consortium's Voice Browser Working Group. The W3C has change control over the SRGS specification.

SRGS规范是万维网联盟语音浏览器工作组的工作成果。W3C对SRGS规范具有变更控制权。

4. IANA Considerations
4. IANA考虑

This document registers six new MIME media types, according to the registrations in Section 2 and Section 3.

根据第2节和第3节中的注册,本文档注册了六种新的MIME媒体类型。

5. Normative References
5. 规范性引用文件

[CCXML] Auburn, RJ., Ed., "Voice Browser Call Control: CCXML Version 1.0, W3C Working Draft", January 2005, <http://www.w3.org/TR/2005/WD-ccxml-20050111/>.

[CCXML]Auburn,RJ.,编辑,“语音浏览器呼叫控制:CCXML 1.0版,W3C工作草案”,2005年1月<http://www.w3.org/TR/2005/WD-ccxml-20050111/>.

[PLS] Baggia, P., Ed., "Pronunciation Lexicon Specification (PLS) Version 1.0, W3C Working Draft", February 2005, <http://w3.org/TR/2005/WD-pronunciation-lexicon-20050214/>.

[PLS]Baggia,P.,Ed.“语音词典规范(PLS)1.0版,W3C工作草案”,2005年2月<http://w3.org/TR/2005/WD-pronunciation-lexicon-20050214/>.

[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.

[RFC3986]Berners Lee,T.,Fielding,R.,和L.Masinter,“统一资源标识符(URI):通用语法”,STD 66,RFC 3986,2005年1月。

[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001.

[RFC3023]Murata,M.,St.Laurent,S.,和D.Kohn,“XML媒体类型”,RFC 3023,2001年1月。

[SRGS] Hunt, A., Ed. and S. McGlashan, Ed., "Speech Recognition Grammar Specification Version 1.0, W3C Recommendation", March 2004, <http://www.w3.org/TR/2004/REC-speech-grammar-20040316/>.

[SRGS]Hunt,A.,Ed.和S.McGrashan,Ed.,“语音识别语法规范1.0版,W3C建议”,2004年3月<http://www.w3.org/TR/2004/REC-speech-grammar-20040316/>.

[SSML] Burnett, D., Ed., Walker, M., Ed., and A. Hunt, Ed., "Speech Synthesis Markup Language (SSML) Version 1.0, W3C Recommendation", September 2004, <http://www.w3.org/TR/2004/REC-speech-synthesis-20040907/>.

[SSML]Burnett,D.,Ed.,Walker,M.,Ed.,和A.Hunt,Ed.,“语音合成标记语言(SSML)1.0版,W3C建议”,2004年9月<http://www.w3.org/TR/2004/REC-speech-synthesis-20040907/>.

[VoiceXML2.0] McGlashan, S., Ed., "Voice Extensible Markup Language (VoiceXML) Version 2.0, W3C Recommendation", March 2004, <http://www.w3.org/TR/2004/REC-voicexml20- 20040316/>.

[VoiceXML2.0]McGrashan,S.,Ed.,“语音可扩展标记语言(VoiceXML)2.0版,W3C建议”,2004年3月<http://www.w3.org/TR/2004/REC-voicexml20- 20040316/>.

[VoiceXML2.1] Oshry, M., Ed., "Voice Extensible Markup Language (VoiceXML) Version 2.1, W3C Working Draft", July 2004, <http://www.w3.org/TR/2004/WD-voicexml21-20040728/>.

[VoiceXML2.1]Oshry,M.,Ed.“语音可扩展标记语言(VoiceXML)2.1版,W3C工作草案”,2004年7月<http://www.w3.org/TR/2004/WD-voicexml21-20040728/>.

[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third Edition)", February 2004, <http://www.w3.org/TR/2004/REC-xml-20040204/>.

[XML]Bray,T.,Paoli,J.,Sperberg McQueen,C.,Maler,E.,和F.Yergeau,“可扩展标记语言(XML)1.0(第三版)”,2004年2月<http://www.w3.org/TR/2004/REC-xml-20040204/>.

Author's Address

作者地址

Max Froumentin World Wide Web Consortium

Max Froumentin万维网联盟

   EMail: mf@w3.org
        
   EMail: mf@w3.org
        

Full Copyright Statement

完整版权声明

Copyright (C) The Internet Society (2005).

版权所有(C)互联网协会(2005年)。

This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

本文件受BCP 78中包含的权利、许可和限制的约束,除其中规定外,作者保留其所有权利。

This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.

本文件及其包含的信息是按“原样”提供的,贡献者、他/她所代表或赞助的组织(如有)、互联网协会和互联网工程任务组不承担任何明示或暗示的担保,包括但不限于任何保证,即使用本文中的信息不会侵犯任何权利,或对适销性或特定用途适用性的任何默示保证。

Intellectual Property

知识产权

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围,或此类权利下的任何许可可能或可能不可用的程度,不采取任何立场;它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息,请参见BCP 78和BCP 79。

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

向IETF秘书处披露的知识产权副本和任何许可证保证,或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果,可从IETF在线知识产权存储库获取,网址为http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.

IETF邀请任何相关方提请其注意任何版权、专利或专利申请,或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.

Acknowledgement

确认

Funding for the RFC Editor function is currently provided by the Internet Society.

RFC编辑功能的资金目前由互联网协会提供。