注册 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

汪涛

 
 
 

日志

 
 
关于我

南京邮电大学学士,北京邮电大学硕士。出版《生态社会人口论》(人民出版社),《通播网宣言》(北京邮电大学出版社) unsnet@163.com

网易考拉推荐
 
 

汪涛:荒诞的科幻作品RFC1606与IPv9  

2008-02-02 22:04:59|  分类: IPv6、IPv9和超级 |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |

 目录

1、为什么可以确定RFC1606是一荒诞科幻作品

2、关于恶搞性质的RFC文档

附件A:RFC1606中文翻译的文档

附件B:RFC1606的英文文档

1、为什么可以确定RFC1606是一荒诞科幻作品

大多数恶搞性质的RFC文档是普通人一眼就可以看出的,但RFC1606却不完全是这样。虽然如此,基本还是可以明显确定这是一个恶搞性质的文档。从附件A和附件B的RFC1606文档里可以明显看出:这个文档是一个表面看似一本正经,而事实上其内容完全是属于和电影《黑客帝国》差不多的荒诞科幻小说式的东西。整篇文档里几乎就没有一个根据现实的科学理论和网络技术能够想像得出来的东西。如:(红色字体为本文对RFC1606相关内容的评语)

“别的太阳系的智能生命的发现”——典型的科幻小说内容;

“超光速传送栈的同时发现”,“ with the parallel discovery of a faster-than-light transport stack”——违反光速不变原理

“紧凑磁盘全息图(Compact Disk Hologram)单元的使用是这种应用的代表”;“ 39层被用为器件的原子结构的试验用途”……——IP地址是分配给网络接口的,不是什么东西都可以分配IP地址的

“再加上早期的广播风暴导致病人血液沸腾的问题”——什么时候听说过网络广播风暴会导致“病人血液沸腾问题”的?到现在都还没实现互联网可以联到人身体里面去,更别说“病人血液”里去了。而这竟然还是“早期的

“穿着愚蠢的碟形卫星天线帽的需要会使人觉得不好意思,当然除了在加尼福利亚,那儿这是最新的时髦。”——这都哪儿跟哪儿啊

“(谣传IPv9要使用)”(which is also rumoured to be IPv9 aware)——“谣传”是严肃技术文档使用的语言吗?

“把血流既当作一个传送带也当作一个信息高速公路存在一些问题”——能想像得出这是什么东西吗?可以比较一下把人和机器缩小成细菌大小,然后用注射器注射到另一个人的身体里的科幻电影;

“反对党成员所谓的信息查询,可以发现办公室内人们的“异常”行为,是所谓隐秘的运动鞋网络,鞋匠先驱的这个行动失败了。市场还没有准备接受发送详细分析脚臭到制造商那里的鞋子。”。“到目前为止,从遥远的星系的黑客设置窃听设备的情况还没有被确定,这是由于从办公室到家的路上的远端控制的查找问题引起的。”——可以比较一下电影《哈里.波特》、特别是《黑客帝国》里的情节;

“登有关于外太空割草机的文章”——令人想起电影《星球大战》;

“最新的研究是夸克-夸克转换器,可以让原子当开关使用。制造这些东西非常昂贵(可能10倍于IPv9协议栈)”——外行人根本看不懂这说得是什么东西,可惜内行人更看不懂这说得是什么。

“使用IPv9的历史观察”、“ 最近几年TCP/IPv9显著兴起”、“ 再一次因为地址耗尽,IPv9协议走向了有用生命的尽头”、“不研究历史的人,注定要重复它。”——文档结尾包括文档名称是说“使用IPv9的历史”。并且一定要搞明白这篇文章谈得不是如何“设计和建立”IPv9,而是当“历史”发展到IPv9地址已经再次耗尽,IPv9已经将要被淘汰时(天呐,这倒底是什么日子?IPv4都还在使用啊),缅怀其光荣的“使用历史”,和总结IPv9的“成功之处”。RFC1606的作者J.Onions是在一开始就想像自己处在未来某个IPv9已经将要被淘汰的时间点上,对IPv9进行历史总结回顾。比较一下有个科幻作品叫《回到未来》。这都是典型的时空完全颠倒到人的直觉根本无法想像程度的,不仅是科幻,而且是科幻艺术作品里面最离谱的荒诞类科幻作品的写作方式。

