Re: [icnrg] RFC 8569 on Content-Centric Networking (CCNx) Semantics

"Dirk Kutscher" <ietf@dkutscher.net> Wed, 10 July 2019 05:58 UTC

Return-Path: <ietf@dkutscher.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1F91200FF for <icnrg@ietfa.amsl.com>; Tue, 9 Jul 2019 22:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 ll3ge0kLn3wA for <icnrg@ietfa.amsl.com>; Tue, 9 Jul 2019 22:58:45 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 189B71200DB for <icnrg@irtf.org>; Tue, 9 Jul 2019 22:58:44 -0700 (PDT)
Received: from [192.168.45.0] ([77.247.85.104]) by mrelayeu.kundenserver.de (mreue107 [212.227.15.183]) with ESMTPSA (Nemesis) id 1N8nrc-1iWwnI2k5O-015u7c for <icnrg@irtf.org>; Wed, 10 Jul 2019 07:58:39 +0200
From: Dirk Kutscher <ietf@dkutscher.net>
To: icnrg@irtf.org
Date: Wed, 10 Jul 2019 07:58:30 +0200
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <D605FD3D-274C-443A-B705-AE8EFF08551A@dkutscher.net>
In-Reply-To: <20190710005440.83A1BB8170B@rfc-editor.org>
References: <20190710005440.83A1BB8170B@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K1:rReElSoRlYGYyHLu4SAsq9bFldnYQ/5B+FpgquI0SQIy6vnW7QT caav01m7ZE3qIONhBleaOPcULqIYSz/pThufjQm2nthLgBLH0K/RalwMYEyhiqDsnzSJAb+ tJTUgRMfdq7LnMow8XRXpxqwOYlKHZ2D52c9c7jn9Ag5AZ7Ond+YvFXjztGt400C8UIpxX5 ugVymhCcvYDJ/HCpYH4MQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:cesBNzIXBwg=:EKlApa+VuEuQmBCXWN/YWJ 80AwIcdv3IOn8IeHHCuTe/I+S56t3KGScxw1u6vWedUvHTM14poMwYtzMtRgbtkujvvS3l+la PLor9OXIkzkIsKLy8MbwwMIMVOh1CiD8iNei8/C+JPJ4eQ7tHCWB36/Xml8HGWny0E16ibfeq rrFsoNK6jL14BXkhi97wPO35sNfKKpBbRojZjHHSqtNk66Jg3LX2PYO7jIdF2Lpe70qSEJdzi vZrV4TA0gWEpyg+6scDaz6VbJrSEU6ASDUaHgXtTK/Kbxtgllwuls7Yz0bL+h1BY6BycL4rXZ WcOAMSrzJAqnsSGwqFURDEygmEYgyoJB60zrXYv85DjTsP1QW0k7TPl2NLXRd8SsSThRm83A6 6XuEbCPljx2T1GbozLdwoj1OtUI0BO2KjZhs9FtVVUvpdmSLZ60AmHdbSjLNV+bxGMUcyKXiz Ac+rfnhAF+3UILZcpZbp8QwRaZdS03yK1IXAQgi75uhzq6EiOVh+3Q46kM7SHdYT0VhQ6t+AZ lwLohcdRGHGOpVSvYpq7UvmI2s/w9a6IFdcNAanYqPY4vKY51if6GhLNw4Juuofj1h1nmB4CP iTOuyb/Fd1mGgDPCxFI2eHzQC1BhawQ5Mbt+GEvM7Mg9E+U6oVCNUYZ35SJz40OEioLTs7SEt zlAIKLNNweAjikFhujoiRqm+NjLpxaZL63IAiX2frWml7nZdQng6m+KaFoN2QNJmfGMjSyPoE 6RdBIWKWnXekOZZq+LDyVZqCGY4JEvrIoy1FPLqhy4S7HYfsOYljtx7+kiP7QDvyk3t7HbBa0 2zPFTXd
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/WR8R4pg6iKxuDebL0RTc3X-gzRs>
Subject: Re: [icnrg] RFC 8569 on Content-Centric Networking (CCNx) Semantics
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2019 05:58:48 -0000

Hello ICNRG,

that’s a major milestone for ICNRG and the ICN community at large!

Many, many thanks to Marc Mosko for putting a lot of effort intro 
improving the two documents and for sorting out all the issues with the 
RFC editor team.

We hope you can join us Montreal to celebrate this achievement.

Best regards,
Dirk, Börje, Dave





On 10 Jul 2019, at 2:54, rfc-editor@rfc-editor.org wrote:

> 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
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce