Re: [karp] Time to wind up KARP

Hi Adrian,

draft-ietf-karp-bfd-analysis has finished the WG LC (this I think has been discussed in the BFD WG as well) and we're waiting for Brian to prepare a writeup. We can push it to the IESG as soon as the writeup is done.

Cheers, Manav

> -----Original Message-----
> From: karp [mailto:karp-bounces@ietf.org] On Behalf Of Adrian Farrel
> Sent: Wednesday, May 21, 2014 12:56 PM
> To: karp@ietf.org
> Cc: sec-ads@tools.ietf.org; rtg-ads@tools.ietf.org
> Subject: [karp] Time to wind up KARP
> 
> Hi KARP working group,
> 
> With RFC 7210 now published and draft-ietf-karp-ops-model having
> completed
> Auth48, the WG can justifiably claim to have delivered on significant
> parts of
> the charter.
> 
> The "next big thing" for the working group has been constant for a long
> time:
> AKM. However, as you know, there has been no movement on this despite a
> couple
> of I-Ds on the topic. In London there was a suggestion that there might
> be a
> "management plane" solution to AKM spanning multiple routing protocols,
> but when
> squeezed, there were not many people offering to do work on this, and
> no I-Ds or
> even emails have popped out in the 8 weeks since then.
> 
> The WG also has just two more drafts in hand.
>  - draft-ietf-karp-isis-analysis is pretty close to cooked
>  - draft-ietf-karp-bfd-analysis has expired, but is also close to
> cooked.
> 
> Of course, there are a number of active individual drafts in the pipe
> as well.
> 
> After discussion with the chairs and with Alia, and unless persuaded
> otherwise,
> I will close the KARP working group on 29th May.
> 
> We would handle remaining work as follows:
> 
> - There will not be a meeting in Toronto.
> - The KARP mailing list will remain open as a place to contact people
> about
> KARP-related work.
> - The two remaining WG drafts will be completed as "AD Sponsored" with
> cross-checks to the ISIS and BFD working groups.
> - Any new protocol analysis I-Ds will be taken to the appropriate
> protocol-owning working groups.
>      - The work mapping TCP-AO state to key tables can move to IDR
>      - A home for management of KeyTables can also be found (e.g.,
> NETMod)
> - If a group of people want to work on a management solution for AKM
> for routing
> protocols (or for any protocol) then the OPS, SEC, and RTG ADs will
> find a place
> for the work. (Write a draft, get some support, and talk to us.)
> - If a charterable body of work comes along (such as AKM within routing
> protocols) then we will charter or home the work as necessary.
> 
> Please think about this and comment to the list.
> 
> Thanks,
> Adrian
> 
> _______________________________________________
> karp mailing list
> karp@ietf.org
> https://www.ietf.org/mailman/listinfo/karp