这是RFC1606纯粹是一篇荒诞科幻作品最清楚明白的证据。

……

无论是支持还是反对IPv9的中国同胞们,相信大家都没认真看明白RFC1606说得到底是什么内容。令人最遗憾之处就在这里。

2、关于恶搞性质的RFC文档

互联网不仅很多网站有大量恶搞的内容,而且从其源头上的IETF标准组织就有恶搞的传统。一般技术标准组织都是相严肃的,其文档即使不成功也都是严肃态度在做事。但互联网标准组织IETF不是这样。西方4月1日为愚人节。每年愚人节这一天,都有可能增加不严肃的RFC文档。这种情况特别在1989年以后几乎成了固定的传统。这些不严肃的RFC文档有些可能是一些根本不可能实现的技术设想,而且文档本身就指明这是“非推荐的”,有些甚至是一首诗(如RFC527),有些是明显相当搞笑的文章(如RFC2324,“超文本咖啡壶控制协议”,这名字一看就该知道属于恶搞性质的)。但IETF却都象模象样地把它们与正常严肃的RFC文档一起保存下来了。在RFC的INDEX索引中,每年4月1日这一天发表的RFC文档都特定标有具体日期,而一般的文档只标明月份不标明日期。可以参见: http://www.ietf.org/iesg/1rfc_index.txt

注意一下这个RFC索引文件里面每个RFC文档April月份里的时间标识。

当然,并不是说只要是4月1日发表的RFC文档就一定是不严肃的,但这一天发表的文档却的确相当大的比例都是不严肃的。并且并不仅仅是4月1日,其他日期也有可能会上载一些恶搞性质的RFC文档。而一般中国老百姓,政府官员,甚至相当多的网络专业技术人员都根本没有注意到这一点.

以下是各个年份里4月1日发表的不严肃的RFC文档相对比较完整的汇总:

l  RFC 748TELNET RANDOMLY-LOSE option. M.R. Crispin. 1 April 1978. A parody of the TCP/IP documentation style. Due to some people taking it seriously, for a long time it was specially marked in the RFC index with "note date of issue".

RFC 1097TELNET SUBLIMINAL-MESSAGE option. B. Miller. 1 April 1989.

以下是非4月1日发表的恶搞性质的RFC文档汇总:

l         RFC 439 — PARRY encounters the DOCTOR. V. Cerf. 21 January 1972.

l         RFC 527 — ARPAWOCKY. R. Merryman, UCSD. 22 June 1973.

l         RFC 968 — Twas the night before start-up. V.G. Cerf, 1 December 1985.

l         RFC 1882 — The 12-Days of Technology Before Christmas. B. Hancock. December 1995.

因此,并非RFC1606一个文章是恶搞的,在RFC文档里恶搞的作品多了去了。

 

附件A:RFC1606中文翻译的文档

RFC中文文档资源可参阅:http://www.chinaitpower.com/Net/xieyi/rfccn/index.html

——————————————————————————————————

Network Working Group                                    J. Onions

Request for Comments: 1606                                Nexor Ltd.

Category: Informational                                  1 April 1994

 使用IPv9的历史考察

 本备忘录的状态

本备忘录是因特网社区的网络号和自治系统号码的状态报告。本备忘录无分发限制。

 

摘要

本论文回顾了旧的IP版本协议的使用。探讨它的一些成功和失败。

目录

1. 介绍  1

2. 路由  2

3. 分配  2

4. 应用  2

