Browse Prior Art Database

Multiprotocol Interoperability In IPng (RFC1683)

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

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Clark: AUTHOR [+2]

Related Documents

10.17487/RFC1683: DOI

Abstract

In this document, we identify several features that affect a protocol's ability to operate in a multiprotocol environment and propose the incorporation of these features into IPng. 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 12% of the total text.

Network Working Group R. Clark Request for Comments: 1683 M. Ammar Category: Informational K. Calvert Georgia Institute of Technology August 1994

Multiprotocol Interoperability In 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.

1. Executive Summary

The two most commonly cited issues motivating the introduction of IPng are address depletion and routing table growth in IPv4. Further motivation is the fact that the Internet is witnessing an increasing diversity in the protocols and services found in the network. When evaluating alternatives for IPng, we should consider how well each alternative addresses the problems arising from this diversity. In this document, we identify several features that affect a protocol’s ability to operate in a multiprotocol environment and propose the incorporation of these features into IPng.

Our thesis, succinctly stated, is: The next generation Internet Protocol should have features that support its use with a variety of protocol architectures.

2. Introduction

The Internet is not a single protocol network [4]. While TCP/IP remains the primary protocol suite, other protocols (e.g., IPX, AppleTalk, OSI) exist either natively or encapsulated as data within IP. As new protocols continue to be developed, we are likely to find that a significant portion of the traffic in future networks is not from single-protocol communications. It is important to recognize that multiprotocol networking is not just a transition issue. For instance, we will continue to see tunneling used to carry IPX traffic

Clark, Ammar & Calvert [Page 1]

RFC 1683 Multiprotocol Interoperability In IPng August 1994

over the Internet between two Novell networks. Furthermore, the introduction of IPng is not going to result in a near term elimination of IPv4. Even when IPng becomes the primary protocol used in the Internet, there will still be IPv4 systems in use. We should consider such multiprotocol uses of the network as we design future protocols that can efficiently handle mixed protocol traffic.

We have identified several issues related to the way in which protocols operate in a multiprotocol environment. Many of these issues have traditionally been deemed "less important" by protocol designers since their goal was to optimize for the case where all systems supported the same protocol. With the increasing diversity of network protocols, this approach is no longer practical. By addressing the issues outlined in this paper, we can simplify the introduction of IPng to the Internet and reduce the risk for network managers faced with the prospect of supporting...

Processing...
Loading...