What's In A Name:Thoughts from the NSRG
draft-irtf-nsrg-report-10
Document | Type |
Expired Internet-Draft
(gen)
Expired & archived
|
|
---|---|---|---|
Authors | Eliot Lear , Ralph Droms | ||
Last updated | 2003-12-17 (Latest revision 2003-09-22) | ||
RFC stream | Internet Research Task Force (IRTF) | ||
Intended RFC status | Informational | ||
Formats | |||
Stream | IRTF state | (None) | |
Consensus boilerplate | Unknown | ||
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
Telechat date | (None) | ||
Responsible AD | Russ Housley | ||
IESG note | IRTF document. | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Over the last few years, the use of IP addresses for Internet connectivity has changed dramatically. The Name Space Research Group (NSRG) was chartered by the IRTF to review these changes, and make recommendations on whether or not remediation within the protocol stack is necessary. This document reports the outcome of some of the discussions within the research group. One of the questiones addressed by the NSRG is: Does the TCP/IP protocol suite need an additional level of naming above layer 3 but below the application layer? There was no consensus on the answer. This document reviews the motivation for an additional naming mechanism, reviews related work, proposes a straw man 'stack name' and discusses the structure and use of those names.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)