5.制造  3

6.结论  3

7.安全考虑      3

8.作者地址      3

版权说明 3

致谢     4

 

1.介绍

最近几年TCP/IPv9显著兴起。只有几百万台主机的时代已经过去,网络为人们所了解。随着再一次因为地址耗尽,IPv9协议走向了有用生命的尽头,这里我们回顾一下本协议的一些成功之处。

2.路由

IPv9的深达42层的路由层次是它得到广泛应用的关键特性。分配整个网络,或者一组网络给一个电子器件的能力是它兴起的原因之一。紧凑磁盘全息图(Compact Disk Hologram)单元的使用是这种应用的代表。典型的,他们有一个37层的网络号分配给每一个逻辑部分,一个36层的网络号分配给整个设备。这使得CDH的管理协议可以把单元作为设备的一个元素控制。同样,允许次芯片级的路由能够使用38层的地址来下载新的微代码。但是,40-42层还没有发现需求,虽然当需要的时候,39层被用为器件的原子结构的试验用途。

3.分配

IPv9协议的大量的号码空间也使得分配地址可以用一种直接的方式。典型的,大部分高级街道商业互联网提供者提供给每个房屋10亿个地址。这些地址动态的分区成子网结构,允许百万个地址的组可以分配给每个单元(比如:房间/地面 等等)。子组的分配可以到控制器,比如电灯开关,电线插座,同样的可以到每一个插孔。分配过程可以再通过结构化分区的方式进行,每一个主要的应用从他的控制器请求一块地址。通过这种方式,电灯泡从电灯开关请求一个地址,电灯开关从电气系统,电气系统从房间/地面控制器依次请求地址。由于地址空间很大地址冲突不会有特别的问题发生,这种方式是很成功的,

同时还有很多没有分配空间的地址正在快速增长。别的太阳系的智能生命的发现以及超光速传送栈的同时发现是主要的原因。这样就可以和他们实时通信,世界范围的地址空间的分配就有必要了,可以分配在第三层路由结构。有一个全局的(空间)第二层星系范围的网络可以分配给这个星系,可是在外太空建立的永久空间站开始消耗这个资源。最紧迫的问题是平行宇宙的情况。当然,假设没有比平行宇宙更高级的外推是不完备的。。。

到目前为止,从遥远的星系的黑客设置窃听设备的情况还没有被确定,这是由于从办公室到家的路上的远端控制的查找问题引起的。

4.应用

身体监视器的引入,作为IPv9可以取址的单元注入到血液流中,还没有作出结论。同时,在心脏,肾脏,大脑,等等中可以植入设备,在紧急情况下发送SNMPv9捕捉消息,这已经是医生的一个有用的监视工具,把血流既当作一个传送带也当作一个信息高速公路存在一些问题。在血流中移动的信号的干扰和神经的信号的近似,意味着病人同时承受着多个事件,可能导致猛烈的痉挛。这样,再加上早期的广播风暴导致病人血液沸腾的问题,导致人们对这个问题重新思考。同样,穿着愚蠢的碟形卫星天线帽的需要会使人觉得不好意思,当然除了在加尼福利亚,那儿这是最新的时髦。

IPv9取址商品包装的使用是讨论的热点。行销人视他为神赐之物,它能够反馈商品到底是如何使用的。同样,直接广播极大地改善了回收。“请所有纸板组成的包装响应。”顾客对她是否是私生活的入侵并不在乎。猜物直接跳转器的引入(谣传IPv9要使用)发送直接的广播包到本地的食物包装网络,有效的重置网络掩码为全1,意思是你选择了这个食物。

IPv9杂志的出现受到普遍欢迎。能够询问一般杂志目录在那里是最有用的特性。如果和联网报纸/杂志架结合起来,就有发现你把登有关于外太空割草机的文章的杂志放在那里的能力。最终会有自动下载阅读习惯到家庭控制器,然后告诉读者那里有同样主题的文章的能力。反对党成员所谓的信息查询,可以发现办公室内人们的“异常”行为,是所谓隐秘的运动鞋网络,鞋匠先驱的这个行动失败了。市场还没有准备接受发送详细分析脚臭到制造商那里的鞋子。

