RFC 8991 on GeneRic Autonomic Signaling Protocol Application Program Interface (GRASP API)
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 F1F293A1589; Fri, 21 May 2021 22:48:55 -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 C20pEZdAe4Ox; Fri, 21 May 2021 22:48:51 -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 ECC233A154D; Fri, 21 May 2021 22:48:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 07E08F40719; Fri, 21 May 2021 22:48:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8991 on GeneRic Autonomic Signaling Protocol Application Program Interface (GRASP API)
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: <20210522054845.07E08F40719@rfc-editor.org>
Date: Fri, 21 May 2021 22:48:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/lry3xv7wkIo1jMvbCUm_fsrjaK4>
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:49:05 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8991
Title: GeneRic Autonomic Signaling Protocol Application
Program Interface (GRASP API)
Author: B. Carpenter,
B. Liu, Ed.,
W. Wang,
X. Gong
Status: Informational
Stream: IETF
Date: May 2021
Mailbox: brian.e.carpenter@gmail.com,
leo.liubing@huawei.com,
wdwang@bupt.edu.cn,
xygong@bupt.edu.cn
Pages: 29
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-anima-grasp-api-10.txt
URL: https://www.rfc-editor.org/info/rfc8991
DOI: 10.17487/RFC8991
This document is a conceptual outline of an Application Programming
Interface (API) for the GeneRic Autonomic Signaling Protocol (GRASP).
Such an API is needed for Autonomic Service Agents (ASAs) calling the
GRASP protocol module to exchange Autonomic Network messages with
other ASAs. Since GRASP is designed to support asynchronous
operations, the API will need to be adapted according to the support
for asynchronicity in various programming languages and operating
systems.
This document is a product of the Autonomic Networking Integrated Model and Approach Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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