[rfc-dist] RFC 8609 on Content-Centric Networking (CCNx) Messages in TLV Format
rfc-editor@rfc-editor.org Wed, 10 July 2019 00:55 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6864A120240 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 9 Jul 2019 17:55:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 Oy03hewDWQhx for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 9 Jul 2019 17:55:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8820A1202C2 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 9 Jul 2019 17:55:00 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8C564B81714; Tue, 9 Jul 2019 17:54:49 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
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
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20190710005447.93B54B81714@rfc-editor.org>
Date: Tue, 09 Jul 2019 17:54:47 -0700
Subject: [rfc-dist] RFC 8609 on Content-Centric Networking (CCNx) Messages in TLV Format
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, icnrg@irtf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
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,
nsolis@linkedin.com,
woodc1@uci.edu
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
specification.
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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
https://www.irtf.org/mailman/listinfo/irtf-announce
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org