Browse Prior Art Database

Six Virtual Inches to the Left: The Problem with IPng (RFC1705)

IP.com Disclosure Number: IPCOM000002544D
Original Publication Date: 1994-Oct-01
Included in the Prior Art Database: 2019-Feb-12
Document File: 27 page(s) / 38K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Carlson: AUTHOR [+1]

Related Documents

10.17487/RFC1705: DOI

Abstract

This document was submitted to the IETF IPng area in response to RFC 1550. This RFC suggests that a new version of TCP (TCPng), and UDP, be developed and deployed. 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 7% of the total text.

Network Working Group: R. Carlson Request for Comments: 1705 ANL Category: Informational D. Ficarella Motorola October 1994

Six Virtual Inches to the Left: The Problem with IPng

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.

Abstract

This document was submitted to the IETF IPng area in response to RFC 1550. Publication of this document does not imply acceptance by the IPng area of any ideas expressed within. Comments should be submitted to the big-internet@munnari.oz.au mailing list.

Overview

This RFC suggests that a new version of TCP (TCPng), and UDP, be developed and deployed. It proposes that a globally unique address (TA) be assigned to Transport layer protocol (TCP/UDP). The purpose of this TA is to uniquely identify an Internet node without specifying any routing information. A new version of TCP, and UDP, will need to be developed describing the new header fields and formats. This new version of TCP would contain support for high bandwidth-delay networks. Support for multiple network layer (Internet Protocol) protocols is also possible with this new TCP. Assigning an address to TCP/UDP would allow for the support of multiple network layer protocols (IPng’s). The TA would identify the location of an Internet node. The IPng layer would provide routing information to the Internet. Separating the location and routing functions will greatly increase the versatility of the Internet.

Carlson & Ficarella [Page 1]

RFC 1705 Six Virtual Inches to the Left: IPng Problems October 1994

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Historical perspective . . . . . . . . . . . . . . . . . . . . 3 2.1 OSI and the 7 layer model . . . . . . . . . . . . . . . 3 2.2 Internet Evolution . . . . . . . . . . . . . . . . . . . 4 2.3 The Reasons for Change . . . . . . . . . . . . . . . . . 4 2.3.1 Class-B Address Exhaustion . . . . . . . . . . . 4 2.3.2 Routing Table Growth . . . . . . . . . . . . . . 5 3. The Problems with Change . . . . . . . . . . . . . . . . . . . 5 3.1 TCP/UDP Implementations . . . . . . . . . . . . . . . . 6 3.2 User Applications . . . . . . . . . . . . . . . . . . . 6 3.3 The Entrenched Masses . . . . . . . . . . . . . . . . . 6 4. Making TCP & UDP Protocol Independent . . . . . . . . . . . . 7 4.1 Transport Addressing . . . . . . . . . . . . . . . . . . 7 4.2 TCPng . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.3 Mandatory Options . . . . . . . . . . . . . . . . . . . 15 4.4 Optional Options . . . . . . . . . . . . . . . . . . . . 16 4.5 Compatibility Issues . . . . . . . . . . . . . . . . . . 16 4.5.1 Backward Compatibility . . . . . . . . . . . . . 17 4.6 Level 4 Gateways . . . . . . . . . . . . . . . . . . . . 17 4.7 Error Conditions . . . . . . . . . . . . . . . . . . . . 18 5. Advantages and Disadvantages of this approach . . . . . . . . 18 6. Conclus...

Processing...
Loading...