Re: [Anima] some minor comments on draft-ietf-anima-grasp-distribution-09

Hi Michael, Thanks much for your detailed review (again). And sorry for the delayed response. See inline please. > -Original Message- > From: Anima On Behalf Of Michael Richardson > Sent: Monday, January 1, 2024 2:53 AM > To: anima@ietf.org > Subject: [Anima] some minor comments on >

Re: [Anima] Adoption call for draft-liu-anima-grasp-distribution (ends 01/27/2020)

Hi Toerless, Thanks a lot for summarizing the comments! We'll revise a new version as you suggested, and upload it soon. We'll also try to maintain a github repo. Best regards, Bing > -Original Message- > From: Toerless Eckert [mailto:t...@cs.fau.de] > Sent: Tuesday, February 11, 2020

Re: [Anima] Adoption call for draft-liu-anima-grasp-distribution (ends 01/27/2020)

Hi Dear all, I support the adoption as a co-author. I believe this document make useful extension to current ANI/GRASP, to allow information distribution capabilities in a flexible manner (e.g. Pub/Sub, Selective Flooding etc.) . And as a co-author I'd like to continue refine the draft with

Re: [Anima] I-D Action: draft-liu-anima-grasp-distribution-13.txt

Hi Brian, Thanks for the detailed review. Please see my replies inline. > -Original Message- > From: Anima [mailto:anima-boun...@ietf.org] On Behalf Of Brian E Carpenter > Sent: Monday, December 16, 2019 12:21 PM > To: Anima WG > Subject: Re: [Anima] I-D Action:

Re: [Anima] I-D Action: draft-liu-anima-grasp-distribution-06.txt

Hi Brian, Thanks for your comments! Since this new version proposed some protocol extensions, we really need review from GRASP perspective. Please see reply inline. > -Original Message- > From: Anima [mailto:anima-boun...@ietf.org] On Behalf Of Brian E Carpenter > Sent: Thursday, July

Re: [Anima] BRSKI over 802.11

Hi Michael, Eliot and all, A clarification question: it sounds like there are two approaches proposed, not sure I understood it correctly: Michael's proposal: there is a dedicated SSID, say "Anima", it is enabled by default, and there is no security. And that SSID can only do BRSKI, no other

Re: [Anima] Adoption call for draft-liu-anima-grasp-api-06, ends Dec. 12, 2017

Hi all, I support it as a co-author. Since GRASP is eventually used by applications (ASAs), the API is essential for ASA developers. Just like the socket interface, the GRASP API can provide some services to app layer. The services are discovery/Sync/Negotiation which would allow developers

[Anima] ANI Objectives-//RE: Calling new works and discussion

Hi Dear all, To response to the Chairs' calling, I'd like to firstly mention an existing work, draft-carpenter-anima-ani-objectives, which belongs to the first category as Sheng defined below: > Leveraging the Current ANI (GRASP, ACP & BRISK) It is very specific technical details (just like

Re: [Anima] Primary ANIMA agenda @ IETF 99, Prague, Czech

Hi Sheng and all, The agenda seems incomplete in the link below. But it is interesting that in another link it is complete: https://www.ietf.org/proceedings/99/agenda/agenda-99-anima-00 . I guess it's a bug of the ietf site? B.R. Bing From: Anima [mailto:anima-boun...@ietf.org] On Behalf Of

[Anima] RPL alternatives in ACP? (was: Regarding ACP routing protocol)

n non-IoT network scenarios. Any comments/eggs? :) B.R. Bing > -Original Message- > From: Anima [mailto:anima-boun...@ietf.org] On Behalf Of Liubing (Leo) > Sent: Tuesday, May 23, 2017 5:53 PM > To: Anima WG > Subject: [Anima] Regarding ACP routing protocol > >