RFC1200 - IAB official protocol standards(2)

时间:2005-02-13 来源: 作者: 点击:
NETED Network Standard Text Editor Not Recommended 569 RJE Remote Job Entry Not Recommended 407 XNET Cross Net Debugger Not Recommended IEN-158 NAMESERVER Host Name Server Protocol Not Recommended IE
  
NETED Network Standard Text Editor Not Recommended 569
RJE Remote Job Entry Not Recommended 407
XNET Cross Net Debugger Not Recommended IEN-158
NAMESERVER Host Name Server Protocol Not Recommended IEN-116
MUX Multiplexing Protocol Not Recommended IEN-90
GRAPHICS Graphics Protocol Not Recommended NIC-24308

7. Contacts

7.1. IAB, IETF, and IRTF Contacts

7.1.1. Internet Activities Board (IAB) Contact

Contact:

Bob Braden
Executive Director of the IAB
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695

1-213-822-1511

Braden@ISI.EDU

Please send your comments about this list of protocols and especially
about the Draft Standard Protocols to the Internet Activities Board
care of Bob Braden, IAB Executive Director.

7.1.2. Internet Engineering Task Force (IETF) Contact

Contact:

Phill Gross
Chair of the IETF
Corporation for National Research Initiatives (NRI)
1895 Preston White Drive, Suite 100
Reston, VA 22091

1-703-620-8990

PGross@NRI.RESTON.VA.US

7.1.3. Internet Research Task Force (IRTF) Contact

Contact:

David D. Clark
Chair of the IRTF
Massachusetts Institute of Technology
Laboratory for Computer Science
545 Main Street
Cambridge, MA 02139

1-617-253-6003

ddc@LCS.MIT.EDU

7.2. Internet Assigned Numbers Authority Contact

Contact:

Joyce K. Reynolds
Internet Assigned Numbers Authority
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695

1-213-822-1511

IANA@ISI.EDU

The protocol standards are managed for the IAB by the Internet
Assigned Numbers Authority.

Please refer to the documents "Assigned Numbers" (RFC-1060) and
"Official Internet Protocols" (RFC-1011) for further information

about the status of protocol documents. There are two documents that
summarize the requirements for host and gateways in the Internet,
"Host Requirements" (RFC-1122 and RFC-1123) and "Gateway
Requirements" (RFC-1009).

How to obtain the most recent edition of this "IAB Official
Protocol Standards" memo:

The file "in-notes/iab-standards.txt" may be copied via FTP
from the VENERA.ISI.EDU computer using the FTP username
"anonymous" and FTP password "guest".

7.3. Request for Comments Editor Contact

Contact:

Jon Postel
RFCEditor
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292-6695

1-213-822-1511

Postel@ISI.EDU

Documents may be submitted via electronic mail to the RFCEditor for
consideration for publication as RFC. If you are not familiar with
the format or style requirements please request the "Instructions for
RFCAuthors". In general, the style of any recent RFCmay be used as
a guide.

7.4. The Network Information Center and
Requests for Comments Distribution Contact

Contact:

DDN Network Information Center
SRI International
Room EJ291
333 Ravenswood Avenue
Menlo Park, CA 94025

1-800-235-3155
1-415-859-3695

NIC@NIC.DDN.MIL

The Network Information Center (NIC) provides many information
services for the Internet community. Among them is maintaining the
Requests for Comments (RFC) library.

RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname
RFC:RFCnnnn.TXT where "nnnn" refers to the number of the RFC. A list
of all RFCs may be obtained by copying the file RFC:RFC-INDEX.TXT.
Log in with FTP username ANONYMOUS and password GUEST.

The NIC also provides an automatic mail service for those sites which
cannot use FTP. Address the request to SERVICE@NIC.DDN.MIL and in
the subject field of the message indicate the file name, as in
"Subject: SEND RFC:RFCnnnn.TXT".

Some RFCs are now available in PostScript, these may be obtained from
the NIC in a similar fashion by substituting ".PS" for ".TXT".

How to obtain the most recent edition of this "IAB Official
Protocol Standards" memo:

The file RFC:IAB-STANDARDS.TXT may be copied via FTP from the
NIC.DDN.MIL computer following the same procedures used to
obtain RFCs.

7.5. Other Sources for Requests for Comments

7.5.1. NSF Network Service Center (NNSC)

NSF Network Service Center (NNSC)
BBN Laboratories, Inc.
10 Moulton St.
Cambridge, MA 02238

617-873-3400

NNSC@NNSC.NSF.NET

7.5.2. NSF Network Information Service (NIS)

NSF Network Information Service
Merit Computer Network
University of Michigan
1075 Beal Avenue
Ann Arbor, MI 48109

313-763-4897

INFO@NIS.NSF.NET

7.5.3. CSNET Coordination and Information Center (CIC)

CSNET Coordination and Information Center
BBN Systems and Technologies Corporation
10 Moulton Street
Cambridge, MA 02238

617-873-2777

INFO@SH.CS.NET

8. Security Considerations

Security issues are not addressed in this memo.

9. Author's Address

Jon Postel
USC/Information Sciences Institute
4676 Admiralty Way
Marina del Rey, CA 90292

Phone: 213-822-1511
Fax: 213-823-6714

Email: Postel@ISI.EDU

------分隔线----------------------------
顶一下
(0)
0%
踩一下
(0)
0%
------分隔线----------------------------
最新评论 查看所有评论
发表评论 查看所有评论
请自觉遵守互联网相关的政策法规,严禁发布色情、暴力、反动的言论。
评价:
表情:
用户名: 密码: 验证码:
推荐内容