[rfc-dist] RFC 8569 on Content-Centric Networking (CCNx) Semantics

rfc-editor@rfc-editor.org Wed, 10 July 2019 00:54 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 1A7F91200CE for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 9 Jul 2019 17:54:48 -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 kkEsfh87PHVv for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 9 Jul 2019 17:54:46 -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 D70A51200F6 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 9 Jul 2019 17:54:45 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 004A5B8170B; Tue, 9 Jul 2019 17:54:42 -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 83A1BB8170B; Tue, 9 Jul 2019 17:54:40 -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: <20190710005440.83A1BB8170B@rfc-editor.org>
Date: Tue, 9 Jul 2019 17:54:40 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8569_on_Content-Centric_Networking_=28C?= =?utf-8?q?CNx=29_Semantics?=
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 8569

        Title:      Content-Centric Networking (CCNx) Semantics 
        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:      40
        Characters: 96155
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-icnrg-ccnxsemantics-10.txt

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

        DOI:        10.17487/RFC8569

This document describes the core concepts of the Content-Centric
Networking (CCNx) architecture and presents a network protocol based
on two messages: Interests and Content Objects.  It specifies the set
of mandatory and optional fields within those messages and describes
their behavior and interpretation.  This architecture and protocol
specification is independent of a specific wire encoding.

The protocol also uses a control message called an Interest Return,
whereby one system can return an Interest message to the previous hop
due to an error condition.  This indicates to the previous hop that
the current system will not respond to the Interest.

This document is a product of the Information-Centric Networking
Research Group (ICNRG).  The document received wide review among
ICNRG participants.  Two full implementations are in active use and
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