jkrey@venera.isi.edu (Joyce K. Reynolds) (12/20/90)
A new Request for Comments is now available from the Network Information
Center in the online library at NIC.DDN.MIL.
Note: This is a PostScript RFC, a secondary version is available in
ASCII. The secondary ASCII version may lack figures and the
information encoded in typographic variation (italics, boldface,
etc.). Since this information often provides esssential context, the
ASCII version is at best incomplete and at worst misleading. Anyone
expecting to understand this document is strongly encouraged to obtain
the PostScript version.
RFC 1195:
Title: Use of OSI IS-IS for Routing in TCP/IP and
Dual Environments
Author: R. Callon
Mailbox: callon@bigfut.enet.dec.com
PS-Pages: 68 ASCII-Pages: 85
PS-Characters: 381,799 ASCII-Characters: 192,628
pathname: RFC:RFC1195.PS
This memo specifies an integrated routing protocol, based on the OSI
Intra-Domain IS-IS Routing Protocol, which may be used as an interior
gateway protocol (IGP) to support TCP/IP as well as OSI. This allows a
single routing protocol to be used to support pure IP environments,
pure OSI environments, and dual environments. This specification was
developed by the IS-IS working group of the Internet Engineering Task
Force.
This RFC specifies a Proposed Standard Protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.
This RFC can be obtained via FTP from NIC.DDN.MIL, with the pathname
RFC:RFC1195.PS. Login 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.PS".
RFCs can also be obtained via FTP from NIS.NSF.NET. Using FTP, login
with username "anonymous" and password "guest"; then connect to the RFC
directory ("cd RFC"). The file name is of the form RFCnnnn.PS-1
(where "nnnn" refers to the number of the RFC).
The NIS also provides an automatic mail service for those sites which
cannot use FTP. Address the request to NIS-INFO@NIS.NSF.NET and leave
the subject field of the message blank. The first line of the text of
the message must be "SEND RFCnnnn.PS-1", where nnnn is replaced by
the RFC number.
To obtain the ASCII version, substitute "TXT" for "PS" in the
preceeding instructions.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
POSTEL@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.
Joyce K. Reynolds
USC/Information Sciences Institute