Browse Prior Art Database

ARPANET AHIP-E Host Access Protocol (enhanced AHIP) (RFC1005)

IP.com Disclosure Number: IPCOM000001808D
Original Publication Date: 1987-May-01
Included in the Prior Art Database: 2005-May-22
Document File: 35 page(s) / 68K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Khanna: AUTHOR [+2]

Abstract

This RFC is a proposed specification for the encoding of Class A IP addresses for use on ARPANET-style networks such as the Milnet and Arpanet, and for enhancements to the AHIP Protocol (AHIP is the preferred term for what has previously been known as the 1822 protocol). These enhancements and modifications are partially motivated by a need to overcome the current address limitation of 256 PSNs per network and by a desire to allow hosts to take advantage of logical addressing with minimal change to their AHIP software. This enhanced AHIP protocol will be referred to as "AHIP-E". These enhancements will:

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group                            Atul Khanna, Andy Malis
Request for Comments: 1005                      BBN Communications Corp.
                                                                May 1987


        The ARPANET AHIP-E Host Access Protocol (Enhanced AHIP)


1. Status of this Memo

   This RFC is a proposed specification for the encoding of Class A
   IP addresses for use on ARPANET-style networks such as the Milnet
   and Arpanet, and for enhancements to the ARPANET AHIP Host Access
   Protocol (AHIP; formerly known as 1822).  These enhancements
   increase the size of the PSN field, allow ARPANET hosts to use
   logical names to address each other, allow for the communication
   of type-of-service information from the host to the PSN and
   enable the PSN to provide congestion feedback to the host on a
   connection basis. Distribution of this memo is unlimited.
   Comments on this RFC should be sent to the netmail address
   "ahipe@bbn.com".


Khanna & Malis                                                  [Page 1]
RFC 1005                                                        May 1987


                             Table of Contents


        1   INTRODUCTION.......................................... 4

        2   IP ISSUES............................................. 6
        2.1   Current Interpretation of Class A IP Address
              Fields
               ................................................... 6
        2.2   Requirements and Constraints Affecting New
              Class A Mapping
               ................................................... 7
        2.3   New Interpretation of IP Address Fields............. 8
        2.4   Discussion of the New Mapping.......................10
        2.5   Interoperability between Current AHIP and
              AHIP-E
               ...................................................11

        3   LOGICAL ADDRESSING................................... 13
        3.1   Addresses and Names................................ 13
        3.2   Name Translations.................................. 14
        3.2.1   Authorization and Effectiveness.................. 15
        3.2.2   Translation Policies............................. 16
        3.2.3   Reporting Destination Host Downs................. 17
        3.3   Establishing Host-PSN Communications............... 18
        3.4   Name Server........................................ 19

        4   OTHER CHANGES......................