RFC 6260 on Compressed Bundle Header Encoding (CBHE)
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 0C246E0746 for <ietf-announce@ietfa.amsl.com>; Wed, 25 May 2011 22:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.344
X-Spam-Level:
X-Spam-Status: No, score=-102.344 tagged_above=-999 required=5 tests=[AWL=0.256, 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 n51B94y1QUIG for <ietf-announce@ietfa.amsl.com>; Wed, 25 May 2011 22:12:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id B7A6CE0728 for <ietf-announce@ietf.org>; Wed, 25 May 2011 22:12:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A7774E07A2; Wed, 25 May 2011 22:12:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6260 on Compressed Bundle Header Encoding (CBHE)
From: rfc-editor@rfc-editor.org
Message-Id: <20110526051251.A7774E07A2@rfc-editor.org>
Date: Wed, 25 May 2011 22:12:51 -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:55 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6260
Title: Compressed Bundle Header Encoding (CBHE)
Author: S. Burleigh
Status: Experimental
Stream: IRTF
Date: May 2011
Mailbox: Scott.C.Burleigh@jpl.nasa.gov
Pages: 12
Characters: 25381
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-irtf-dtnrg-cbhe-09.txt
URL: http://www.rfc-editor.org/rfc/rfc6260.txt
This document describes a convention by which Delay-Tolerant
Networking (DTN) Bundle Protocol (BP) "convergence-layer" adapters
may represent endpoint identifiers in a compressed form within the
primary blocks of bundles, provided those endpoint identifiers
conform to the structure prescribed by this convention.
Compressed Bundle Header Encoding (CBHE) compression is a
convergence-layer adaptation. It is opaque to bundle processing.
Therefore, it has no impact on the interoperability of different
Bundle Protocol implementations, but instead affects only the
interoperability of different convergence-layer adaptation
implementations.
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 defines an Experimental
Protocol for the Internet community.
This document is a product of the IRTF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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