Name-Based Sockets Architecture
draft-ubillos-name-based-sockets-03

Document Type Expired Internet-Draft (individual)
Authors Javier Ubillos  , Mingwei Xu  , Zhongxing Ming  , Christian Vogt 
Last updated 2010-09-17
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
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-ubillos-name-based-sockets-03.txt

Abstract

This memo defines Name-based sockets. name-based sockets allow application developers to refer to remote hosts (and it self) by name only, passing on all IP (locator) management to the operating system. Applications are thus relieved of re-implementing features such as multi-homing, mobility, NAT traversal, IPv6/IPv4 interoperability and address management in general. The operating system can in turn re- use the same solutions for a whole set of guest applications. name- based sockets aims to provide a whole set of features without adding new indirection layers, new delays or other dependences while maintaining transparent backwards compatibility.

Authors

Javier Ubillos (jav@sics.se)
Mingwei Xu (xmw@cernet.edu.cn)
Zhongxing Ming (mingzx@126.com)
Christian Vogt (christian.vogt@ericsson.com)

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