RFC961 - Official ARPA-Internet protocols(2)

时间:2005-02-11 来源: 作者: 点击:
Postel@USC-ISIB.ARPA Document Formats --------------------------------------------------- STATUS: None SPECIFICATION: RFC678 COMMENTS: Describes standard format rules for several types of documents.
  Postel@USC-ISIB.ARPA

Document Formats ---------------------------------------------------

STATUS: None

SPECIFICATION: RFC678

COMMENTS:

Describes standard format rules for several types of documents.

OTHER REFERENCES:

CONTACT: Postel@USC-ISIB.ARPA

Official ARPA-Internet Protocols RFC961

Bitmap Formats -----------------------------------------------------

STATUS: None

SPECIFICATION: RFC797

COMMENTS:

Describes a standard format for bitmap data.

OTHER REFERENCES:

CONTACT: Postel@USC-ISIB.ARPA

Facsimile Formats --------------------------------------------------

STATUS: None

SPECIFICATION: RFC804

COMMENTS:

Describes a standard format for facsimile data.

OTHER REFERENCES:

CONTACT: Postel@USC-ISIB.ARPA

Host-Front End Protocol ------------------------------------- (HFEP)

STATUS: Experimental

SPECIFICATION: RFC929

COMMENTS:

Please discuss any plans for implementation or use of this
protocol with the contact.

OTHER REFERENCES: RFC928

DEPENDENCIES:

CONTACT: Padlipsky@USC-ISI.ARPA

Official ARPA-Internet Protocols RFC961

Internet Protocol on X.25 Networks ------------------------ (IP-X25)

STATUS: Recommended

SPECIFICATION: RFC877

COMMENTS:

Describes a standard for the transmission of IP Datagrams over
Public Data Networks.

OTHER REFERENCES:

CONTACT: jtk@PURDUE.ARPA

Internet Protocol on DC Networks --------------------------- (IP-DC)

STATUS: Elective

SPECIFICATION: RFC891

COMMENTS:

OTHER REFERENCES:

RFC778 - DCNET Internet Clock Service

CONTACT: Mills@USC-ISID.ARPA

Internet Protocol on Ethernet Networks ---------------------- (IP-E)

STATUS: Recommended

SPECIFICATION: RFC894

COMMENTS:

OTHER REFERENCES: RFC893

CONTACT: Postel@USC-ISIB.ARPA

Official ARPA-Internet Protocols RFC961

Internet Protocol on Experimental Ethernet Networks -------- (IP-EE)

STATUS: Recommended

SPECIFICATION: RFC895

COMMENTS:

OTHER REFERENCES:

CONTACT: Postel@USC-ISIB.ARPA

Internet Protocol on IEEE 802.3 -------------------------- (IP-IEEE)

STATUS: Recommended

SPECIFICATION: RFC948

COMMENTS: A proposed protocol of two methods of encapsulating
Internet Protocol (IP) datagrams on an IEEE 802.3 network.

OTHER REFERENCES:

CONTACT: Ira@UPENN.CSNET

Internet Subnet Protocol ---------------------------------- (IP-SUB)

STATUS: Recommended

SPECIFICATION: RFC950

COMMENTS:

Specifies procedures for the use of subnets, including the
ultility of "subnets" of Internet networks, which are logically
visible sub-sections of a single Internet. Recommended in the
sense of "if you do subnetting at all do it this way".

OTHER REFERENCES: RFC940, RFC917, RFC925, RFC932, RFC936,
RFC922

DEPENDENCIES:

CONTACT: Mogul@SU-SCORE.ARPA

Official ARPA-Internet Protocols RFC961

Broadcasting Internet Datagrams ------------------------- (IP-BROAD)

STATUS: Experimental

SPECIFICATION: RFC919

COMMENTS:

A proposed protocol of simple rules for broadcasting Internet
datagrams on local networks that support broadcast, for
addressing broadcasts, and for how gateways should handle them.

Please discuss any plans for implementation or use of this
protocol with the contact.

OTHER REFERENCES: RFC922

DEPENDENCIES:

CONTACT: Mogul@SU-SCORE.ARPA

Address Resolution Protocol ---------------------------------- (ARP)

STATUS: Recommended

SPECIFICATION: RFC826

COMMENTS:

This is a procedure for finding the network hardware address
corresponding to an Internet Address.

OTHER REFERENCES:

CONTACT: Postel@USC-ISIB.ARPA

A Reverse Address Resolution Protocol ----------------------- (RARP)

STATUS: Elective

SPECIFICATION: RFC903

COMMENTS:

This is a procedure for workstations to dynamically find their
protocol address (e.g., their Internet Address), when they only
only know their hardware address (e.g., their attached physical
network address).

Official ARPA-Internet Protocols RFC961

OTHER REFERENCES:

CONTACT: Mogul@SU-SCORE.ARPA

Multi-LAN Address Resolution Protocol ----------------------- (MARP)

STATUS: Experimental

SPECIFICATION: RFC925

COMMENTS:

Discussion of the various problems and potential solutions of
"transparent subnets" in a multi-LAN environment.

Please discuss any plans for implementation or use of this
protocol with the contact.

OTHER REFERENCES: RFC917, RFC826

DEPENDENCIES:

CONTACT: Postel@USC-ISIB.ARPA

Broadcasting Internet Datagrams with Subnets --------- (IP-SUB-BROAD)

STATUS: Experimental

SPECIFICATION: RFC922

COMMENTS:

A proposed protocol of simple rules for broadcasting Internet
datagrams on local networks that support broadcast, for
addressing broadcasts, and for how gateways should handle them.

Please discuss any plans for implementation or use of this
protocol with the contact.

OTHER REFERENCES:

DEPENDENCIES:

CONTACT: Mogul@SU-SCORE.ARPA

Official ARPA-Internet Protocols RFC961

Host Access Protocol ----------------------------------------- (HAP)

STATUS: Recommended

SPECIFICATION: RFC907

COMMENTS:

This protocol specifies the network-access level communication
between an arbitrary computer, called a host, and a
packet-switched satellite network, e.g., SATNET or WBNET.

Note: Implementations of HAP should be performed in
coordination with satellite network development and operations
personnel.

OTHER REFERENCES:

DEPENDENCIES:

CONTACT: Schoen@BBN-UNIX.ARPA

Reliable Asynchronous Transfer Protocol --------------------- (RATP)

STATUS: Experimental

SPECIFICATION: RFC916

COMMENTS:

This paper specifies a protocol which allows two programs to
reliably communicate over a communication link. It ensures
that the data entering one end of the link if received arrives
at the other end intact and unaltered. This proposed protocol
is designed to operate over a full duplex point-to-point
connection. It contains some features which tailor it to the
RS-232 links now in current use.

Please discuss any plans for implementation or use of this
protocol with the contact.

OTHER REFERENCES:

DEPENDENCIES: Transmission Control Protocol

CONTACT: Finn@USC-ISIB.ARPA

Official ARPA-Internet Protocols RFC961

Thinwire Protocol --------------------------------------- (THINWIRE)

STATUS: Experimental

SPECIFICATION: RFC914

COMMENTS:

This paper discusses a Thinwire Protocol for connecting
personal computers to the ARPA-Internet. It primarily focuses
on the particular problems in the ARPA-Internet of low speed
network interconnection with personal computers, and possible
methods of solution.

Please discuss any plans for implementation or use of this
protocol with the contact.

OTHER REFERENCES:

DEPENDENCIES:

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