Network Working Group B. Korver
Request for Comments: 4331 Network Resonance
Category: Standards Track L. Dusseault
OSAF
February 2006
Network Working Group B. Korver
Request for Comments: 4331 Network Resonance
Category: Standards Track L. Dusseault
OSAF
February 2006
Quota and Size Properties for Distributed Authoring and Versioning (DAV) Collections
分布式创作和版本控制（DAV）集合的配额和大小属性
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 (2006).
版权所有（C）互联网协会（2006年）。
Abstract
摘要
Web Distributed Authoring and Versioning (WebDAV) servers are frequently deployed with quota (size) limitations. This document discusses the properties and minor behaviors needed for clients to interoperate with quota (size) implementations on WebDAV repositories.
Web分布式创作和版本控制（WebDAV）服务器的部署通常有配额（大小）限制。本文档讨论客户端与WebDAV存储库上的配额（大小）实现互操作所需的属性和次要行为。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Notational Conventions .....................................2
1.2. Requirement for Quotas .....................................2
2. Solution Overview ...............................................3
3. DAV:quota-available-bytes .......................................3
4. DAV:quota-used-bytes ............................................4
5. Example PROPFIND Request and Response ...........................5
6. Error Reporting .................................................6
7. Notes ...........................................................6
8. Security Considerations .........................................8
9. Internationalization Considerations .............................8
10. Acknowledgements ...............................................8
11. References .....................................................8
11.1. Normative References ......................................8
11.2. Informative References ....................................8
1. Introduction ....................................................2
1.1. Notational Conventions .....................................2
1.2. Requirement for Quotas .....................................2
2. Solution Overview ...............................................3
3. DAV:quota-available-bytes .......................................3
4. DAV:quota-used-bytes ............................................4
5. Example PROPFIND Request and Response ...........................5
6. Error Reporting .................................................6
7. Notes ...........................................................6
8. Security Considerations .........................................8
9. Internationalization Considerations .............................8
10. Acknowledgements ...............................................8
11. References .....................................................8
11.1. Normative References ......................................8
11.2. Informative References ....................................8
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
The definition of live property is provided in [RFC2518]. The definition of protected and computed properties is provided in [RFC3253], Section 1.4.
[RFC2518]中提供了活动财产的定义。[RFC3253]第1.4节提供了受保护和计算属性的定义。
WebDAV servers based on [RFC2518] have been implemented and deployed with quota restrictions on collections and users, so it makes sense to standardize this functionality to improve user experience and client interoperability.
基于[RFC2518]的WebDAV服务器的实现和部署对集合和用户具有配额限制，因此有必要对该功能进行标准化，以改善用户体验和客户端互操作性。
The reasons why WebDAV servers frequently have quotas enforced are the same reasons why any storage system comes with quotas.
WebDAV服务器经常强制执行配额的原因与任何存储系统都带有配额的原因相同。
o Sometimes the storage service charges according to quota.
o 有时存储服务按配额收费。
o Sometimes the storage service is provided free, but the storage service provider has limited storage space (e.g., university-provided student accounts).
o 有时，存储服务是免费提供的，但存储服务提供商的存储空间有限（例如，大学提供的学生帐户）。
o Even in cases where the storage can be upgraded, the storage managers may choose to limit quota in order to encourage users to limit the files they store on the system and to clean up obsolete files (e.g., IT departments within corporations).
o 即使在可以升级存储的情况下，存储经理也可以选择限制配额，以鼓励用户限制他们存储在系统上的文件，并清理过时的文件（例如，公司内的IT部门）。
In order to work best with repositories that support quotas, client software should be able to determine and display the DAV:quota-available-bytes (defined below) on collections. Further, client software should have some way of fairly reliably determining how much storage space is already counted towards that quota.
为了更好地与支持配额的存储库配合使用，客户端软件应该能够确定并显示集合上的DAV:quota可用字节（定义如下）。此外，客户端软件应该有某种方法可以相当可靠地确定该配额中已经计算了多少存储空间。
Support for the properties defined in this document enhances the client experience, because the client has a chance of managing its files to avoid running out of allocated storage space. Clients may not be able to calculate the value as accurately on their own, depending on how total space used is calculated by the server.
对本文档中定义的属性的支持增强了客户端体验，因为客户端有机会管理其文件以避免耗尽分配的存储空间。客户端可能无法自行准确地计算该值，这取决于服务器计算使用的总空间的方式。
The approach to meeting the requirements and scenarios outlined above is to define two live properties. This specification can be met on a server by implementing both DAV:quota-available-bytes and DAV:quota-used-bytes on collections only.
满足上述要求和场景的方法是定义两个活动属性。通过仅在集合上实现DAV:quota available字节和DAV:quota used字节，可以在服务器上满足此规范。
A <DAV:allprop> PROPFIND request SHOULD NOT return any of the properties defined by this document. However, these property names MUST be returned in a <DAV:propname> request for a resource that supports the properties, except in the case of infinite limits, which are explained below.
<DAV:allprop>PROPFIND请求不应返回此文档定义的任何属性。但是，这些属性名称必须在支持属性的资源的<DAV:propname>请求中返回，无限限制的情况除外，如下所述。
The DAV:quota-available-bytes and DAV:quota-used-bytes definitions below borrow heavily from the quota definitions in the Network File System (NFS) [RFC3530] specification.
下面的DAV:quota available bytes和DAV:quota used bytes定义大量借用了网络文件系统（NFS）[RFC3530]规范中的配额定义。
Name: quota-available-bytes
名称：配额可用字节数
Namespace: DAV:
名称空间：DAV:
Purpose: Indicates the maximum amount of additional storage available to be allocated to a resource.
用途：表示可分配给资源的最大附加存储容量。
DTD: <!ELEMENT quota-available-bytes (#PCDATA) >
DTD: <!ELEMENT quota-available-bytes (#PCDATA) >
The DAV:quota-available-bytes property value is the value in octets representing the amount of additional disk space beyond the current allocation that can be allocated to this resource before further allocations will be refused. It is understood that this space may be consumed by allocations to other resources.
DAV:quota available bytes属性值是以八位字节为单位的值，表示在拒绝进一步分配之前，当前分配之外可以分配给此资源的额外磁盘空间量。可以理解，该空间可能会被分配给其他资源所消耗。
Support for this property is REQUIRED on collections, and OPTIONAL on other resources. A server SHOULD implement this property for each resource that has the DAV:quota-used-bytes property.
集合上需要支持此属性，其他资源上支持此属性是可选的。服务器应为具有DAV:quota used bytes属性的每个资源实现此属性。
Clients SHOULD expect that as the DAV:quota-available-bytes on a resource approaches 0, further allocations to that resource may be refused. A value of 0 indicates that users will probably not be able to perform operations that write additional information (e.g., a PUT inside a collection), but may be able to replace through overwrite an existing resource of equal size.
客户端应该预料到，当资源上的DAV:quota可用字节接近0时，对该资源的进一步分配可能会被拒绝。值为0表示用户可能无法执行写入附加信息的操作（例如，集合中的PUT），但可以通过覆盖同等大小的现有资源进行替换。
Note that there may be a number of distinct but overlapping limits, which may even include physical media limits. When reporting DAV: quota-available-bytes, the server is at liberty to choose any of
请注意，可能存在许多不同但重叠的限制，甚至可能包括物理介质限制。报告DAV:quota available bytes时，服务器可以自由选择以下任何一个字节：
those limits but SHOULD do so in a repeatable way. The rule may be configured per repository, or may be "choose the smallest number".
这些限制，但应以可重复的方式进行。规则可以按存储库配置，也可以是“选择最小数量”。
If a resource has no quota enforced or unlimited storage ("infinite limits"), the server MAY choose not to return this property (404 Not Found response in Multi-Status), although this specification RECOMMENDS that servers return some appropriate value (e.g., the amount of free disk space). A client cannot entirely assume that there is no quota enforced on a resource that does not have this property, but might as well act as if there is no quota.
如果资源没有配额强制或无限存储（“无限限制”），服务器可以选择不返回此属性（404未找到多状态响应），尽管本规范建议服务器返回一些适当的值（例如，可用磁盘空间量）。客户机不能完全假定对不具有此属性的资源没有强制的配额，但也可能表现为没有配额。
The value of this property is protected (see Section 1.4.2 of [RFC3253] for the definition of protected properties). A 403 Forbidden response is RECOMMENDED for attempts to write a protected property, and the server SHOULD include an XML error body as defined by DeltaV [RFC3253] with the <DAV:cannot-modify-protected-property/> precondition tag.
该财产的价值受到保护（受保护财产的定义见[RFC3253]第1.4.2节）。建议尝试写入受保护的属性时使用403禁止响应，并且服务器应包含由DeltaV[RFC3253]定义的XML错误体，并带有<DAV:cannot modify protected property/>前置条件标记。
Name: quota-used-bytes
名称：配额已用字节数
Namespace: DAV:
名称空间：DAV:
Purpose: Contains the amount of storage counted against the quota on a resource.
目的：包含根据资源配额计算的存储量。
DTD: <!ELEMENT quota-used-bytes (#PCDATA) >
DTD: <!ELEMENT quota-used-bytes (#PCDATA) >
The DAV:quota-used-bytes value is the value in octets representing the amount of space used by this resource and possibly a number of other similar resources, where the set of "similar" meets at least the criterion that allocating space to any resource in the set will count against the DAV:quota-available-bytes. It MUST include the total count including usage derived from sub-resources if appropriate. It SHOULD include metadata storage size if metadata storage is counted against the DAV:quota-available-bytes.
DAV:quota used bytes值是以八位字节为单位的值，表示此资源以及可能的许多其他类似资源所使用的空间量，其中“相似”集合至少满足将空间分配给集合中的任何资源将计入DAV:quota available bytes的标准。它必须包括总计数，包括从子资源派生的使用情况（如果适用）。如果元数据存储是根据DAV:quota-available字节计数的，那么它应该包括元数据存储大小。
Note that there may be a number of distinct but overlapping sets of resources for which a DAV:quota-used-bytes is maintained (e.g., "all files with a given owner", "all files with a given group owner", etc.). The server is at liberty to choose any of those sets but SHOULD do so in a repeatable way. The rule may be configured per repository.
请注意，可能存在许多不同但重叠的资源集，其中维护了DAV:配额使用字节（例如，“具有给定所有者的所有文件”、“具有给定组所有者的所有文件”等）。服务器可以自由选择这些集合中的任何一个，但应以可重复的方式进行选择。可以为每个存储库配置该规则。
Support for this property is REQUIRED on collections, and OPTIONAL on other resources. A server SHOULD implement this property for each resource that has the DAV:quota-available-bytes property.
集合上需要支持此属性，其他资源上支持此属性是可选的。服务器应该为每个具有DAV:quota-available-bytes属性的资源实现此属性。
This value of this property is computed (see Section 1.4.3 of [RFC3253] for the definition of computed property). A 403 Forbidden response is RECOMMENDED for attempts to write a protected property, and the server SHOULD include an XML error body as defined by DeltaV [RFC3253] with the <DAV:cannot-modify-protected-property/> precondition tag.
计算该属性的该值（有关计算属性的定义，请参见[RFC3253]第1.4.3节）。建议尝试写入受保护的属性时使用403禁止响应，并且服务器应包含由DeltaV[RFC3253]定义的XML错误体，并带有<DAV:cannot modify protected property/>前置条件标记。
Request:
请求：
PROPFIND /~milele/public/ HTTP/1.1
Depth: 0
Host: www.example.com
Content-Type: text/xml
Content-Length: xxx
PROPFIND /~milele/public/ HTTP/1.1
Depth: 0
Host: www.example.com
Content-Type: text/xml
Content-Length: xxx
<?xml version="1.0" ?>
<D:propfind xmlns:D="DAV:">
<D:prop>
<D:quota-available-bytes/>
<D:quota-used-bytes/>
</D:prop>
</D:propfind>
<?xml version="1.0" ?>
<D:propfind xmlns:D="DAV:">
<D:prop>
<D:quota-available-bytes/>
<D:quota-used-bytes/>
</D:prop>
</D:propfind>
Response:
答复：
HTTP/1.1 207 Multi-Status
Date: Tue, 16 Oct 2001 22:13:39 GMT
Content-Length: xxx
Content-Type: text/xml; charset=UTF-8
HTTP/1.1 207 Multi-Status
Date: Tue, 16 Oct 2001 22:13:39 GMT
Content-Length: xxx
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:">
<D:response>
<D:href>http://www.example.com/~milele/public/</D:href>
<D:propstat>
<D:prop>
<D:quota-available-bytes>596650</D:quota-available-bytes>
<D:quota-used-bytes>403350</D:quota-used-bytes>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>
<?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:">
<D:response>
<D:href>http://www.example.com/~milele/public/</D:href>
<D:propstat>
<D:prop>
<D:quota-available-bytes>596650</D:quota-available-bytes>
<D:quota-used-bytes>403350</D:quota-used-bytes>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>
WebDAV [RFC2518] defines the status code 507 (Insufficient Storage). This status code SHOULD be used when a client request (e.g., a PUT, PROPFIND, MKCOL, MOVE, or COPY) fails because it would exceed their quota or physical storage limits. In order to differentiate the response from other storage problems, the server SHOULD include an XML error body as defined by DeltaV [RFC3253] with the appropriate precondition tag.
WebDAV[RFC2518]定义状态代码507（存储不足）。当客户端请求（例如PUT、PROPFIND、MKCOL、MOVE或COPY）因超出其配额或物理存储限制而失败时，应使用此状态代码。为了将响应与其他存储问题区分开来，服务器应该包含一个由DeltaV[RFC3253]定义的XML错误体，并带有适当的前置条件标记。
Preconditions:
先决条件：
(DAV:quota-not-exceeded): the request MUST NOT cause the allocated quota to be exceeded.
（DAV：未超出配额）：请求不得导致超出分配的配额。
(DAV:sufficient-disk-space): there is sufficient physical space to execute the request.
（DAV：足够的磁盘空间）：有足够的物理空间来执行请求。
Example error response:
错误响应示例：
HTTP/1.1 507 Insufficient Storage
Content-Length: xxx
Content-Type: text/xml
HTTP/1.1 507 Insufficient Storage
Content-Length: xxx
Content-Type: text/xml
<?xml version="1.0">
<error xmlns="DAV:">
<quota-not-exceeded/>
</error>
<?xml version="1.0">
<error xmlns="DAV:">
<quota-not-exceeded/>
</error>
Implementation note: some clients may be able to take advantage of the different precondition codes when mapping to operating system status codes, such as E_NOSPC and E_DQUOT in NFS (see [RFC3530], Section 12).
实施说明：在映射到操作系统状态代码时，某些客户端可能能够利用不同的前提条件代码，例如NFS中的E_NOSPC和E_DQUOT（请参阅[RFC3530]，第12节）。
Server implementations store and account for their data in many different ways. Some of the challenges:
服务器实现以多种不同的方式存储和解释其数据。其中一些挑战：
o Some server implementations find it prohibitive to count storage used for metadata; others may choose to do so for better accounting.
o 一些服务器实现发现无法统计用于元数据的存储量；其他人可能会选择这样做，以便更好地进行会计核算。
o Older versions of resources may be stored as well.
o 也可以存储较旧版本的资源。
o Variants of one resource may exist with different content lengths.
o 一种资源的变体可能存在不同的内容长度。
o Content may be dynamically generated.
o 内容可以动态生成。
o Resource bodies can be compressed.
o 资源体可以被压缩。
o Some resources may be stored for "free", not counting against quota.
o 有些资源可能是“免费”存储的，不计入配额。
Since server storage accounting can vary so much, clients should expect the following:
由于服务器存储记帐可能会变化很大，因此客户端应该期望以下情况：
o The size of a file on the client's file system, or in a PUT message, may not correspond to the amount of storage required by the server to store the resource. Thus, the client cannot predict with 100% accuracy whether a given file will be allowed given the storage quota.
o 客户端文件系统上或PUT消息中的文件大小可能与服务器存储资源所需的存储量不一致。因此，客户机无法100%准确地预测给定的存储配额是否允许给定的文件。
o Deleting or overwriting a resource may not free up the same amount of storage as indicated by the DAV:getcontentlength property defined in [RFC2518] for the resource. If deleting a resource does not free up any space, the file may have been moved to a "trash" folder or "recycle bin", or retained as in versioning systems ([RFC3253]).
o 删除或覆盖资源可能无法释放与[RFC2518]中为资源定义的DAV:getcontentlength属性所指示的存储量相同的存储量。如果删除资源没有释放任何空间，则该文件可能已被移动到“垃圾箱”文件夹或“回收站”，或在版本控制系统（[RFC3253]）中保留。
o Since there are many factors that affect the storage used by a set of resources, including automatic compression, the size of associated metadata, and server-inserted content (such as that created by PHP code) in the on-the-wire representation of resources, clients are advised not to depend on the value of DAV: quota-used-bytes being the sum of the DAV:getcontentlength properties for resources contained by a collection.
o 由于有许多因素会影响一组资源所使用的存储，包括自动压缩、关联元数据的大小以及资源在线表示中服务器插入的内容（如PHP代码创建的内容），建议客户端不要依赖于DAV:quota used bytes的值，该值是集合包含的资源的DAV:getcontentlength属性的总和。
o Additionally, because there may be a number of distinct but overlapping sets of resources for which a DAV:quota-used-bytes is maintained (Section 4), there may be no correlation between the size of the resources in a collection and DAV:quota-used-bytes. For example, for a server that implements user-based quotas, DAV:quota-used-bytes usually will be the same for a collection and its members.
o 此外，由于可能存在许多不同但重叠的资源集，这些资源集的DAV:quota used字节被维护（第4节），因此集合中的资源大小与DAV:quota used字节之间可能没有相关性。例如，对于实现基于用户的配额的服务器，集合及其成员的DAV:quota used字节通常相同。
o On some systems where quota is counted by collection and not by user, a quota on a sub-collection may be larger than the quota on the parent collection that contains it. For example, the quota on /~milele/ may be 100 MB, but the quota on /~milele/public/ may be unlimited. This allows the space used by /~milele/public/ to be as large as the quota on /~milele/ allows (depending on the other contents of /~milele/) even if the quota on /~milele/ is changed. Thus, even when the quota on a parent collection is changed, it is not necessarily required to change the quota on every child or descendant collection.
o 在某些系统中，配额是按集合而不是按用户计数的，子集合上的配额可能大于包含它的父集合上的配额。例如，/~milele/上的配额可能是100 MB，但/~milele/public/上的配额可能是无限的。这允许/~milele/public/使用的空间与/~milele/allows上的配额一样大（取决于/~milele/的其他内容），即使/~milele/上的配额已更改。因此，即使更改了父集合上的配额，也不一定要更改每个子集合或子集合上的配额。
A hacker may prefer to store files in collections with a large quota. This isn't strictly a security concern because it doesn't make it any easier to store files. On the other hand, the DAV:quota-used-bytes property may make it easier to detect tampering or misuse.
黑客可能更喜欢将文件存储在配额较大的集合中。严格来说，这不是一个安全问题，因为它不会使存储文件变得更容易。另一方面，DAV:quota-used-bytes属性可能更容易检测篡改或误用。
Quota is counted in Arabic numerals expressed in strings. There are no internationalization considerations.
配额以字符串表示的阿拉伯数字计算。没有国际化的考虑。
Stefan Eissing, Geoff Clemm, Jim Luther, Julian Reschke, and Jim Whitehead, among others, have provided valuable comments on this document.
Stefan Eissing、Geoff Clemm、Jim Luther、Julian Reschke和Jim Whitehead等人对本文件提出了宝贵意见。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. Jensen, "HTTP Extensions for Distributed Authoring -- WebDAV", RFC 2518, February 1999.
[RFC2518]Goland，Y.，Whitehead，E.，Faizi，A.，Carter，S.，和D.Jensen，“分布式创作的HTTP扩展——WebDAV”，RFC25181999年2月。
[RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. Whitehead, "Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)", RFC 3253, March 2002.
[RFC3253]Clemm，G.，Amsden，J.，Ellison，T.，Kaler，C.，和J.Whitehead，“WebDAV的版本控制扩展（Web分布式创作和版本控制）”，RFC 3253，2002年3月。
[RFC3530] Shepler, S., Callaghan, B., Robinson, D., Thurlow, R., Beame, C., Eisler, M., and D. Noveck, "Network File System (NFS) version 4 Protocol", RFC 3530, April 2003.
[RFC3530]Shepler，S.，Callaghan，B.，Robinson，D.，Thurlow，R.，Beame，C.，Eisler，M.，和D.Noveck，“网络文件系统（NFS）版本4协议”，RFC 3530，2003年4月。
Authors' Addresses
作者地址
Brian Korver Network Resonance, Inc. 2483 E. Bayshore Road Suite 212 Palo Alto, CA 94303 US
Brian Korver Network Resonance，Inc.美国加利福尼亚州帕洛阿尔托市海湾大道东2483号212室，邮编94303
Phone: +1 650 812-7705
EMail: briank@networkresonance.com
Phone: +1 650 812-7705
EMail: briank@networkresonance.com
Lisa Dusseault Open Source Applications Foundation 543 Howard Street 5th Floor San Francisco, CA 94105 US
丽莎DuSaunt开源应用基金会543霍华德街第五楼，CA旧金山94105美国
Phone: +1 415 946-3040
EMail: lisa@osafoundation.org
Phone: +1 415 946-3040
EMail: lisa@osafoundation.org
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2006).
版权所有（C）互联网协会（2006年）。
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 provided by the IETF Administrative Support Activity (IASA).
RFC编辑器功能的资金由IETF行政支持活动（IASA）提供。