Browse Prior Art Database

Pip Near-term Architecture (RFC1621)

IP.com Disclosure Number: IPCOM000002456D
Original Publication Date: 1994-May-01
Included in the Prior Art Database: 2019-Feb-12
Document File: 51 page(s) / 75K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Francis: AUTHOR

Related Documents

10.17487/RFC1621: DOI

Abstract

The purpose of this RFC and the companion RFC "Pip Header Processing" are to record the ideas (good and bad) of Pip. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

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

Network Working Group P. Francis Request for Comments: 1621 NTT Category: Informational May 1994

Pip Near-term Architecture

Status of this Memo

This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Preamble

During 1992 and 1993, the Pip internet protocol, developed at Belclore, was one of the candidate replacments for IP. In mid 1993, Pip was merged with another candidate, the Simple Internet Protocol (SIP), creating SIPP (SIP Plus). While the major aspects of Pip-- particularly its distinction of identifier from address, and its use of the source route mechanism to achieve rich routing capabilities-- were preserved, many of the ideas in Pip were not. The purpose of this RFC and the companion RFC "Pip Header Processing" are to record the ideas (good and bad) of Pip.

This document references a number of Pip draft memos that were in various stages of completion. The basic ideas of those memos are presented in this document, though many details are lost. The very interested reader can obtain those internet drafts by requesting them directly from me at <francis@cactus.ntt.jp>.

The remainder of this document is taken verbatim from the Pip draft memo of the same title that existed when the Pip project ended. As such, any text that indicates that Pip is an intended replacement for IP should be ignored.

Abstract

Pip is an internet protocol intended as the replacement for IP version 4. Pip is a general purpose internet protocol, designed to evolve to all forseeable internet protocol requirements. This specification describes the routing and addressing architecture for near-term Pip deployment. We say near-term only because Pip is designed with evolution in mind, so other architectures are expected in the future. This document, however, makes no reference to such future architectures.

Francis [Page 1]

RFC 1621 Pip Near-term Architecture May 1994

Table of Contents

1. Pip Architecture Overview ................................... 4 1.1 Pip Architecture Characteristics ........................... 4 1.2 Components of the Pip Architecture ......................... 5

2. A Simple Example ............................................ 6

3. Pip Overview ................................................ 7

4. Pip Addressing .............................................. 9 4.1 Hierarchical Pip Addressing ................................ 9 4.1.1 Assignment of (Hierarchical) Pip Addresses ............... 12 4.1.2 Host Addressing .......................................... 14 4.2 CBT Style Multicast Addresses .............................. 15 4.3 Class D Style Multicast Addresses .......................... 16 4.4 Anycast Addressing ......................................... 16

5. Pip IDs ..................................................... 17

6. Use of DNS .................................................. 18 6.1 Information Held by DNS ..................................

Processing...
Loading...