Network Working Group K. van den Hout
Request for Comments: 2322 HvU/HIP-networkteam
Category: Informational A. Koopal
UUnet NL/HIP-networkteam
R. van Mook
University of Twente/HIP-networkteam
1 April 1998
Network Working Group K. van den Hout
Request for Comments: 2322 HvU/HIP-networkteam
Category: Informational A. Koopal
UUnet NL/HIP-networkteam
R. van Mook
University of Twente/HIP-networkteam
1 April 1998
Management of IP numbers by peg-dhcp
通过peg-dhcp管理IP号码
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年）。版权所有。
Introduction
介绍
This RFC describes a protocol to dynamically hand out ip-numbers on field networks and small events that don't necessarily have a clear organisational body.
本RFC描述了一种协议，用于在现场网络和不一定有明确组织机构的小型活动上动态分发ip号码。
It can also provide some fixed additional fields global for all clients like netmask and even autoproxyconfigs. It does not depend on a particular ip-stack.
它还可以为所有客户端（如netmask甚至autoproxyconfigs）提供一些固定的附加全局字段。它不依赖于特定的ip堆栈。
History of the protocol.
议定书的历史。
The practice of using pegs for assigning IP-numbers was first used at the HIP event (http://www.hip97.nl/). HIP stands for Hacking In Progress, a large three-day event where more then a thousand hackers from all over the world gathered. This event needed to have a TCP/IP lan with an Internet connection. Visitors and participants of the HIP could bring along computers and hook them up to the HIP network.
在髋关节比赛中，首次采用了使用钉子分配IP号码的做法(http://www.hip97.nl/). HIP代表黑客行为进行中，这是一个为期三天的大型活动，来自世界各地的一千多名黑客在此聚会。此事件需要一个具有Internet连接的TCP/IP lan。HIP的访客和参与者可以携带电脑，并将其连接到HIP网络。
During preparations for the HIP event we ran into the problem of how to assign IP-numbers on such a large scale as was predicted for the event without running into troubles like assigning duplicate numbers or skipping numbers. Due to the variety of expected computers with associated IP stacks a software solution like a Unix DHCP server would probably not function for all cases and create unexpected technical problems.
在HIP活动的准备过程中，我们遇到了一个问题，即如何在如此大规模的情况下分配IP号码，而不会遇到分配重复号码或跳过号码等问题。由于具有相关IP堆栈的预期计算机种类繁多，像Unix DHCP服务器这样的软件解决方案可能无法在所有情况下运行，并会产生意外的技术问题。
So a way of centrally administrating IP-numbers and giving them out to people to use on their computers had to be devised. After some discussion, the idea came up of using wooden clothes-pegs. Using pegs has the following advantages in respect to other methods:
因此，必须设计一种集中管理IP号码并将其分发给人们在计算机上使用的方法。经过一番讨论，提出了使用木制衣夹的想法。与其他方法相比，使用销钉具有以下优点：
- cheap - a peg is a 'token' and represents one IP-number, therefore making the status of the IP-number (allocated or not allocated) visible. - a peg can be clipped to a network cable giving a very clear view of where a given IP-number is in use.
- 便宜-peg是一个“令牌”，代表一个IP号码，因此使IP号码的状态（已分配或未分配）可见。-可以将一个peg夹在网线上，以便非常清楚地看到给定IP号码的使用位置。
Credits for the original idea of using wooden pegs go to Daniel Ockeloen.
使用木钉的最初想法归功于丹尼尔·奥克伦。
The server.
服务器。
The server can have many appearances. At HIP it was a large tent situated at the central field where all the activities were. It can also be a small table in the corner of a terminalroom.
服务器可以有许多外观。在HIP，它是一个大帐篷，位于中心场地，所有活动都在这里进行。它也可以是终点站房间角落里的一张小桌子。
The server can hand out two parts to the client, the peg and a paper with additional fields fixed for the site the server is running for. We will describe both here.
服务器可以将两部分内容分发给客户端，即peg和一张带有为服务器运行的站点固定的附加字段的纸张。我们将在这里描述两者。
The peg.
钉子。
On the peg the IP-number is mentioned. The text on the peg can be described according to the following BNF:
在peg上提到了IP号码。peg上的文字可根据以下BNF进行描述：
Total ::== IP | Net
Total ::== IP | Net
IP ::== num.num.num.num | num.num | num
IP ::== num.num.num.num | num.num | num
Net ::== num.num.num/mask | num.num/mask | num/mask
Net ::== num.num.num/mask | num.num/mask | num/mask
num ::== {1..255}
num ::== {1..255}
mask ::== {8..31}
mask ::== {8..31}
The Net-method of writing larger nets is an optional part of the protocol, it doesn't have to be implemented. If it is implemented, it requires more administration at the server (see below).
编写较大网络的Net方法是协议的可选部分，不必实现。如果实现了它，则需要在服务器上进行更多的管理（请参见下文）。
The short versions of the IP-number with only 1 or 2 chunks are meant for large servers where writing the whole number on the peg is just boring and time-consuming. It requires the prefix to be mentioned on the additional field paper, but that can be produced in more
只有1或2个数据块的IP号码的简短版本适用于大型服务器，在这些服务器上，将整个号码写在peg上既枯燥又耗时。它要求在额外的现场论文中提及前缀，但这可以在更多的文档中生成
convenient ways. It is not recommended to work with more prefixes. It is better to write more numbers on the peg and use a smaller prefix.
方便的方式。不建议使用更多前缀。最好在桩上写更多的数字，并使用较小的前缀。
If the network to be numbered is rather large and some kind of subnetting has to be implemented it is possible to give the pegs from the different subnets different colors. This has proven to be a very convenient way at HIP.
如果要编号的网络相当大，并且必须实施某种子网，则可以为不同子网的桩赋予不同的颜色。事实证明，这是一种非常方便的HIP方式。
The additional vendorfield paper.
额外的vendorfield文件。
This part is meant for information that is fixed for the whole site. It can either be implemented as small printed notes handed out with the peg or as a large paper billboard hung at a convenient place where everybody can read it.
本部分用于提供整个站点固定的信息。它既可以实现为用钉子分发的小纸条，也可以实现为悬挂在方便的地方的大纸牌，每个人都可以阅读。
The information can be described with the following BNF:
该信息可用以下BNF描述：
Network ::== num.num.num.num
Network ::== num.num.num.num
Netmask ::== num.num.num.num | num
Netmask ::== num.num.num.num | num
Gateway ::== num.num.num.num | num.num | num
Gateway ::== num.num.num.num | num.num | num
Proxy ::== num.num.num.num:port | num.num:port | num:port
Proxy ::== num.num.num.num:port | num.num:port | num:port
Paper ::== Network Netmask Gateway Proxy | Network Netmask Gateway
Paper ::== Network Netmask Gateway Proxy | Network Netmask Gateway
num ::== {0..255}
num ::== {0..255}
port ::== {1..65535}
port ::== {1..65535}
The paper and the peg are of course one part, if two numbers are used on the peg, two numbers are used on the paper.
纸和钉子当然是一部分，如果钉子上有两个数字，纸上就有两个数字。
Because it is fixed information, it can be produced with means of mass-production (printing, copying).
因为它是固定信息，所以可以通过大规模生产（印刷、复印）的方式进行生产。
The IP-repository
IP存储库
Due to the nature of the peg, the repository can be quite simple. Just a clothes-line with all the pegs that are ready to be handed out attached to it. If you work with different subnets, it is convenient to group the pegs for the different subnets (colors).
由于peg的性质，存储库可以非常简单。只是一条晾衣绳，上面挂着准备分发的所有钉子。如果使用不同的子网，则可以方便地为不同的子网（颜色）分组桩号。
At large networks where it is not really known how many IP-numbers are needed, a first set of pegs can be made in advance, and the administration of produced pegs kept on paper so it is known for which numbers pegs have already been made. If use is made of the
在不知道需要多少IP号码的大型网络中，可以提前制作第一组PEG，并且制作的PEG的管理保存在纸上，以便知道已经制作了哪些号码PEG。如果使用
net-extension on the pegs, numbers given out that way can be administrated this way too.
在pegs上的net扩展，以这种方式给出的数字也可以通过这种方式进行管理。
Issuing IP-numbers.
发放IP号码。
The pegs and the IP-numbers are issued at the server to the client. Normally the client has to visit the server personally. Depending on how secure and controlled you want the process, the client has to ask for a peg to a responsible person, or he or she can just get a peg from store himself.
PEG和IP号在服务器上发布到客户端。通常，客户端必须亲自访问服务器。根据您对流程的安全性和控制程度，客户必须向负责人申请peg，或者他或她可以自己从门店获得peg。
If someone could apply for a networkrange, and he net-extension isn't used, coat-hangers can be prepared with sets of pegs attached to them.
如果有人可以申请一个networkrange，但他没有使用网络扩展，那么衣架上可以挂上几套钉子。
The vendorfields paper doesn't have to be issued with every peg, it is only needed when wanted.
vendorfields文件不必随附每一个peg，只在需要时才需要。
Reclaiming and reusing IP-numbers.
回收和重用IP号码。
It is not easy to implement a TTL in this protocol. One obvious TTL is the duration of the event after which the IP-numbers are not valid anymore.
在这个协议中实现TTL并不容易。一个明显的TTL是事件的持续时间，在此之后IP号码不再有效。
However, if a client decides that it doesn't need an IP-number anymore it can bring the peg back to the server.
但是，如果客户机决定不再需要IP号码，它可以将peg带回服务器。
The server should at that point decide what to do, if desired, it can bring the peg back into the pool (attach it to the clothes-line again).
服务器应该在此时决定要做什么，如果需要，它可以将钉子带回池中（再次将其连接到晾衣绳上）。
If the server is not manned (the client has to help themselves), the only thing possible is that the client just places the peg back into the pool.
如果服务器没有人（客户机必须自己动手），唯一可能的事情是客户机只是将peg放回池中。
The client side.
客户端。
The optimum location for the peg is clipped to the network cable near the NIC of the device needing an IP-number allocated. This ensures a clear visual connection between the device and the IP-number allocated and makes it an easy task to see which IP-number is allocated.
peg的最佳位置夹在需要分配IP号的设备NIC附近的网线上。这确保了设备和分配的IP号码之间的清晰可视连接，并使查看分配的IP号码变得容易。
Transfer of the IP information from the peg and the additional vendorfield paper note to the settings in the IP stack is done by human transfer. A person reads the information from the peg and from the additional information and enters this in the configuration of the used IP stack. This transfer is not completely free of
通过人工传输将peg和附加vendorfield纸条中的IP信息传输至IP堆栈中的设置。一个人从peg和附加信息中读取信息，并将其输入到所用IP堆栈的配置中。这种转移并非完全没有风险
corruption of the information or loss of the information contained on the peg.
peg上包含的信息损坏或丢失。
A certain amount of knowledge of the logic of IP settings is also assumed on the part of the person transferring the information.
传输信息的人员还假定对IP设置的逻辑有一定的了解。
Other information on the vendorfield paper note has to be transferred to the settings within specific application programs.
vendorfield纸条上的其他信息必须传输到特定应用程序中的设置中。
Use with other protocols
与其他协议一起使用
This protocol could be combined with avian carriers as described in RFC 1149 to hand out IP-numbers remote.
该协议可与RFC 1149中所述的鸟类携带者相结合，以远程分发IP号码。
At the first avian carrier, the peg is clipped to the leg of the carrier after rolling the additional vendorfield paper around it.
在第一个载体上，在将额外的vendorfield纸卷绕在其周围后，将销钉夹在载体的支腿上。
The remote site can take the peg on arrival of the avian carrier and use the information on it.
远程站点可以在鸟类携带者到达时获取peg并使用其上的信息。
This part of the protocol is still experimental and requires some additional research on topics like the weight of the peg and loss of the peg/whole carrier.
协议的这一部分仍然是实验性的，需要对peg的重量和peg/整个载体的损失等主题进行一些额外的研究。
Security Considerations
安全考虑
Some remarks about security can be made.
可以就安全问题发表一些评论。
Pegs are small devices and can be lost. At that time, the IP-number which was lost can't be used anymore because someone else can find the peg and use the information stored on it. But, once the peg is attached to a network cable, the chance to loose the peg is minimized.
钉子是小装置，可能会丢失。当时，丢失的IP号码无法再使用，因为其他人可以找到peg并使用其上存储的信息。但是，一旦将peg连接到网络电缆上，松开peg的机会就最小化了。
All the information on both the peg and on the additional 'fixed' fields on the paper record are plain text and readable for everyone. Private information should not be exchanged through this protocol.
所有关于peg和纸质记录上附加“固定”字段的信息都是纯文本，每个人都可以阅读。私人信息不应通过此协议进行交换。
On the client side all sorts of clients exist and cooperate freely. Due to the human factor of the clients transferring information from peg to IP stack, the information can be misinterpreted, which could cause network troubles. In the field test at HIP this became perfectly clear when someone mixed up the numbers and used the address from the default router as his IP-number, rendering the network useless for a period of time.
在客户方面，各种各样的客户自由地存在和合作。由于客户端将信息从peg传输到IP堆栈的人为因素，这些信息可能会被误解，从而导致网络故障。在HIP的现场测试中，当有人混淆了数字并使用默认路由器的地址作为他的IP号码时，这一点变得非常清楚，使得网络在一段时间内毫无用处。
Authors' Addresses
作者地址
Koos van den Hout Hogeschool van Utrecht / Expertisecentrum Cetis P.O. box 85029 3508 AA Utrecht The Netherlands
荷兰乌得勒支Koos van den Hout Hogeschool van Utrecht/Expertisecentrum Cetis邮政信箱85029 3508 AA
Phone: +31-30-2586287
Fax: +31-30-2586292
EMail: koos@cetis.hvu.nl
Phone: +31-30-2586287
Fax: +31-30-2586292
EMail: koos@cetis.hvu.nl
Andre Koopal UUnet Netherlands P.O. box 12954 1100 AZ AMSTERDAM The Netherlands
安德烈·库帕尔荷兰邮政信箱12954 1100荷兰阿姆斯特丹
Phone: +31-20-4952727
Fax: +31-20-4952737
EMail: andre@NL.net
Phone: +31-20-4952727
Fax: +31-20-4952737
EMail: andre@NL.net
Remco van Mook Van Mook Consulting Calslaan 10-31 7522 MA Enschede The Netherlands
Remco van Mook van Mook Consulting Calslaan 10-31 7522 MA Enschede荷兰
Phone: +31-53-4895267
EMail: remco@sateh.com
Phone: +31-53-4895267
EMail: remco@sateh.com
Full Copyright Statement
完整版权声明
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。