RFC 6256 on Using Self-Delimiting Numeric Values in Protocols
rfc-editor@rfc-editor.org Thu, 26 May 2011 05:12 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62FFAE070F for <ietf-announce@ietfa.amsl.com>; Wed, 25 May 2011 22:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.326
X-Spam-Level:
X-Spam-Status: No, score=-102.326 tagged_above=-999 required=5 tests=[AWL=0.274, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vDwerEoaNqhj for <ietf-announce@ietfa.amsl.com>; Wed, 25 May 2011 22:12:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id CAB64E06C1 for <ietf-announce@ietf.org>; Wed, 25 May 2011 22:12:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B6D59E078C; Wed, 25 May 2011 22:12:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6256 on Using Self-Delimiting Numeric Values in Protocols
From: rfc-editor@rfc-editor.org
Message-Id: <20110526051204.B6D59E078C@rfc-editor.org>
Date: Wed, 25 May 2011 22:12:04 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2011 05:12:05 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6256
Title: Using Self-Delimiting Numeric Values in
Protocols
Author: W. Eddy, E. Davies
Status: Informational
Stream: IRTF
Date: May 2011
Mailbox: wes@mti-systems.com,
elwynd@folly.org.uk
Pages: 17
Characters: 40765
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-irtf-dtnrg-sdnv-09.txt
URL: http://www.rfc-editor.org/rfc/rfc6256.txt
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.
This document is a product of the IRTF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC