Browse Prior Art Database

ARPANET 1822L Host Access Protocol (RFC0851)

IP.com Disclosure Number: IPCOM000003898D
Original Publication Date: 1983-Apr-01
Included in the Prior Art Database: 2019-Feb-14
Document File: 47 page(s) / 45K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A.G. Malis: AUTHOR

Related Documents

10.17487/RFC0851: DOI

Abstract

This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. 1822L allows ARPANET hosts to use logical names as well as 1822's physical port locations to address each other. This RFC is also being presented as a solicitation of comments on 1822L, especially from host network software implementers and maintainers. Obsoletes RFC 802.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 8% of the total text.

Request for Comments: 851 Obsoletes RFC: 802

The ARPANET 1822L Host Access Protocol

RFC 851

Andrew G. Malis ARPANET Mail: malis@bbn-unix

Bolt Beranek and Newman Inc. 50 Moulton St. Cambridge, MA 02238

April 1983

This RFC specifies the ARPANET 1822L Host Access Protocol, which is a successor to the existing 1822 Host Access Protocol. 1822L allows ARPANET hosts to use logical names as well as 1822’s physical port locations to address each other. The RFC is also being presented as a solicitation of comments on 1822L, especially from host network software implementers and maintainers.

1822L Host Access Protocol April 1983 RFC 851

Table of Contents

1 INTRODUCTION.......................................... 1 2 THE ARPANET 1822L HOST ACCESS PROTOCOL................ 4 2.1 Addresses and Names................................. 6 2.2 Name Translations................................... 8 2.2.1 Authorization and Effectiveness................... 8 2.2.2 Translation Policies............................. 11 2.2.3 Reporting Destination Host Downs................. 13 2.2.4 1822L and 1822 Interoperability.................. 16 2.3 Uncontrolled Packets............................... 18 2.4 Establishing Host-IMP Communications............... 20 2.5 Counting RFMS When Using 1822L..................... 22 2.6 1822L Name Server.................................. 24 3 1822L LEADER FORMATS................................. 27 3.1 Host-to-IMP 1822L Leader Format.................... 28 3.2 IMP-to-Host 1822L Leader Format.................... 35 4 REFERENCES........................................... 43

- i -

1822L Host Access Protocol April 1983 RFC 851

FIGURES

1822 Address Format....................................... 6 1822L Name Format......................................... 7 1822L Address Format...................................... 7 Communications between different host types.............. 17 Host-to-IMP 1822L Leader Format.......................... 28 NDM Message Format....................................... 31 IMP-to-Host 1822L Leader Format.......................... 35 Name Server Reply Format................................. 39

- ii -

1822L Host Access Protocol April 1983 RFC 851

1 INTRODUCTION

This RFC specifies the ARPANET 1822L Host Access Protocol, which

will allow hosts to use logical addressing (i.e., host names that

are independent of their physical location on the ARPANET) to

communicate with each other. This new host access protocol is

known as the ARPANET 1822L (for Logical) Host Access Protocol,

and is a successor to the current ARPANET 1822 Host Access

Protocol, which is described in sections 3.3 and 3.4 of BBN

Report 1822 [1]. Although the 1822L protocol uses different

Host-IMP leaders than the 1822 protocol, the IMPs will continue

to support the 1822 protocol, and hosts using either protocol can

readily communicate with each other (the IMPs will handle the

translation automatically).

There is one major restriction to the new 1822L protocol: it

will b...

Processing...
Loading...