Справочник по сетевым протоколам

RFC1700 - часть 140 2422-190-28100-00 Intersped AS [OXG] Unassigned [JBP] Reserved [JBP]

The standard for transmission of IP datagrams over the Public Data

Network is specified in RFC-1356 [69].


[RFC877] Korb, J., "A Standard for the Transmission of IP Datagrams

Over Public Data Networks", RFC 877, Purdue University,

September 1983.


[ABB2] A. Blasco Bonito

[AD67] Andy Davis

[AXH] Arthur Harvey

[AXM] Alex Martin <---none--->

[BXD] Brian Dockter <---none--->


[GB7] Gerd Beling

[JBP] Jon Postel

[JD21] Jonathan Dreyer

[JFW] Jon F. Wilkes

[JK64] mystery contact!

[JXE2] Jeanne Evans

[LZ15] Lee Ziegenhals

[MS56] Marvin Solomon

Reynolds & Postel [Page 184]

RFC 1700 Assigned Numbers October 1994

[MO2] Michael O'Brien

[OXG] Oyvind Gjerstad

[PAM6] Paul McNabb

[PK] Peter Kirstein

[PXD] Peter Delchiappo <---none--->

[PXF1] Per Futtrup <---none--->

[RAM57] Rex Mann <---none--->

[SXA3] Sten Andler <---none--->

[TN] Thomas Narten

[TC27] Thomas Calderwood

[TXR] Tim Rylance


[VXT] V. Taylor


URL = ftp://ftp.isi.edu/in-notes/iana/assignments/public-data-network-


Reynolds & Postel [Page 185]

RFC 1700 Assigned Numbers October 1994


The word "link" here refers to a field in the original MILNET Host/IMP

interface leader. The link was originally defined as an 8-bit field.

Later specifications defined this field as the "message-id" with a

length of 12 bits. The name link now refers to the high order 8 bits of

this 12-bit message-id field. The Host/IMP interface is defined in BBN

Report 1822 [BBN1822].

The low-order 4 bits of the message-id field are called the sub-link.

Unless explicitly specified otherwise for a particular protocol, there

is no sender to receiver significance to the sub-link. The sender may

use the sub-link in any way he chooses (it is returned in the RFNM by

Содержание  Назад  Вперед