Re: [karp] Closing KARP

"Adrian Farrel" <> Wed, 04 June 2014 19:30 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 55B121A033B for <>; Wed, 4 Jun 2014 12:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1sU7VEmEtLp9 for <>; Wed, 4 Jun 2014 12: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 5D9191A02A8 for <>; Wed, 4 Jun 2014 12:30:51 -0700 (PDT)
Received: from (localhost.localdomain []) by (8.13.8/8.13.8) with ESMTP id s54JUgAN004180; Wed, 4 Jun 2014 20:30:42 +0100
Received: from 950129200 ( []) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id s54JUfX3004159 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 4 Jun 2014 20:30:42 +0100
From: "Adrian Farrel" <>
To: "'Mahesh Jethanandani'" <>
Date: Wed, 4 Jun 2014 20:30:37 +0100
Message-ID: <086501cf802b$76f43a60$64dcaf20$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0866_01CF8033.D8BBAFA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac+AK3MUABKs7FhcQjaRaO6agcJ9cQ==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--24.452-10.0-31-10
X-imss-scan-details: No--24.452-10.0-31-10
X-TMASE-MatchedRID: pS5owHKhBO0NDmNqb6OmShes/RxhysDbLAnNohUyMa2638ZUY6gSdxEa gYlxo94POUYNXsr1n12+ajoomsCKvONMTcuWvx5285L5JHGOAXDaCn4DqCiXNuJsgXmCsctFrop xmZF4UD3vSTHlSbgM2QzLDqEyu1hQ1QwDBMM4Gey7vYqkCS0dL3+ogtHzaKWZk4cPqhCnOBG3DY GNlagpcAgrUzk34ys53OaIc5xACOrD11TnHAQ1PW0PWqD0pliRGSqdEmeD/nU06dhcpwNHEIZbN Fr3ThNDI1j68AwVJtWHViUtZ9Duft/VfsVgOrak3fn7n/ZHGqYhXHiVbGfuY//o4E70SZ2Yh8Uz juoP0V7Y4mcCOjnnT+UnCn5BOic/O6Fj0OJGfRnRXhA4ma+s3txOVRSUW4iEYHvy8ATgR+T0rkm G2TPGAtaGsc3CbJRZxUvk8kW7jQ7B6kugcU0FsOXP7JqXOmP+6Jj6zYvfFASw5aBPa7nICTxH8t KF9a4gCPnYMmIYXkfdL3pi9TCVtQRpZ0PAS0nmtT4jIeGRd/VBldmDYjwlppuSv4SfxhK37/+9s wuISRVYVA2Tj4cKiIcypU5vI8wyw1hXve9gEVCO0rt0LpQGeRSpYqhygmjp6ygMMToK892nhZyb KoFsXELduO9IO73n36y5gCD1lYkzG8Dg48sJ/vIVL3+KSNgwkTzAgHG5eNKgJH974mpbq6gTkLg TtTggIm6fKcuFyK8oR0K3DJ8mwtZXwwpvfhGVFlT/KggLyj0lWygvtTclwOKYpwtG+wHVRq7NaF miCIDOQf/S1XvtEAC/b4aTkuDFizFhECDuofCeAiCmPx4NwGmRqNBHmBve1kTfEkyaZdxFGCd0S 0NCshJA/WiCmlLA5J7mpKFUklLkKMmDThYc+wjBtep+LgrVWClYJu9r4yY=
Subject: Re: [karp] Closing 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: Wed, 04 Jun 2014 19:30:54 -0000

Hi Mahesh,
Do you mean ready for last call? It doesn't seem that the document had been adopted by the WG. And it seems to have expired a little while ago.
A very brief scan of the document suggests that the references are in a bit of a mess. You need to clean up the things that don't need to be referenced. Perhaps run idnits?
Conversely, I'm a bit surprised that your document doesn't reference RFC5920 or RFC6941.
Tell me whether this document focuses on MPLS-TE, or also covers GMPLS? What about MPLS-TP?
I suggest that the approach is...
- polish your document
- post a new revision
- decide whether you are MPLS-TE only or GMPLS and MPLS-TP as well
- approach the chairs of MPLS or CCAMP according to your decision
Oh, and consider sending a copy to the RSVP Directorate.
From: Mahesh Jethanandani [] 
Sent: 31 May 2014 16:01
Cc: <>rg>;;;
Subject: Re: [karp] Closing KARP
There is one other draft that was reviewed and ready for last call. draft-mahesh-karp-rsvp-te-analysis. How do you want to proceed on it?

Mahesh Jethanandani

On May 30, 2014, at 3:32 PM, "Adrian Farrel" <> wrote:
OK, thanks to those of you who have contacted me about the future of KARP work.

I will ask the Secretariat to close the working group forthwith, and keep the
mailing list open.

Is on the RFC Editor queue and has completed Auth48
Publication soon

The I-D has been refreshed and WG last call is complete.
The BFD working group has already reviewed the document.
Brian is working on a shepherd write-up and I will AD Sponsor the publication.

Document almost complete. 
Needs a final push and review by the ISIS WG.
I will AD sponsor it when it is ready.

Management plane solution to AKM
Sam has offered to work on something here.
I'm sure he would welcome help if anyone is willing.
We can easily find a home for this sort of work. I would start with the OPSAWG
but maybe it will belong in netmod.

Uma has recently posted a new revision.
This document can be advanced as AD sponsored when it is ready.

This document needs work.
I'll ask the PIM chairs to run with this in the PIM WG.

This document needs work.
I'll ask the CCAMP chairs to run with this in the CCAMP WG.

New work / other work:
- No new or existing work is "banned" or blocked...
  - Write your I-Ds and polish them
- This mailing list remains open for general discussions
- Specific work (for example analysis of protocols against the KARP
  guidelines) should be taken to protocol-owning working groups
- Work on TCP/AO for routing protocols (if anyone wishes to pursue it)
 needs to be distributed to the correct place. Some of it will be specific
 to enhancing BGP security and belongs in IDR or SIDR, some of it may
 be specific to other routing protocols and can be handled there. But
 obviously, work on TCP/AO must also involve the Security Area and
 (if it changes the protocol) the Transport Area. We'll handle these on
 a case-by-case basis as drafts are produced.

Finally, I want to thank you all, and especially the chairs, for the work done
by KARP.


karp mailing list