Re: [karp] Time to wind up KARP

Uma Chunduri <> Tue, 27 May 2014 23:30 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 47CC21A0671 for <>; Tue, 27 May 2014 16:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id waK0n4PhpyJa for <>; Tue, 27 May 2014 16:30:52 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CDDDC1A02AF for <>; Tue, 27 May 2014 16:30:51 -0700 (PDT)
X-AuditID: c618062d-f79be6d000006b89-89-5384d011850e
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 66.72.27529.110D4835; Tue, 27 May 2014 19:49:05 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Tue, 27 May 2014 19:30:39 -0400
From: Uma Chunduri <>
To: "" <>, "" <>
Thread-Topic: [karp] Time to wind up KARP
Thread-Index: Ac90xe+dXuN2Do6kTKmgsjLTeo0OdgFPFhVw
Date: Tue, 27 May 2014 23:30:38 +0000
Message-ID: <>
References: <02ae01cf74c5$f62bd200$e2837600$>
In-Reply-To: <02ae01cf74c5$f62bd200$e2837600$>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyuXRPlK7ghZZggz9vrS1+9Nxgttj7bQ2j xfM5M1ksli+ezO7A4rFkyU8mjxWbVzJ6fLn8mS2AOYrLJiU1J7MstUjfLoEr4/W/PpaCTVIV yz9OZmxg/C/SxcjJISFgItHeMIcVwhaTuHBvPVsXIxeHkMBRRon/++cygiSEBJYzSkx4oA1i swnoSXyc+pMdxBYRCJJYP/sUmM0skCVx4sI1sEHCAhoSH/oeM0LUaEqsa3oJVMMBZBtJbGi3 BjFZBFQlFj0MAqngFfCV2Hy2lwVik5XE1LlXwaZwClhLnLqxkRnEZgQ67fupNUwQm8Qlbj2Z zwRxsoDEkj3nmSFsUYmXj/9BvaIosa9/OtRlOhILdn9ig7C1JZYtfM0MsVdQ4uTMJywTGMVm IRk7C0nLLCQts5C0LGBkWcXIUVqcWpabbmSwiREYP8ck2HR3MO55aXmIUYCDUYmHVyGpJViI NbGsuDL3EKM0B4uSOK/2zapgIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYxlLxU1LJvmnJT6 6vuDKaPI4svM7xph3y4v3Wy90+/mdJPe+cr2rQ3XaxR/pLr/v/03ZJO48Yfjpoweb145vzve PS9n/+n6pLTP7LGXF7yZHtfA0MnFL7ar+GwYl18jX+6xkPsTD5gL+XU/eTHtjuP0o107d3kU GaZIfFFs2VHzsu+lkOOnqnIlluKMREMt5qLiRAAmaWBIgAIAAA==
Cc: "" <>, "" <>
Subject: Re: [karp] Time to wind up KARP
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion list for key management for routing and transport protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 27 May 2014 23:30:54 -0000

Dear Adrian & Alia,

Please see comments in-line [Uma]:

Uma C.

-----Original Message-----
From: karp [] On Behalf Of Adrian Farrel
Sent: Wednesday, May 21, 2014 12:26 AM
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.

[Uma]: I guess, security work for relatively  new WGs in routing area (for e.g., NVO3, I2RS, SFC etc..) ought to be discussed in this mailing list.
              This will enable security experts in this group, who don't follow routing work groups regularly.
- The two remaining WG drafts will be completed as "AD Sponsored" with cross-checks to the ISIS and BFD working groups.

[Uma]: Thanks.  I co-author IS-IS draft and any further suggestion/action item for us in this regard will be helpful.

- 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

[Uma]: Could you please specify which particular draft you were talking about.

     - A home for management of KeyTables can also be found (e.g., NETMod)

[Uma]: Could you please specify which particular draft you were talking about.
I have posted a new version for this  ID,   and I feel this is very useful for KMP centric solution for AKM.
If you can specify the ID you were talking about, it would be useful.

- 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.


karp mailing list