NDN Message Format Proposal
draft-stapp-icnrg-ndn-msgs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark Stapp | ||
| Last updated | 2015-07-20 (Latest revision 2015-01-08) | ||
| 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
This memo defines an on-the-wire format for Named-data Networking (NDN) protocol messages. NDN packets begin with a fixed-size header. After the header, the remainder of the message is composed of type- length-value (TLV) tuples. The Type and Length fields use a compact, fixed-size encoding scheme. The TLVs for message attributes that are standardized are defined in a registry. Part of the TLV number-space is reserved for standardized attributes. Other parts of the number- space are set aside for experimental use.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)