5.制造

当然,制造代价是设计IPv9时没有考虑的一个问题。它需要跳跃性的想象去相信有一天任何想要取址的东西都是IPv9可以取址的。他假设IPv9协议机随着芯片技术的进步价格会下降。很少有人预见到使用基因技术让病毒按指令建造纳米技术IPv9协议机的代价。同样,纳米机器人是否有地方放这些东西。

最新的研究是夸克-夸克转换器,可以让原子当开关使用。制造这些东西非常昂贵(可能10倍于IPv9协议栈),除非有非常特别的需要。 

6.结论

不研究历史的人,注定要重复它。 

7.安全考虑

本备忘录不讨论安全问题。

 8.作者地址

  Julian Onions

  Nexor Ltd.

  PO Box 132

  Nottingham NG7 2UU, ENGLAND

  Phone: +44 602 520580

  EMail: j.onions@nexor.co.uk

——————————————————————————————————

 

 

附件B:RFC1606的英文文档:

RFC文档官方下载地址:http://www.ietf.org/rfc.html

RFC1606官方资源地址:http://www.ietf.org/rfc/rfc1606.txt?number=1606

——————————————————————————————————

 Network Working Group                                       J. Onions

Request for Comments: 1606                                   Nexor Ltd.

Category: Informational                                 1 April 1994

 

         A Historical Perspective On The Usage Of IP Version 9

 

Status of this Memo

 

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

 

Abstract

    This paper reviews the usages of the old IP version protocol. It considers some of its successes and its failures.

 

Introduction

 The take-up of the network protocol TCP/IPv9 has been phenomenal over the last few years. Gone are the days when there were just a few million hosts, and the network was understood. As the IP version 9 protocol comes to the end of its useful life, once again due to address space exhaustion, we look back at some of the success of the protocol.

 

Routing

  The up to 42 deep hierarchy of routing levels built into IPv9 must have been one of the key features for its wide deployment. The ability to assign a whole network, or group of networks to an electronic component must be seen as one of the reasons for its takeup. The use of the Compact Disk Hologram units is typical of the usage. They typically have a level 37 network number assigned to each logical part, and a level 36 network number assigned to the whole device. This allows the CDH management protocol to control the unit as a whole, and the high-street vendor to do remote diagnostics on discreet elements of the device. This still allows sub-chip routing to be done using the 38th level addressing to download new nanocode.

   As yet, no requirement has been found for levels 40-42, with level 39 still being used for experimental interrogation of atomic structure of components where required.

 Onions                                                      [Page 1]

 

RFC 1606         Historical Perspective Usage of IP V9      1 April 1994

 Allocation

 The vast number space of the IPv9 protocol has also allowed allocation to be done in a straight forward manner. Typically, most high street commercial internet providers issue a range of 1 billion addresses to each house. The addresses are then dynamically partitioned into subnet hierarchies allowing groups of a million addresses to be allocated for each discreet unit (e.g., room/floor etc.) The allocation of sub groups then to controllers such as light switches, mains sockets and similar is then done from each pool.

 The allocation process is again done in a hierarchical zoned way,with each major application requesting a block of addresses from its controller. In this way the light bulb requests an address block from the light switch, the light switch in turn from the electrical system which in turn requests one from the room/floor controller. This has been found to be successful due to the enormous range of addresses available, and contention for the address space being without   problems typically.

 Whilst there are still many addresses unallocated the available space has been sharply decreased. The discovery of intelligent life on other solar systems with the parallel discovery of a faster-than-light transport stack is the main cause. This enables real time communication with them, and has made the allocation of world-size address spaces necessary, at the level 3 routing hierarchy. There is  still only 1 global (spatial) level 2 galaxy wide network required for this galaxy, although the establishment of permanent space stations in deep space may start to exhaust this. This allows level 1 to be used for inter-galaxy routing. The most pressing problem now is the case of parallel universes.  Of course there is the danger of assuming that there is no higher extrapolation than parallel universes

 Up to now, the hacking into, and setting of holo-recorder devices to the wrong channel from remote galaxies, has not been confirmed, and appears to be attributable to finger problem with the remote control whilst travelling home from the office.

 

