Browse Prior Art Database

Encoding Network Addresses to Support Operation over Non-OSI Lower Layers (RFC1277)

IP.com Disclosure Number: IPCOM000002096D
Original Publication Date: 1991-Nov-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 13 page(s) / 16K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S.E. Hardcastle-Kille: AUTHOR

Related Documents

10.17487/RFC1277: DOI

Abstract

This document defines a new network address format, and rules for using some existing network address formats. [STANDARDS-TRACK]

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

Network Working Group S.E. Hardcastle-Kille Requests for Comments 1277 University College London November 1991

Encoding Network Addresses to support operation over non-OSI lower layers

Status of this Memo This RFC specifies an IAB standards track 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. Abstract

The OSI Directory specifies an encoding of Presentation Address, which utilises OSI Network Addresses as defined in the OSI Network Layer standards [CCI88] [ISO87a]. The OSI Directory, and any OSI application utilising the OSI Directory must be able use these Network Addresses to identify end systems. Currently, OSI applications are often run over lower layers other than the OSI Network Service. It is neither reasonable nor desirable for groups wishing to investigate and use OSI Applications in conjunction with the OSI Directory to be dependent on a global OSI Network Service. This document defines a new network address format, and rules for using some existing network address formats. The scope of this document is:

1. Any TCP/IP network supporting COTS using RFC 1006.

2. Any mapping of COTS onto X.25 (usually X.25(80)), where X.25 is not used to provide CONS (i.e., only DTE and not Network address is carried).

The approach could also be extended to use with other means of providing COTS (or CLTS). It is not appropriate for use where CONS or CLNS is used to provide COTS (or CLTS).

RFC 1277 Encoding Network Addresses November 1991

1 Introduction

The OSI Directory specifies an encoding of Presentation Address, which utilises OSI Network Addresses as defined in the OSI Network Layer standards [CCI88] [ISO87a]. The OSI Directory, and any OSI application utilising the OSI Directory must be able use these Network Addresses to identify end systems. Currently, OSI applications are often run over lower layers other than the OSI Network Service. It is neither reasonable nor desirable for groups wishing to investigate and use OSI Applications in conjunction with the OSI Directory to be dependent on a global OSI Network Service. This RFCdefines mechanisms to encode addressing information within Network Addresses, in order to support this type of working. In particular, support is defined for RFC 1006 mapping of COTS onto TCP/IP and COTS mapped onto X.25(1980) [RC87, CCI80].

Where an OSI application is run over CLNS on the internet, the NSAP Guidelines of RFC 1237 should be followed [CGC91]. This document must be read in the context of ISO 8348 Addendum 2 [ISO87b]. It will not be meaningful on its own.

1.1 Historical Note

This document was originally published as UCL Research Note RN/89/13 and as a project THORN internal document [Kil89]. It was devised in response to two projects which faced this requirement, and was agreed as a common...

Processing...
Loading...