[dtn-interest] RFC 7116 on Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding (CBHE), and Bundle Protocol IANA Registries

rfc-editor@rfc-editor.org Thu, 13 February 2014 04:48 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dtn-interest@ietfa.amsl.com
Delivered-To: dtn-interest@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id CE3881A00EC; Wed, 12 Feb 2014 20:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id zERSOQOnedZU; Wed, 12 Feb 2014 20:48:11 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id BB5571A00E8; Wed, 12 Feb 2014 20:48:11 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AA4097FC177; Wed, 12 Feb 2014 20:48:10 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
From: rfc-editor@rfc-editor.org
Message-Id: <20140213044810.AA4097FC177@rfc-editor.org>
Date: Wed, 12 Feb 2014 20:48:10 -0800 (PST)
X-Mailman-Approved-At: Thu, 13 Feb 2014 01:58:17 -0800
Cc: drafts-update-ref@iana.org, dtn-interest@irtf.org, rfc-editor@rfc-editor.org
Subject: [dtn-interest] RFC 7116 on Licklider Transmission Protocol (LTP), Compressed Bundle Header Encoding (CBHE), and Bundle Protocol IANA Registries
X-BeenThere: dtn-interest@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." <dtn-interest.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/dtn-interest/>
List-Post: <mailto:dtn-interest@irtf.org>
List-Help: <mailto:dtn-interest-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 04:48:15 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7116

        Title:      Licklider Transmission Protocol (LTP), Compressed 
                    Bundle Header Encoding (CBHE), and Bundle 
                    Protocol IANA Registries 
        Author:     K. Scott, M. Blanchet
        Status:     Informational
        Stream:     IRTF
        Date:       February 2014
        Mailbox:    kscott@mitre.org, 
        Pages:      10
        Characters: 18568
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-dtnrg-ltp-cbhe-registries-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7116.txt

The DTNRG Research Group has defined the experimental Licklider
Transmission Protocol (LTP) and the Compressed Bundle Header Encoding
(CBHE) mechanism for the InterPlanetary Network ('ipn' URI scheme).
Moreover, RFC 5050 defines values for the Bundle Protocol
administrative record type.  All of these fields are subject to a
registry.  For the purpose of its research work, the group has
created ad hoc registries.  As the specifications are stable and have
multiple interoperable implementations, the group would like to hand
off the registries to IANA for official management.  This document
describes the necessary IANA actions.

This document is a product of the Delay-Tolerant Networking Research Group 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, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/search
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