Applications

 The introduction of body monitors as IPv9 addresseable units injected into the blood stream has been rated as inconclusive. Whilst being able to have devices lodged in the heart, kidneys, brain, etc., sending out SNMPv9 trap messages at critical events has been a useful monitoring tool for doctors, the use of the blood stream as both a delivery and a communication highway, has been problematic. The crosstalk between the signals moving through the blood stream and the

 

Onions                                                   [Page 2]

 

RFC 1606         Historical Perspective Usage of IP V9      1 April 1994

 close proximity of nerves has meant that patients suffering multiple events at once, can go into violent spasm. This, coupled with early problems with broadcasts storms tending to make patients blood boil, have led to a rethink on this whole procedure. Also, the requirement to wear the silly satellite dish hat has led to feelings of embarrassment except in California, where it is now the latest trend.

 The usage of IPv9 addresseable consumer packaging has been a topic of hot debate. The marketing people see it as a godsend, being able to get feedback on how products are actually used. Similarly, the recycling is much improved by use of directed broadcast, "All those  packages composed of cardboard respond please." Consumers are not so keen on this seeing it as an invasion of privacy. The introduction of the handy-dandy directed stack zapper (which is also rumoured to be IPv9 aware) sending directed broadcasts on the local food package net effectively resetting the network mask to all 1's has made this an area of choice.

 The advent of the IPv9 magazine was universally approved of. Being able to ask a magazine where its contents page was the most useful of the features. However combined with the networked newspaper/magazine rack, the ability to find out where you left the magazine with the article that was concerned with something about useage of lawn mowers  in outer space is obvious. The ability to download reading habits automatically into the house controller and therefore alert the reader of articles of similar ilk is seen as marginal. Alleged querying of this information to discover "deviant" behaviour in persons within political office by members of contending parties is suspected

 Sneakernet, as pioneered by shoe specialists skholl is seen to be a failure. The market was just not ready for shoes that could forward detailed analysis of foot odour to manufacturers...

 

Manufacture

 Of course, cost is one of the issues that was not considered when IPv9 was designed. It took a leap of imagination to believe that one day anything that wished to be could be IPv9 addresseable. It was assumed that IPv9 protocol machines would drop in price as with general chip technology. Few people would have forseen the advance in genetic manipulation that allowed viruses to be instructed to build nano-technology IPv9 protocol machines by the billion for the price or a grain of sugar. Or similarly, the nano-robots that could insert and wire these in place.

 

Onions                                            [Page 3]

 

RFC 1606         Historical Perspective Usage of IP V9      1 April 1994

 

The recent research in quark-quark transistors, shows some promise and may allow specially built atoms to be used as switches. The manufacture of these will be so expensive (maybe up to 10cent an IPv9 stack) as to be prohibitive except for the most highly demanding niches.

 

Conclusions

 Those who do not study history, are doomed to repeat it.

 

Security Considerations

 

   Security issues are not discussed in this memo.

 

Author's Address

 

   Julian Onions

   Nexor Ltd.

   PO Box 132

   Nottingham NG7 2UU, ENGLAND

    Phone: +44 602 520580

   EMail: j.onions@nexor.co.uk

——————————————————————————————————

  评论这张
 
阅读(3618)| 评论(3)
推荐 转载

历史上的今天

在LOFTER的更多文章

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2017