Hi Brian,
Thanks for sharing interesting incidents and reflecting on the role of ANIMA
technologies.
Reading the report, it seems the outage results from a series of indirectly
linked events
leading to isolation of a portion of the GCP network.
For the incident you refer here, how/where
Hello,
I'm a co-author of this draft.
I support its adoption as WG document.
Best regards,
Laurent
> -Original Message-
> From: Anima On Behalf Of Toerless Eckert
> Sent: Thursday, October 15, 2020 12:37
> To: Anima WG
> Cc: anima-cha...@ietf.org; Rob Wilton (rwilton)
> Subject:
Dear ANIMA WG Chairs,
We'd like to ask for a short slot on draft-carpenter-anima-asa-guidelines.
The main purpose is to present the status of the I-D (no change, stable
version) and ask for WG document adoption.
Best regards,
-Laurent
> -Original Message-
> From: Anima On Behalf Of
Hi Bria, All,
Re: https://tools.ietf.org/html/draft-carpenter-anima-asa-guidelines
As a co-author, I also believe we need to make a decision on the next step for
this document.
We have proposed options for content evolution in previous ANIMA meetings.
Maybe a call for adoption as WG document
> -Original Message-
> From: Anima On Behalf Of Michael Richardson
> Sent: Saturday, October 12, 2019 23:02
> To: anima@ietf.org
> Subject: Re: [Anima] Call for agenda ANIMA @ IETF 106, Singapore [ASAs]
>
>
> Brian E Carpenter wrote:
> > It seems time for the WG to discuss
> -Original Message-
> From: Anima On Behalf Of Toerless Eckert
> Sent: Friday, February 22, 2019 12:00
> To: Brian E Carpenter
> Cc: Michael Richardson ; anima@ietf.org
> Subject: Re: [Anima] Intent: -> NMRG -> ANIMA -> NMRG -> (ANIMA?)!) Re:
> proposed anima charter (was; Re: New
Just running some tests as I'm not receiving emails for IETF mailing lists.
-Laurent.
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
Hi Alex,
Thanks for your comments on draft-carpenter-anima-asa-guidelines.
If I get it correctly you raised the following points:
1. -better describe what ASA are: rather application or network service, and
better describe the border between the two and implications for ASA
Hello,
Sheng you mentioned two works we should liaise to, which could help getting
deployment experience.
Bing mentioned an ID but I cannot find it under the ANIMA related docs (not
T2TRG ones).
Could you share the pointers or contacts, please?
Thanks, Laurent.
Hello,
Does the need to explicitly distinguish ANIMA work from HOMENET work still exist
If not, then why not remove/forget about this possibly contentious terminology.
(the goal would be to avoid unnecessary difficulties for ANIMA documents
publication at IESG review or IETF last call stages).
Hello,
We are currently 8 "co-authors" for this draft.
My preferences, in priority order, are:
1) Michael as Editor, all other authors listed as authors, no
contributors.
2) Michael as Editor, all other authors listed as contributors.
Given how this document originated and has
Hello,
>
> Firstly, a global concern:
> This technique (and I suspect many automated prefix allocations where
> a device uses space, and then requests more) is likely (I think) to
> result in fragmentation of the address space - this will lead to more
> routing entries in the IGP, which may
Hello,
I think this work is of interest and should continue, either as an individual
or working group document.
Laurent.
-Original Message-
From: Anima [mailto:anima-boun...@ietf.org] On Behalf Of Diego R. Lopez
Sent: Tuesday, December 12, 2017 10:36 AM
To: Toerless Eckert
13 matches
Mail list logo
