scispace - formally typeset
Journal ArticleDOI

TUBA: replacing IP with CLNP

D. Katz, +1 more
- 01 May 1993 - 
- Vol. 7, Iss: 3, pp 38-47
Reads0
Chats0
TLDR
The basis of the proposal is to run the Internet transport protocols, the Transmission Control Protocol (TCP), and the User Datagram Protocol (UDP) on top of CLNP in an approach known as TCP and UDP with bigger addresses (TUBA).
Abstract
The Connectionless Network Protocol (CLNP), which is supported by the associated OSI routing protocols, is proposed as a replacement for the Internet Protocol (IP). The basis of the proposal is to run the Internet transport protocols, the Transmission Control Protocol (TCP), and the User Datagram Protocol (UDP) on top of CLNP in an approach known as TCP and UDP with bigger addresses (TUBA). The fundamentals of CLNP and the OSI connectionless routing architecture, the operation of the IP suite with CLNP replacing IP, the support of Internet applications operating on top of TUBA, and a transition plan to a TUBA Internet are discussed. >

read more

Citations
More filters
Proceedings ArticleDOI

NIRA: a new Internet routing architecture

TL;DR: This paper explores various technical problems that would have to be solved to give users the ability to choose: how a user discovers routes and whether the dynamic conditions of the routes satisfy his requirements, how to efficiently represent routes, and how to properly compensate providers if a user chooses to use them.
Book

Open Systems Networking: Tcp/Ip and Osi

TL;DR: This book compares the TCP/IP and OSI architectures and examines each of the protocol layers, using a "top-down" approach, which deals first with the user-visible distributed applications (such as electronic mail, directories, and network management) and then with the way in which these applications are supported by lower-layer networking protocols.
Proceedings ArticleDOI

Flexible routing and addressing for a next generation IP

TL;DR: It is argued that, for reasons of simplicity and evolvability, a single powerful mechanism to achieve a wide range of routing and addressing functions is preferable to having multiple specific mechanisms, one for each function.
Journal ArticleDOI

Distributed multicast address management in the global Internet

TL;DR: A distributed architecture for managing multicast addresses in the global Internet, based on the unicast host address and a per-host address management entity is proposed, and the random allocation strategy is shown to be attractive primarily due to its simplicity.
Journal ArticleDOI

A new forwarding address for next generation networks

TL;DR: The results show that not only can the VA construct a simpler, more secure, and more scalable network, but it also can accommodate many more users than an Internet Protocol (IP) network with the same address length.
References
More filters

A Border Gateway Protocol 4 (BGP-4)

Yakov Rekhter, +1 more
TL;DR: This document, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter- autonomous system routing protocol for the Internet.

User Datagram Protocol

J. Postel
TL;DR: UDP does not guarantee reliability or ordering in the way that TCP does, but its stateless nature is also useful for servers that answer small queries from huge numbers of clients.

Simple Network Management Protocol (SNMP)

TL;DR: This RFC is a re-release of RFC 1098, with a changed "Status of this Memo" section plus a few minor typographical corrections.
Journal ArticleDOI

A Protocol for Packet Network Intercommunication

TL;DR: A protocol that supports the sharing of resources that exist in different packet switching networks is presented and provides for variation in individual network packet sizes, transmission failures, sequencing, flow control, end-to-end error checking, and the creation and destruction of logical process- to-process connections.

An Architecture for IP Address Allocation with CIDR

Yakov Rekhter, +1 more
TL;DR: This approach can allow a great deal of hierarchical abbreviation of routing information, and thereby allows the provider, when informing other routing domains of the addresses that it can reach, to abbreviate the reachability information for a large number of routing domains as a single prefix.