MULTIPLE ADDRESS SERVICE FOR TRANSPORT (MAST):AN EXTENDED PROPOSAL
draft-crocker-mast-proposal-01

Document Type Expired Internet-Draft (individual)
Author Dave Crocker 
Last updated 2003-09-29 (latest revision 2003-08-29)
Stream (None)
Formats
Expired & archived
pdf htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-crocker-mast-proposal-01.txt

Abstract

Classic Internet transport protocols use a single source IP address and a single destination IP address, as part of the identification for an individual data flow. TCP includes these in its definition of a connection and its calculation of the header checksum. Hence the transport service is tied to a particular IP address pair. This is problematic for multihomed hosts and for mobile hosts. They cannot use more than one, for any single transport association (context). Multiple Address Service for Transport (MAST) defines a mechanism that supports association of multiple IP addresses with any transport association. It requires no change to the Internet infrastructure, no change to IP modules or transport modules in the end-systems, and no new administrative effort. Instead, it defines a layer between classic IP and transport that operates only in the end systems and affects only participating hosts. Additional functionality is obtained by use of a DNS and 'presence' rendezvous service.

Authors

Dave Crocker (dcrocker@bbiw.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)