在網上查找RFC822的中文版,未找到(應該有吧),反正我也打算深入瞭解,所以就親手做翻譯,希望能對別人有點用
首頁
RFC # 822
Obsoletes: RFC #733 (NIC #41952)
STANDARD FOR THE FORMAT OF
ARPA INTERNET TEXT MESSAGES
August 13, 1982
Revised by
David H. Crocker
Dept. of Electrical Engineering
University of Delaware, Newark, DE 19711
Network: DCrocker @ UDel-Relay
RFC # 822
廢棄: RFC #733 (NIC(注1) #41952)
ARPA(注2) 英特網文本消息格式標準
八月 13, 1982
修訂:David H. Crocker
Dept. of Electrical Engineering
University of Delaware, Newark, DE 19711
Network: DCrocker @ UDel-Relay
注1:NIC Network Information Center 簡稱NIC, 國際組織, Internet IP地址由它統一負責全球地址的
注2:ARPA Advanced Research Projects Agency, (美國國防部)高級研究計劃署
在1950年代,通信研究者認識到需要允許在不同計算機用戶和通信網絡之間進行常規的通信。這促使了分散網絡、排隊論和包交換的研究。
1960年美國國防部國防前沿研究項目署（ARPA）建立的ARPA網引發了技術進步並使其成爲因特網發展的中心。
1973年ARPA網擴展成因特網，第一批接入的有英國和挪威計算機。
1974年ARPA的鮑勃·凱恩和斯坦福的溫登·澤夫提出TCP/IP協議。
1983年1月1日，ARPA網將其網絡核心協議由NCP改變爲TCP/IP協議)
目錄第1頁
Standard for ARPA Internet Text Messages
TABLE OF CONTENTS
PREFACE .................................................... ii
1. INTRODUCTION ........................................... 1
1.1. Scope ............................................ 1
1.2. Communication Framework .......................... 2
2. NOTATIONAL CONVENTIONS ................................. 3
3. LEXICAL ANALYSIS OF MESSAGES ........................... 5
3.1. General Description .............................. 5
3.2. Header Field Definitions ......................... 9
3.3. Lexical Tokens ................................... 10
3.4. Clarifications ................................... 11
4. MESSAGE SPECIFICATION .................................. 17
4.1. Syntax ........................................... 17
4.2. Forwarding ....................................... 19
4.3. Trace Fields ..................................... 20
4.4. Originator Fields ................................ 21
4.5. Receiver Fields .................................. 23
4.6. Reference Fields ................................. 23
4.7. Other Fields ..................................... 24
5. DATE AND TIME SPECIFICATION ............................ 26
5.1. Syntax ........................................... 26
5.2. Semantics ........................................ 26
6. ADDRESS SPECIFICATION .................................. 27
6.1. Syntax ........................................... 27
6.2. Semantics ........................................ 27
6.3. Reserved Address ................................. 33
7. BIBLIOGRAPHY ........................................... 34
APPENDIX
A. EXAMPLES ............................................... 36
B. SIMPLE FIELD PARSING ................................... 40
C. DIFFERENCES FROM RFC #733 .............................. 41
D. ALPHABETICAL LISTING OF SYNTAX RULES ................... 44
目錄
序 .................................................... ii
1. 介紹 ........................................... 1
1.1. 範圍 ............................................ 1
1.2. 通訊框架 .......................... 2
2. 符號約定 ................................. 3
3. 消息詞法分析 ........................... 5
3.1. 總體描述 .............................. 5
3.2. 消息頭定義 ......................... 9
3.3. 詞定義 ................................... 10
3.4. 一些需要明確的名義 ................................... 11
4. 消息定義 .................................. 17
4.1. 語法 ........................................... 17
4.2. 前轉 ....................................... 19
4.3. 用來追蹤郵件投遞過程的域 ..................................... 20
4.4. 發信人相關的域 ................................ 21
4.5. 收件人相關的域 .................................. 23
4.6. 參考域 ................................. 23
4.7. 其他域 ..................................... 24
5. 日期和時間定義 ............................ 26
5.1. 語法 ........................................... 26
5.2. 語義 ........................................ 26
6. 地址定義 .................................. 27
6.1. 語法 ........................................... 27
6.2. 語義 ........................................ 27
6.3. 保留地址 ................................. 33
7. 參考書目 ........................................... 34
附錄
A. 例子............................................... 36
B. 簡單的域解析 ................................... 40
C. 和RFC733的不同點 .............................. 41
D. 按字母順序排列的語法規則定義 ................... 44
目錄第二頁
Standard for ARPA Internet Text Messages
PREFACE
By 1977, the Arpanet employed several informal standards for
the text messages (mail) sent among its host computers. It was
felt necessary to codify these practices and provide for those
features that seemed imminent. The result of that effort was
Request for Comments (RFC) #733, "Standard for the Format of ARPA
Network Text Message", by Crocker, Vittal, Pogran, and Henderson.
The specification attempted to avoid major changes in existing
software, while permitting several new features.
This document revises the specifications in RFC #733, in
order to serve the needs of the larger and more complex ARPA
Internet. Some of RFC #733's features failed to gain adequate
acceptance. In order to simplify the standard and the software
that follows it, these features have been removed. A different
addressing scheme is used, to handle the case of inter-network
mail; and the concept of re-transmission has been introduced.
This specification is intended for use in the ARPA Internet.
However, an attempt has been made to free it of any dependence on
that environment, so that it can be applied to other network text
message systems.
The specification of RFC #733 took place over the course of
one year, using the ARPANET mail environment, itself, to provide
an on-going forum for discussing the capabilities to be included.
More than twenty individuals, from across the country, partici-
pated in the original discussion. The development of this
revised specification has, similarly, utilized network mail-based
group discussion. Both specification efforts greatly benefited
from the comments and ideas of the participants.
The syntax of the standard, in RFC #733, was originally
specified in the Backus-Naur Form (BNF) meta-language. Ken L.
Harrenstien, of SRI International, was responsible for re-coding
the BNF into an augmented BNF that makes the representation
smaller and easier to understand.
序
1977年, ARPA網絡(注:inetnet前身)使用了幾種非正式的郵件標準用
來在不同主機之間交互. 統一郵件格式因此變得十分迫切. 這導致了RFC733的誕生.
RFC733, "ARPA 英特網文本消息格式標準", 由Crocker, Vittal, Pogran,
和Henderson制定. 這份協議定義避免對已經存在軟件進行更改, 同時還定義了
幾個新的特性(注:簡單說是個向前兼容的湊合產品)
RFC733文檔是爲了在越來越大,越來越複雜的ARPA網絡上使用. 其中的
一些特性不能獲得大家的認可(應該是太複雜了),爲了簡化標準,讓後續的軟件
開發能更容易,這些複雜的特性被去掉了. 爲了處理網絡郵件,本文檔(RFC822)
使用了一種不同的地址格式,並且引入再次傳送的概念.
本定義是爲ARPA網絡定義的,但是,我們也試圖讓它能不依賴ARPA的環境.
這樣,它就能被其他的郵件系統使用
RFC733的定義過程超過了1年, 討論者本身也使用ARPA網絡,來不斷的發
起討論, 以討論RFC定義中應該包含的特性. 超過20個不同的人(注:太少
了,現在隨便要發個幾百個人頂的帖子太簡單了)從全國各地參與討論.隨着
規範定義討論的深入, 以電子郵件爲基礎的分組討論也發揚光大. 從參與者的
主意中規範定義獲得了很多好處(注:這一段翻譯的實在不好,也沒有什麼用,大家忽略之...)
RFC733的標準語法, 使用了BNF meta-language( 注 BNF:巴科斯範式,學過
離散的人清楚概念,不清楚也沒關係,下面有詳細說明 ). 斯坦福研究所的
Ken L. Harrenstien, 把巴科斯範式進行了一些擴展,使其語法更少,更容易
讓人理解