RFC 8609 on Content-Centric Networking (CCNx) Messages in TLV Format

rfc-editor@rfc-editor.org Wed, 10 July 2019 00:54 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 681621202C5 for <ietf-announce@ietfa.amsl.com>; Tue, 9 Jul 2019 17:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id I1pfF7_Mwb4U for <ietf-announce@ietfa.amsl.com>; Tue, 9 Jul 2019 17:54:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DBD0120281 for <ietf-announce@ietf.org>; Tue, 9 Jul 2019 17:54:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 93B54B81714; Tue, 9 Jul 2019 17:54:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
Subject: =?UTF-8?B?UkZDIDg2MDkgb24gQ29udGVudC1DZW50cmljIE5ldHdvcmtpbmcgKENDTngpIE1lc3NhZ2VzIGluIFRMViBGb3JtYXQ=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, icnrg@irtf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190710005447.93B54B81714@rfc-editor.org>
Date: Tue, 9 Jul 2019 17:54:47 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/1P63xYA4TSB3D0Pht327xuOrDIo>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 10 Jul 2019 00:54:57 -0000

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

        RFC 8609

        Title:      Content-Centric Networking (CCNx) Messages in 
                    TLV Format 
        Author:     M. Mosko,
                    I. Solis,
                    C. Wood
        Status:     Experimental
        Stream:     IRTF
        Date:       July 2019
        Mailbox:    marc.mosko@parc.com, 
        Pages:      46
        Characters: 109089
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-icnrg-ccnxmessages-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8609

        DOI:        10.17487/RFC8609

Content-Centric Networking (CCNx) is a network protocol that uses a
hierarchical name to forward requests and to match responses to
requests.  This document specifies the encoding of CCNx messages in a
TLV packet format, including the TLV types used by each message
element and the encoding of each value.  The semantics of CCNx
messages follow the encoding-independent CCNx Semantics

This document is a product of the Information Centric Networking
research group (ICNRG).  The document received wide review among
ICNRG participants and has two full implementations currently in
active use, which have informed the technical maturity of the
protocol specification.

This document is a product of the Information-Centric 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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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