[Anima] text for grasp-07 (-08)
Michael Richardson <mcr+ietf@sandelman.ca> Wed, 19 October 2016 12:37 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20A291294F7 for <anima@ietfa.amsl.com>; Wed, 19 Oct 2016 05:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.332
X-Spam-Level:
X-Spam-Status: No, score=-2.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.431, SPF_PASS=-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 p3bL4Zo23lSZ for <anima@ietfa.amsl.com>; Wed, 19 Oct 2016 05:37:51 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95734129456 for <anima@ietf.org>; Wed, 19 Oct 2016 05:37:51 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D56612009E for <anima@ietf.org>; Wed, 19 Oct 2016 08:52:28 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 5EA0163AFE for <anima@ietf.org>; Wed, 19 Oct 2016 08:37:50 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 19 Oct 2016 08:37:50 -0400
Message-ID: <26928.1476880670@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/4_o5wEJeH6cN6gdFNuliB9AzbDw>
Subject: [Anima] text for grasp-07 (-08)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 12:37:54 -0000
Brian, I began reading draft-carpenter-anima-asa-guidelines-00 and also draft-liu-anima-grasp-api-01. (Chairs, I think they should become WG items) I think though, that section 3.3 of asa-guidelines ought to be worked into the GRASP protocol document's introduction. (But should remain in asa-guidelines as is, except for "kernel") This would be some of the text that I suggested was missing that explains how to use the different mechanisms. I haven't read -08 yet, mind you, so many you got this already. Let me tweak the text slightly below. I suggest that the world "kernel" may be confusing to some developers: it may make them think that GRASP requires access to toggle hardware bits... 3.3. Mechanisms offered by GRASP GRASP is expected to run as an operating system core module, providing an API (such as [I-D.liu-anima-grasp-api]) to interface to less privileged ASAs. Thus ASAs may operate without special privilege, unless they need it for other reasons (such as configuring IP addresses or manipulating routing tables). The GRASP mechanisms used by the ASA are built around GRASP objectives defined as data structures containing administrative information such as the objective's unique name, and its current value. The format and size of the value is not restricted by the protocol, except that it must be possible to serialise it for transmission in CBOR [RFC7049], which is no restriction at all in practice. The GRASP provides the following mechanisms: o A discovery mechanism (M_DISCOVERY, M_RESPONSE), by which an ASA can discover other ASAs supporting a given objective. o A negotiation request mechanism (M_REQ_NEG), by which an ASA can start negotiation of an objective with a counterpart ASA. With this, there is a corresponding negotiation response mechanism (M_NEGOTIATE) mechanism for an ASA that wishes to respond to negotiation requests, and a set of functions to support negotiating steps (M_END). o A synchronization mechanism (M_REQ_SYN), by which an ASA can request the current value of an objective from a counterpart ASA. With this, there is a corresponding listening function for an ASA that wishes to respond to synchronization requests. o A flood mechanism (M_FLOOD), by which an ASA can cause the current value of an objective to be flooded throughout the AN so that any ASA can receive it. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Anima] text for grasp-07 (-08) Michael Richardson
- Re: [Anima] text for grasp-07 (-08) Brian E Carpenter