RFC 1132

Research, RFC, Technology
Network Working Group L. McLaughlin III Request for Comments: 1132 The Wollongong Group November 1989 A Standard for the Transmission of 802.2 Packets over IPX Networks Status of this Memo This document specifies a standard method of encapsulating 802.2 [1] packets on networks supporting Novell's Internet Packet Exchange Protocol [2] (IPX). It obsoletes earlier documents detailing the transmission of Internet packets over IPX networks. It differs from these earlier documents in that it allows for the transmission of multiple network protocols over IPX and for the transmission of packets through IPX bridges. Distribution of this memo is unlimited. Introduction The goal of this specification is to allow compatible and interoperable implementations for transmitting Internet packets such as the Internet Protocol [3] (IP) and Address Resolution Protocol [4] (ARP) as well…
Read More

RFC 1002

Research, RFC, Technology
Network Working Group Request for Comments: 1002 March, 1987 PROTOCOL STANDARD FOR A NetBIOS SERVICE ON A TCP/UDP TRANSPORT: DETAILED SPECIFICATIONS ABSTRACT This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC gives the detailed specifications of the NetBIOS-over-TCP packets, protocols, and defined constants and variables. A more general overview is found in a companion RFC, "Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods". NetBIOS Working Group [Page 1] RFC 1002 March 1987 TABLE OF CONTENTS 1. STATUS OF THIS MEMO 4 2. ACKNOWLEDGEMENTS 4 3.…
Read More

RFC 1001

Research, RFC, Technology
Network Working Group Request for Comments: 1001 March, 1987 PROTOCOL STANDARD FOR A NetBIOS SERVICE ON A TCP/UDP TRANSPORT: CONCEPTS AND METHODS ABSTRACT This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment. Both local network and internet operation are supported. Various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast. This RFC describes the NetBIOS-over-TCP protocols in a general manner, emphasizing the underlying ideas and techniques. Detailed specifications are found in a companion RFC, "Protocol Standard For a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications". NetBIOS Working Group [Page 1] RFC 1001 March 1987 SUMMARY OF CONTENTS 1. STATUS OF THIS MEMO 6 2. ACKNOWLEDGEMENTS 6 3. INTRODUCTION 7…
Read More

RFC 864

Research, RFC, Technology
Network Working Group J. Postel Request for Comments: 864 ISI May 1983 Character Generator Protocol This RFC specifies a standard for the ARPA Internet community. Hosts on the ARPA Internet that choose to implement a Character Generator Protocol are expected to adopt and implement this standard. A useful debugging and measurement tool is a character generator service. A character generator service simply sends data without regard to the input. TCP Based Character Generator Service One character generator service is defined as a connection based application on TCP. A server listens for TCP connections on TCP port 19. Once a connection is established a stream of data is sent out the connection (and any data received is thrown away). This continues until the calling user terminates the connection. It is fairly…
Read More

RFC 826

Research, RFC, Technology
Network Working Group David C. Plummer Request For Comments: 826 (DCP@MIT-MC) November 1982 An Ethernet Address Resolution Protocol -- or -- Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware Abstract The implementation of protocol P on a sending host S decides, through protocol P's routing mechanism, that it wants to transmit to a target host T located some place on a connected piece of 10Mbit Ethernet cable. To actually transmit the Ethernet packet a 48.bit Ethernet address must be generated. The addresses of hosts within protocol P are not always compatible with the corresponding Ethernet address (being different lengths or values). Presented here is a protocol that allows dynamic distribution of the information needed to build tables to translate an address A in protocol P's…
Read More