RFC 7242 on Delay-Tolerant Networking TCP Convergence-Layer Protocol

rfc-editor@rfc-editor.org Fri, 13 June 2014 16:46 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21D1F1B2973 for <ietf-announce@ietfa.amsl.com>; Fri, 13 Jun 2014 09:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level:
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IRNscRfmd4AM for <ietf-announce@ietfa.amsl.com>; Fri, 13 Jun 2014 09:46:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED981B293F for <ietf-announce@ietf.org>; Fri, 13 Jun 2014 09:46:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 378A918000E; Fri, 13 Jun 2014 09:45:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
Subject: RFC 7242 on Delay-Tolerant Networking TCP Convergence-Layer Protocol
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140613164522.378A918000E@rfc-editor.org>
Date: Fri, 13 Jun 2014 09:45:22 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/0LkYEq3w-lr_uFnMndntFiYweTc
Cc: drafts-update-ref@iana.org, dtn-interest@irtf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 13 Jun 2014 16:46:25 -0000

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

        
        RFC 7242

        Title:      Delay-Tolerant Networking 
                    TCP Convergence-Layer Protocol 
        Author:     M. Demmer,
                    J. Ott,
                    S. Perreault
        Status:     Experimental
        Stream:     IRTF
        Date:       June 2014
        Mailbox:    demmer@cs.berkeley.edu, 
                    jo@netlab.tkk.fi, 
                    simon@per.reau.lt
        Pages:      22
        Characters: 53818
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-dtnrg-tcp-clayer-09.txt

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

This document describes the protocol for the TCP-based convergence
layer for Delay-Tolerant Networking (DTN).  It is the product of the
IRTF's DTN Research Group (DTNRG).

This document is a product of the Delay-Tolerant Networking Research Group 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, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
  http://www.irtf.org/mailman/listinfo/irtf-announce

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