[IRTF-Announce] RFC 9508 on Information-Centric Networking (ICN) Ping Protocol Specification
rfc-editor@rfc-editor.org Mon, 11 March 2024 22:25 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: irtf-announce@ietfa.amsl.com
Delivered-To: irtf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76852C14CF13; Mon, 11 Mar 2024 15:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZbVLcb1eKRYj; Mon, 11 Mar 2024 15:25:36 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 709ACC14CE4A; Mon, 11 Mar 2024 15:23:40 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 6671E192EB64; Mon, 11 Mar 2024 15:23:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
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: <20240311222340.6671E192EB64@rfcpa.amsl.com>
Date: Mon, 11 Mar 2024 15:23:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-announce/DywJyOyF4ORXg6cJiSKstmY1GNk>
Subject: [IRTF-Announce] RFC 9508 on Information-Centric Networking (ICN) Ping Protocol Specification
X-BeenThere: irtf-announce@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IRTF-Announce <irtf-announce.irtf.org>
List-Unsubscribe: <https://mailman.irtf.org/mailman/options/irtf-announce>, <mailto:irtf-announce-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-announce/>
List-Post: <mailto:irtf-announce@irtf.org>
List-Help: <mailto:irtf-announce-request@irtf.org?subject=help>
List-Subscribe: <https://mailman.irtf.org/mailman/listinfo/irtf-announce>, <mailto:irtf-announce-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2024 22:25:38 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9508
Title: Information-Centric Networking (ICN) Ping Protocol
Specification
Author: S. Mastorakis,
D. Oran,
J. Gibson,
I. Moiseenko,
R. Droms
Status: Experimental
Stream: IRTF
Date: March 2024
Mailbox: smastor2@nd.edu,
daveoran@orandom.net,
jcgibson61@gmail.com,
iliamo@mailbox.org,
rdroms.ietf@gmail.com
Pages: 18
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-irtf-icnrg-icnping-12.txt
URL: https://www.rfc-editor.org/info/rfc9508
DOI: 10.17487/RFC9508
This document presents the design of an Information-Centric
Networking (ICN) Ping protocol. It includes the operations of both
the client and the forwarder.
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