Network Working Group L. Masinter
Request for Comments: 2324 1 April 1998
Category: Informational
Network Working Group L. Masinter
Request for Comments: 2324 1 April 1998
Category: Informational
Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
超文本咖啡壶控制协议（HTCPCP/1.0）
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 (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
Abstract
摘要
This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots.
本文档描述了HTCPCP，一种用于控制、监控和诊断咖啡壶的协议。
There is coffee all over the world. Increasingly, in a world in which computing is ubiquitous, the computists want to make coffee. Coffee brewing is an art, but the distributed intelligence of the web-connected world transcends art. Thus, there is a strong, dark, rich requirement for a protocol designed espressoly for the brewing of coffee. Coffee is brewed using coffee pots. Networked coffee pots require a control protocol if they are to be controlled.
全世界都有咖啡。在一个计算机无处不在的世界里，计算机工作者越来越想煮咖啡。咖啡酿造是一门艺术，但网络世界的分布式智能超越了艺术。因此，有一个强大的，黑暗的，丰富的要求，一个协议设计的浓缩咖啡酿造咖啡。咖啡是用咖啡壶煮的。如果要控制联网咖啡壶，则需要控制协议。
Increasingly, home and consumer devices are being connected to the Internet. Early networking experiments demonstrated vending devices connected to the Internet for status monitoring [COKE]. One of the first remotely _operated_ machine to be hooked up to the Internet, the Internet Toaster, (controlled via SNMP) was debuted in 1990 [RFC2235].
家庭和消费设备越来越多地连接到互联网。早期的网络实验表明，自动售货机连接到互联网上进行状态监控[COKE]。互联网烤面包机（通过SNMP控制）是第一台连接到互联网的远程操作机器之一，于1990年首次亮相[RFC2235]。
The demand for ubiquitous appliance connectivity that is causing the consumption of the IPv4 address space. Consumers want remote control of devices such as coffee pots so that they may wake up to freshly brewed coffee, or cause coffee to be prepared at a precise time after the completion of dinner preparations.
对无处不在的设备连接的需求导致了IPv4地址空间的消耗。消费者希望对咖啡壶等设备进行远程控制，这样他们就可以在刚煮好的咖啡中醒来，或者在晚餐准备完成后的准确时间准备咖啡。
This document specifies a Hyper Text Coffee Pot Control Protocol (HTCPCP), which permits the full request and responses necessary to control all devices capable of making the popular caffeinated hot beverages.
本文件规定了超文本咖啡壶控制协议（HTCPCP），该协议允许控制所有能够制作流行含咖啡因热饮料的设备所需的完整请求和响应。
HTTP 1.1 ([RFC2068]) permits the transfer of web objects from origin servers to clients. The web is world-wide. HTCPCP is based on HTTP. This is because HTTP is everywhere. It could not be so pervasive without being good. Therefore, HTTP is good. If you want good coffee, HTCPCP needs to be good. To make HTCPCP good, it is good to base HTCPCP on HTTP.
HTTP 1.1（[RFC2068]）允许将web对象从源服务器传输到客户端。网络是世界性的。HTCPCP是基于HTTP的。这是因为HTTP无处不在。如果不好，它就不可能如此普及。因此，HTTP是好的。如果你想要好的咖啡，HTCPCP必须是好的。为了使HTCPCP更好，最好将HTCPCP建立在HTTP之上。
Future versions of this protocol may include extensions for espresso machines and similar devices.
该协议的未来版本可能包括对浓缩咖啡机和类似设备的扩展。
The HTCPCP protocol is built on top of HTTP, with the addition of a few new methods, header fields and return codes. All HTCPCP servers should be referred to with the "coffee:" URI scheme (Section 4).
HTCPCP协议构建在HTTP之上，添加了一些新方法、头字段和返回代码。所有HTCPCP服务器都应使用“coffee:”URI方案（第4节）进行引用。
Commands to control a coffee pot are sent from client to coffee server using either the BREW or POST method, and a message body with Content-Type set to "application/coffee-pot-command".
使用BREW或POST方法以及内容类型设置为“application/coffee pot command”的消息正文，将控制咖啡壶的命令从客户端发送到咖啡服务器。
A coffee pot server MUST accept both the BREW and POST method equivalently. However, the use of POST for causing actions to happen is deprecated.
咖啡壶服务器必须等效地接受BREW和POST方法。但是，不推荐使用POST导致操作发生。
Coffee pots heat water using electronic mechanisms, so there is no fire. Thus, no firewalls are necessary, and firewall control policy is irrelevant. However, POST may be a trademark for coffee, and so the BREW method has been added. The BREW method may be used with other HTTP-based protocols (e.g., the Hyper Text Brewery Control Protocol).
咖啡壶使用电子装置加热水，所以没有火。因此，不需要防火墙，防火墙控制策略也无关紧要。然而，POST可能是咖啡的商标，因此添加了BREW方法。BREW方法可与其他基于HTTP的协议（如超文本啤酒厂控制协议）一起使用。
In HTTP, the GET method is used to mean "retrieve whatever information (in the form of an entity) identified by the Request-URI." If the Request-URI refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not the source text of the process, unless that text happens to be the output of the process.
在HTTP中，GET方法用于表示“检索由请求URI标识的任何信息（以实体的形式）。如果请求URI指的是数据生成过程，则应将生成的数据作为响应中的实体返回，而不是过程的源文本，除非该文本恰好是流程的输出。
In HTCPCP, the resources associated with a coffee pot are physical, and not information resources. The "data" for most coffee URIs contain no caffeine.
在HTCPCP中，与咖啡壶相关联的资源是物理资源，而不是信息资源。大多数咖啡URI的“数据”不含咖啡因。
If a cup of coffee is data, metadata about the brewed resource is discovered using the PROPFIND method [WEBDAV].
如果一杯咖啡是数据，那么将使用PROPFIND方法[WEBDAV]查找有关酿造资源的元数据。
When coffee is poured, and milk is offered, it is necessary for the holder of the recipient of milk to say "when" at the time when sufficient milk has been introduced into the coffee. For this purpose, the "WHEN" method has been added to HTCPCP. Enough? Say WHEN.
当倒咖啡并提供牛奶时，牛奶接收者的持有者有必要在咖啡中加入足够牛奶时说“何时”。为此，HTCPCP中添加了“WHEN”方法。足够地说什么时候。
HTCPCP recommends several HTTP header fields and defines some new ones.
HTCPCP推荐了几个HTTP头字段，并定义了一些新字段。
2.2.1.1 The "safe" response header field.
2.2.1.1 “安全”响应标题字段。
[SAFE] defines a HTTP response header field, "Safe", which can be used to indicate that repeating a HTTP request is safe. The inclusion of a "Safe: Yes" header field allows a client to repeat a previous request if the result of the request might be repeated.
[SAFE]定义HTTP响应头字段“SAFE”，可用于指示重复HTTP请求是安全的。如果请求的结果可能会重复，则包含“Safe:Yes”头字段允许客户端重复以前的请求。
The actual safety of devices for brewing coffee varies widely, and may depend, in fact, on conditions in the client rather than just in the server. Thus, this protocol includes an extension to the "Safe" response header:
煮咖啡设备的实际安全性差异很大，实际上可能取决于客户端的条件，而不仅仅是服务器的条件。因此，该协议包括对“安全”响应头的扩展：
Safe = "Safe" ":" safe-nature
safe-nature = "yes" | "no" | conditionally-safe
conditionally-safe = "if-" safe-condition
safe-condition = "user-awake" | token
Safe = "Safe" ":" safe-nature
safe-nature = "yes" | "no" | conditionally-safe
conditionally-safe = "if-" safe-condition
safe-condition = "user-awake" | token
indication will allow user agents to handle retries of some safe requests, in particular safe POST requests, in a more user-friendly way.
该指示将允许用户代理以更用户友好的方式处理某些安全请求的重试，特别是安全POST请求。
In HTTP, the "Accept" request-header field is used to specify media types which are acceptable for the response. However, in HTCPCP, the response may result in additional actions on the part of the automated pot. For this reason, HTCPCP adds a new header field, "Accept-Additions":
在HTTP中，“接受”请求头字段用于指定响应可接受的媒体类型。但是，在HTCPCP中，响应可能会导致自动pot的其他操作。因此，HTCPCP添加了一个新的标题字段“Accept Additions”：
Accept-Additions = "Accept-Additions" ":" #( addition-range [ accept-params ] )
Accept Additions=“Accept Additions”“：”#（添加范围[接受参数]）
addition-type = ( "*"
| milk-type
| syrup-type
| sweetener-type
| spice-type
| alcohol-type
) *( ";" parameter )
milk-type = ( "Cream" | "Half-and-half" | "Whole-milk"
| "Part-Skim" | "Skim" | "Non-Dairy" )
syrup-type = ( "Vanilla" | "Almond" | "Raspberry"
| "Chocolate" )
alcohol-type = ( "Whisky" | "Rum" | "Kahlua" | "Aquavit" )
addition-type = ( "*"
| milk-type
| syrup-type
| sweetener-type
| spice-type
| alcohol-type
) *( ";" parameter )
milk-type = ( "Cream" | "Half-and-half" | "Whole-milk"
| "Part-Skim" | "Skim" | "Non-Dairy" )
syrup-type = ( "Vanilla" | "Almond" | "Raspberry"
| "Chocolate" )
alcohol-type = ( "Whisky" | "Rum" | "Kahlua" | "Aquavit" )
No options were given for decaffeinated coffee. What's the point?
没有为无咖啡因咖啡提供任何选择。重点是什么？
Normal HTTP return codes are used to indicate difficulties of the HTCPCP server. This section identifies special interpretations and new return codes.
正常HTTP返回码用于指示HTCPCP服务器的困难。本节确定了特殊解释和新的返回代码。
This return code is normally interpreted as "The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request. In HTCPCP, this response code MAY be returned if the operator of the coffee pot cannot comply with the Accept-Addition request. Unless the request was a HEAD request, the response SHOULD include an entity containing a list of available coffee additions.
此返回代码通常解释为“根据请求中发送的accept标头，请求标识的资源只能生成具有不可接受内容特征的响应实体。在HTCPCP中，如果咖啡壶操作员无法遵守“接受添加”请求，则可能会返回此响应代码。除非该请求是一项主要请求，否则响应应包括一个实体，其中包含一份可用咖啡添加物的列表。
In practice, most automated coffee pots cannot currently provide additions.
在实践中，大多数自动咖啡壶目前无法提供额外的功能。
Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout.
任何用茶壶煮咖啡的尝试都会导致错误代码“418我是茶壶”。生成的实体体可能短而结实。
Because coffee is international, there are international coffee URI schemes. All coffee URL schemes are written with URL encoding of the UTF-8 encoding of the characters that spell the word for "coffee" in any of 29 languages, following the conventions for internationalization in URIs [URLI18N].
因为咖啡是国际性的，所以有国际性的咖啡计划。所有coffee URL方案都使用UTF-8编码的URL编码来编写，UTF-8编码的字符在29种语言中的任何一种中拼写“coffee”一词，遵循URI国际化的惯例[URLI18N]。
coffee-url = coffee-scheme ":" [ "//" host ]
["/" pot-designator ] ["?" additions-list ]
coffee-url = coffee-scheme ":" [ "//" host ]
["/" pot-designator ] ["?" additions-list ]
coffee-scheme = ( "koffie" ; Afrikaans, Dutch
| "q%C3%A6hv%C3%A6" ; Azerbaijani
| "%D9%82%D9%87%D9%88%D8%A9" ; Arabic
| "akeita" ; Basque
| "koffee" ; Bengali
| "kahva" ; Bosnian
| "kafe" ; Bulgarian, Czech
| "caf%C3%E8" ; Catalan, French, Galician
| "%E5%92%96%E5%95%A1" ; Chinese
| "kava" ; Croatian
| "k%C3%A1va ; Czech
| "kaffe" ; Danish, Norwegian, Swedish
| "coffee" ; English
| "kafo" ; Esperanto
| "kohv" ; Estonian
| "kahvi" ; Finnish
| "%4Baffee" ; German
| "%CE%BA%CE%B1%CF%86%CE%AD" ; Greek
| "%E0%A4%95%E0%A5%8C%E0%A4%AB%E0%A5%80" ; Hindi
| "%E3%82%B3%E3%83%BC%E3%83%92%E3%83%BC" ; Japanese
| "%EC%BB%A4%ED%94%BC" ; Korean
| "%D0%BA%D0%BE%D1%84%D0%B5" ; Russian
| "%E0%B8%81%E0%B8%B2%E0%B9%81%E0%B8%9F" ; Thai
)
coffee-scheme = ( "koffie" ; Afrikaans, Dutch
| "q%C3%A6hv%C3%A6" ; Azerbaijani
| "%D9%82%D9%87%D9%88%D8%A9" ; Arabic
| "akeita" ; Basque
| "koffee" ; Bengali
| "kahva" ; Bosnian
| "kafe" ; Bulgarian, Czech
| "caf%C3%E8" ; Catalan, French, Galician
| "%E5%92%96%E5%95%A1" ; Chinese
| "kava" ; Croatian
| "k%C3%A1va ; Czech
| "kaffe" ; Danish, Norwegian, Swedish
| "coffee" ; English
| "kafo" ; Esperanto
| "kohv" ; Estonian
| "kahvi" ; Finnish
| "%4Baffee" ; German
| "%CE%BA%CE%B1%CF%86%CE%AD" ; Greek
| "%E0%A4%95%E0%A5%8C%E0%A4%AB%E0%A5%80" ; Hindi
| "%E3%82%B3%E3%83%BC%E3%83%92%E3%83%BC" ; Japanese
| "%EC%BB%A4%ED%94%BC" ; Korean
| "%D0%BA%D0%BE%D1%84%D0%B5" ; Russian
| "%E0%B8%81%E0%B8%B2%E0%B9%81%E0%B8%9F" ; Thai
)
pot-designator = "pot-" integer ; for machines with multiple pots
additions-list = #( addition )
pot-designator = "pot-" integer ; for machines with multiple pots
additions-list = #( addition )
All alternative coffee-scheme forms are equivalent. However, the use of coffee-scheme in various languages MAY be interpreted as an indication of the kind of coffee produced by the coffee pot. Note that while URL scheme names are case-independent, capitalization is important for German and thus the initial "K" must be encoded.
所有可选的咖啡方案形式都是等效的。然而，不同语言中咖啡方案的使用可能被解释为咖啡壶生产的咖啡种类的指示。请注意，虽然URL方案名称与大小写无关，但大写对于德语很重要，因此必须对首字母“K”进行编码。
The entity body of a POST or BREW request MUST be of Content-Type "message/coffeepot". Since most of the information for controlling the coffee pot is conveyed by the additional headers, the content of "message/coffeepot" contains only a coffee-message-body:
POST或BREW请求的实体体必须为内容类型“message/coffeepot”。由于用于控制咖啡壶的大多数信息都是通过附加的标题传递的，“消息/咖啡壶”的内容仅包含一个咖啡消息正文：
coffee-message-body = "start" | "stop"
coffee-message-body = "start" | "stop"
This section lays out some of the operational issues with deployment of HTCPCP ubiquitously.
本节列出了普遍部署HTCPCP的一些操作问题。
A robust quality of service is required between the coffee pot user and the coffee pot service. Coffee pots SHOULD use the Network Time Protocol [NTP] to synchronize their clocks to a globally accurate time standard.
在咖啡壶用户和咖啡壶服务之间需要一个可靠的服务质量。咖啡壶应使用网络时间协议[NTP]将其时钟同步到全球精确的时间标准。
Telerobotics has been an expensive technology. However, with the advent of the Cambridge Coffee Pot [CAM], the use of the web (rather than SNMP) for remote system monitoring and management has been proven. Additional coffee pot maintenance tasks might be accomplished by remote robotics.
远程机器人技术一直是一项昂贵的技术。然而，随着剑桥咖啡壶[CAM]的出现，使用web（而不是SNMP）进行远程系统监控和管理已经得到证明。额外的咖啡壶维护任务可能由远程机器人完成。
Web data is normally static. Therefore to save data transmission and time, Web browser programs store each Web page retrieved by a user on the user's computer. Thus, if the user wants to return to that page, it is now stored locally and does not need to be requested again from the server. An image used for robot control or for monitoring a changing scene is dynamic. A fresh version needs to be retrieved from the server each time it is accessed.
Web数据通常是静态的。因此，为了节省数据传输和时间，Web浏览器程序将用户检索到的每个网页存储在用户的计算机上。因此，如果用户想要返回到该页面，它现在存储在本地，不需要再次从服务器请求。用于机器人控制或监控变化场景的图像是动态的。每次访问服务器时都需要从服务器检索新版本。
In most organizations HTTP traffic crosses firewalls fairly easily. Modern coffee pots do not use fire. However, a "firewall" is useful for protection of any source from any manner of heat, and not just fire. Every home computer network SHOULD be protected by a firewall from sources of heat. However, remote control of coffee pots is
在大多数组织中，HTTP通信相当容易跨越防火墙。现代咖啡壶不用火。然而，“防火墙”对于保护任何热源不受任何形式的热量影响是有用的，而不仅仅是火灾。每个家庭计算机网络都应该受到防火墙的保护，防止热源进入。然而，远程控制咖啡壶是非常困难的
important from outside the home. Thus, it is important that HTCPCP cross firewalls easily.
重要的是从外面的家。因此，HTCPCP轻松跨越防火墙是很重要的。
By basing HTCPCP on HTTP and using port 80, it will get all of HTTP's firewall-crossing virtues. Of course, the home firewalls will require reconfiguration or new versions in order to accommodate HTCPCP-specific methods, headers and trailers, but such upgrades will be easily accommodated. Most home network system administrators drink coffee, and are willing to accommodate the needs of tunnelling HTCPCP.
通过基于HTTP的HTCPCP和使用端口80，它将获得HTTP的所有防火墙穿越优点。当然，家庭防火墙将需要重新配置或新版本，以适应特定于HTCPCP的方法、报头和预告片，但这样的升级将很容易适应。大多数家庭网络系统管理员喝咖啡，并愿意满足隧道HTCPCP的需要。
Coffee pot monitoring using HTTP protocols has been an early application of the web. In the earliest instance, coffee pot monitoring was an early (and appropriate) use of ATM networks [CAM].
使用HTTP协议监控咖啡壶已经成为web的早期应用。在最早的例子中，咖啡壶监控是ATM网络[CAM]的早期（适当）使用。
The traditional technique [CAM] was to attach a frame-grabber to a video camera, and feed the images to a web server. This was an appropriate application of ATM networks. In this coffee pot installation, the Trojan Room of Cambridge University laboratories was used to give a web interface to monitor a common coffee pot. of us involved in related research and, being poor, impoverished academics, we only had one coffee filter machine between us, which lived in the corridor just outside the Trojan Room. However, being highly dedicated and hard-working academics, we got through a lot of coffee, and when a fresh pot was brewed, it often didn't last long.
传统的技术[CAM]是将一个帧抓取器连接到摄像机上，然后将图像传送到web服务器。这是ATM网络的适当应用。在这个咖啡壶安装中，剑桥大学实验室的特洛伊木马机房被用来提供一个web界面来监控普通咖啡壶。我们中的大多数人都参与了相关的研究，身为贫穷的学者，我们之间只有一台咖啡过滤机，就住在特洛伊机房外的走廊里。然而，作为一个高度敬业和勤奋的学者，我们喝了很多咖啡，当一个新的壶煮出来时，它通常不会持续很久。
This service was created as the first application to use a new RPC mechanism designed in the Cambridge Computer Laboratory - MSRPC2. It runs over MSNL (Multi-Service Network Layer) - a network layer protocol designed for ATM networks.
该服务是第一个使用剑桥计算机实验室设计的新RPC机制（MSRPC2）的应用程序。它运行在MSNL（多业务网络层）——一种为ATM网络设计的网络层协议。
Coffee pots on the Internet may be managed using the Coffee Pot MIB [CPMIB].
互联网上的咖啡壶可以使用咖啡壶MIB[CPMIB]进行管理。
Anyone who gets in between me and my morning coffee should be insecure.
任何妨碍我喝早茶的人都应该没有安全感。
Unmoderated access to unprotected coffee pots from Internet users might lead to several kinds of "denial of coffee service" attacks. The improper use of filtration devices might admit trojan grounds. Filtration is not a good virus protection method.
互联网用户对无保护咖啡壶的无限制访问可能会导致几种“拒绝咖啡服务”攻击。过滤设备的不当使用可能会导致特洛伊木马的出现。过滤不是一种很好的病毒防护方法。
Putting coffee grounds into Internet plumbing may result in clogged plumbing, which would entail the services of an Internet Plumber [PLUMB], who would, in turn, require an Internet Plumber's Helper.
将咖啡渣放入互联网管道可能会导致管道堵塞，这将需要互联网管道工的服务，而互联网管道工又需要互联网管道工的助手。
Access authentication will be discussed in a separate memo.
访问认证将在单独的备忘录中讨论。
Many thanks to the many contributors to this standard, including Roy Fielding, Mark Day, Keith Moore, Carl Uno-Manros, Michael Slavitch, and Martin Duerst. The inspiration of the Prancing Pony, the CMU Coke Machine, the Cambridge Coffee Pot, the Internet Toaster, and other computer controlled remote devices have led to this valuable creation.
非常感谢本标准的许多贡献者，包括罗伊·菲尔丁、马克·戴、基思·摩尔、卡尔·乌诺·曼罗斯、迈克尔·斯拉维奇和马丁·杜尔斯特。腾跃的小马、CMU可乐机、剑桥咖啡壶、互联网烤面包机和其他计算机控制的远程设备的灵感促成了这一有价值的创造。
[RFC2068] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2068, January 1997.
[RFC2068]菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC 2068，1997年1月。
[RFC2186] Wessels, D., and K. Claffy, "Internet Cache Protocol (ICP), version 2," RFC 2186, September 1997
[RFC2186]Wessels，D.和K.Claffy，“互联网缓存协议（ICP），第2版”，RFC2186，1997年9月
[CPMIB] Slavitch, M., "Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2", RFC 2325, 1 April 1998.
[CPMIB]Slavitch，M.“使用SMIv2的滴水式加热饮料硬件设备的管理对象定义”，RFC 2325，1998年4月1日。
[HTSVMP] Q. Stafford-Fraser, "Hyper Text Sandwich Van Monitoring Protocol, Version 3.2". In preparation.
[HTSVMP]Q.Stafford Fraser，“超文本三明治货车监控协议，3.2版”。准备中。
[RFC2295] Holtman, K., and A. Mutz, "Transparent Content Negotiation in HTTP", RFC 2295, March 1998.
[RFC2295]Holtman，K.和A.Mutz，“HTTP中的透明内容协商”，RFC 2295，1998年3月。
[SAFE] K. Holtman. "The Safe Response Header Field", September 1997.
[安全]K.霍特曼。“安全响应标题字段”，1997年9月。
[CAM] "The Trojan Room Coffee Machine", D. Gordon and M. Johnson,
University of Cambridge Computer Lab,
<http://www.cl.cam.ac.uk/coffee/coffee.html>
[CAM] "The Trojan Room Coffee Machine", D. Gordon and M. Johnson,
University of Cambridge Computer Lab,
<http://www.cl.cam.ac.uk/coffee/coffee.html>
[CBIO] "The Trojan Room Coffee Pot, a (non-technical) biography", Q. Stafford-Fraser, University of Cambridge Computer Lab, <http://www.cl.cam.ac.uk/coffee/qsf/coffee.html>.
“木马室咖啡壶，一个（非技术）传记”，Q. Stafford Fraser，剑桥大学计算机实验室，<http://www.cl.cam.ac.uk/coffee/qsf/coffee.html>.
[RFC2235] Zakon, R., "Hobbes' Internet Timeline", FYI 32, RFC 2230,
November 1997. See also
<http://www.internode.com.au/images/toaster2.jpg>
[RFC2235] Zakon, R., "Hobbes' Internet Timeline", FYI 32, RFC 2230,
November 1997. See also
<http://www.internode.com.au/images/toaster2.jpg>
[NTP] Mills, D., "Network Time Protocol (Version 3) Specification, Implementation and Analysis", RFC 1305, March 1992.
[NTP]Mills，D.，“网络时间协议（第3版）规范、实施和分析”，RFC13051992年3月。
[URLI18N] Masinter, L., "Using UTF8 for non-ASCII Characters in Extended URIs" Work in Progress.
[URLI18N]Masinter，L.，“在扩展URI中对非ASCII字符使用UTF8”的工作正在进行中。
[PLUMB] B. Metcalfe, "Internet Plumber of the Year: Jim Gettys", Infoworld, February 2, 1998.
[PLUMB]B.Metcalfe，“年度互联网管道工：吉姆·盖蒂”，信息世界，1998年2月2日。
[COKE] D. Nichols, "Coke machine history", C. Everhart, "Interesting uses of networking", <http://www-cse.ucsd.edu/users/bsy/coke.history.txt>.
[COKE]D.Nichols，“可乐机历史”，C.Everhart，“网络的有趣用途”<http://www-cse.ucsd.edu/users/bsy/coke.history.txt>.
Larry Masinter Xerox Palo Alto Research Center 3333 Coyote Hill Road Palo Alto, CA 94304
美国加利福尼亚州帕洛阿尔托郊狼山路3333号帕洛阿尔托研究中心
EMail: masinter@parc.xerox.com
EMail: masinter@parc.xerox.com
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。