Goals for Organizational-Scope Communications
draft-hain-templin-ipv6-localcomm-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tony L. Hain , Fred L. Templin | ||
| Last updated | 2003-12-09 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The IPv6 addressing architecture specifies formats for unicast addresses, but provides no operational guidelines for their use. There is a clear need for IPv6 to support organizational-scope communications whether members of the organization are located in the same site or different sites. Aspects of certain types of sites introduce challenges for supporting organizational-scope communications. Of special interest are nomadic sites, e.g., sites that are intermittently-connected or disconnected from the global Internet, sites that frequently change provider points of attachment, sites that temporarily or permanently merge with other sites, etc. This memo will discuss scenarios and goals for IPv6 support organizational-scope communications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)