Generic Autonomic Signaling Protocol Application Program Interface (GRASP API)
draft-ietf-anima-grasp-api-04
Network Working Group B. Carpenter
Internet-Draft Univ. of Auckland
Intended status: Informational B. Liu, Ed.
Expires: April 9, 2020 Huawei Technologies
W. Wang
X. Gong
BUPT University
October 7, 2019
Generic Autonomic Signaling Protocol Application Program Interface
(GRASP API)
draft-ietf-anima-grasp-api-04
Abstract
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 (ASA) 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 to the support for
asynchronicity in various languages and operating systems.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 9, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
Carpenter, et al. Expires April 9, 2020 [Page 1]
Internet-Draft GRASP API October 2019
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. GRASP API for ASA . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Design Principles . . . . . . . . . . . . . . . . . . . . 4
2.2. Asynchronous Operations . . . . . . . . . . . . . . . . . 5
2.3. API definition . . . . . . . . . . . . . . . . . . . . . 7
2.3.1. Parameters and data structures . . . . . . . . . . . 7
2.3.2. Registration . . . . . . . . . . . . . . . . . . . . 11
2.3.3. Discovery . . . . . . . . . . . . . . . . . . . . . . 13
2.3.4. Negotiation . . . . . . . . . . . . . . . . . . . . . 14
2.3.5. Synchronization and Flooding . . . . . . . . . . . . 19
2.3.6. Invalid Message Function . . . . . . . . . . . . . . 23
3. Implementation Status [RFC Editor: please remove] . . . . . . 24
4. Security Considerations . . . . . . . . . . . . . . . . . . . 24
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.1. Normative References . . . . . . . . . . . . . . . . . . 24
7.2. Informative References . . . . . . . . . . . . . . . . . 24
Appendix A. Error Codes . . . . . . . . . . . . . . . . . . . . 25
Appendix B. Change log [RFC Editor: Please remove] . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
1. Introduction
As defined in [I-D.ietf-anima-reference-model], the Autonomic Service
Agent (ASA) is the atomic entity of an autonomic function, and it is
instantiated on autonomic nodes. When ASAs communicate with each
other, they should use the Generic Autonomic Signaling Protocol
(GRASP) [I-D.ietf-anima-grasp].
As the following figure shows, a GRASP implementation could contain
two major sub-layers. The bottom is the GRASP base protocol module,
which is only responsible for sending and receiving GRASP messages
and maintaining shared data structures. The upper layer contains
some extended functions based upon GRASP basic protocol. For
Show full document text