RFC 8990 on GeneRic Autonomic Signaling Protocol (GRASP)
rfc-editor@rfc-editor.org Sat, 22 May 2021 05:48 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CBB63A153B; Fri, 21 May 2021 22:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-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 od66fynFKdZI; Fri, 21 May 2021 22:47:58 -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 180B93A1536; Fri, 21 May 2021 22:47:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4BAE8F40719; Fri, 21 May 2021 22:47:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8990 on GeneRic Autonomic Signaling Protocol (GRASP)
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, anima@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210522054751.4BAE8F40719@rfc-editor.org>
Date: Fri, 21 May 2021 22:47:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/g7QnVdHk3z_Ojyb8Ggmdih_Yhjg>
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: Sat, 22 May 2021 05:48:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8990
Title: GeneRic Autonomic Signaling Protocol (GRASP)
Author: C. Bormann,
B. Carpenter, Ed.,
B. Liu, Ed.
Status: Standards Track
Stream: IETF
Date: May 2021
Mailbox: cabo@tzi.org,
brian.e.carpenter@gmail.com,
leo.liubing@huawei.com
Pages: 55
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-anima-grasp-15.txt
URL: https://www.rfc-editor.org/info/rfc8990
DOI: 10.17487/RFC8990
This document specifies the GeneRic Autonomic Signaling Protocol
(GRASP), which enables autonomic nodes and Autonomic Service Agents
to dynamically discover peers, to synchronize state with each other,
and to negotiate parameter settings with each other. GRASP depends on
an external security environment that is described elsewhere. The
technical objectives and parameters for specific application
scenarios are to be described in separate documents. Appendices
briefly discuss requirements for the protocol and existing protocols
with comparable features.
This document is a product of the Autonomic Networking Integrated Model and Approach Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
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