RFC 6256: Using Self-Delimiting Numeric Values in Protocols
In plain English — editorial summary, not part of the RFC
Self-Delimiting Numeric Values (SDNVs) have recently been introduced as a field type in proposed Delay-Tolerant Networking protocols. SDNVs encode an arbitrary-length non-negative integer or arbitrary- length bitstring with minimum overhead. They are intended to provide protocol flexibility without sacrificing economy and to assist in future-proofing protocols under development. This document describes formats and algorithms for SDNV encoding and decoding, along with notes on implementation and usage. This document is a product of the Delay-Tolerant Networking Research Group and has been reviewed by that group. No objections to its publication as an RFC were raised. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6256
- Published
- May 2011
- Authors
- W. Eddy; E. Davies
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6255Delay-Tolerant Networking Bundle Protocol IANA RegistriesCurrent
May 2011
- RFC 6258Delay-Tolerant Networking Metadata Extension BlockCurrent
May 2011
- RFC 6259Delay-Tolerant Networking Previous-Hop Insertion BlockCurrent
May 2011
- RFC 6260Compressed Bundle Header Encoding (CBHE)Updated
May 2011
- RFC 6693Probabilistic Routing Protocol for Intermittently Connected NetworksCurrent
August 2012
- RFC 5050Bundle Protocol SpecificationCurrent
November 2007
- RFC 9675Delay-Tolerant Networking Management Architecture (DTNMA)Current
November 2024
- RFC 9713Bundle Protocol Version 7 Administrative Record Types RegistryCurrent
January 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?