Re: [karp] Time to wind up KARP

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 21 May 2014 09:22 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC1021A0315 for <karp@ietfa.amsl.com>; Wed, 21 May 2014 02:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 OCXoCbKgdBnn for <karp@ietfa.amsl.com>; Wed, 21 May 2014 02:22:32 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 824B21A031F for <karp@ietf.org>; Wed, 21 May 2014 02:22:32 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s4L9Lk0v025269; Wed, 21 May 2014 10:21:46 +0100
Received: from 950129200 ([217.206.228.219]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s4L9LjOC025243 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 21 May 2014 10:21:46 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Bhatia, Manav \(Manav\)'" <manav.bhatia@alcatel-lucent.com>
References: <02ae01cf74c5$f62bd200$e2837600$@olddog.co.uk> <20211F91F544D247976D84C5D778A4C32E60B5C3@SG70YWXCHMBA05.zap.alcatel-lucent.com>
In-Reply-To: <20211F91F544D247976D84C5D778A4C32E60B5C3@SG70YWXCHMBA05.zap.alcatel-lucent.com>
Date: Wed, 21 May 2014 10:21:44 +0100
Message-ID: <02da01cf74d6$15c77410$41565c30$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHiDpHgZAUAhlORqerV9hFV9EYNfwIjVdlimxR0AZA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.0.0.1014-20706.006
X-TM-AS-Result: No--29.479-10.0-31-10
X-imss-scan-details: No--29.479-10.0-31-10
X-TMASE-MatchedRID: xcONGPdDH5pK/2BqVYjLouYAh37ZsBDCt3aeg7g/usAutoY2UtFqGI1e cYQjcUBP45HLzdQc+35fwPs2uejPEGr4uS6vfh2t6Zzj+kMRBrZ+Mk6ACsw4JkX5hc8ioB2+kyG MOJyKxBG6bEpY1OwqaYP6ZmKxVHQjQHp6QyCfxJlCnGIuUMP0VfBkYT/50xzW47E6rstCUYvqOg IC+yJP2JGKBcj/nkbq5uXkSXTDIXQlO3FWVopgW4DTBcxjSxJQH181YDtIVaoj/BgXooqgw69AM 6N/Kp5dHopbK1iQa6xZu3RooavPofH17GX1hHxkuIwLnB3Aqp1Ojummt4nJ90y+1KMKBUT6k4Tr wZ+avU6czCJvSaLJUb/sbW8UfZ/nYqmUd3tOErXbH8WaUL9qjCH8kDR0dp2mEd+K6O5Nt53zb5k mgp405bfqHaErmu92gDLqnrRlXrY3zuRrgWxGGP7E6GNqs6ce3QfwsVk0UbslCGssfkpInQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/dYmewgfNN1u1Y73mu3KBCUW595k
Cc: karp@ietf.org
Subject: Re: [karp] Time to wind up KARP
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Discussion list for key management for routing and transport protocols <karp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/karp>, <mailto:karp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/karp/>
List-Post: <mailto:karp@ietf.org>
List-Help: <mailto:karp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/karp>, <mailto:karp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 May 2014 09:22:35 -0000

Hi,

Can you start the process by refreshing the I-D?

Thanks,
Adrian

> -----Original Message-----
> From: Bhatia, Manav (Manav) [mailto:manav.bhatia@alcatel-lucent.com]
> Sent: 21 May 2014 08:30
> To: adrian@olddog.co.uk; karp@ietf.org
> Cc: sec-ads@tools.ietf.org; rtg-ads@tools.ietf.org
> Subject: 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