From nobody Tue May 13 12:44:03 2014
Return-Path: <mjethanandani@gmail.com>
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 6B94A1A0195 for <karp@ietfa.amsl.com>; Tue, 13 May 2014 12:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 BpunPgfQ9_aL for <karp@ietfa.amsl.com>; Tue, 13 May 2014 12:43:58 -0700 (PDT)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 742471A013F for <karp@ietf.org>; Tue, 13 May 2014 12:43:58 -0700 (PDT)
Received: by mail-qg0-f46.google.com with SMTP id q108so1136470qgd.33 for <karp@ietf.org>; Tue, 13 May 2014 12:43:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LwCRm4cfVm34DFhC2zFa01cTq2Ti3wFwLW65/DSZKCo=; b=nwUq/w6U5RlLsumvJtGQ6DHMU4LwjihIO4WThVWNAYWC0f8Vtqnw8PYHZ/9GfvdRqY f0kKbSJVAzSLmzfxnDtLQCa+obu2aRcvYwzXEmS6FGD95WIiAytLshJq30+Cc484rHHX sG4KFJRnN+vbgr6rUJAGl4Myfr7WDu7vk+QJy0DNz0e5tR7Yj5o+lnpswQHhUzHBWlz2 PHsnW5uNiaedXQgeROrMfLTXB7QZP9aJ4xSEJIWV+XFkD1WBZyIl1TaxgflNLqbe9WE1 JefMB46iZsDWcC1AabQj+ws+B5uDdDmKBHiFQ+hTn9p4IIWfXX5/vRjqG6MsLrnH/Ky9 teTQ==
MIME-Version: 1.0
X-Received: by 10.140.31.196 with SMTP id f62mr48026586qgf.59.1400010231983; Tue, 13 May 2014 12:43:51 -0700 (PDT)
Received: by 10.140.19.136 with HTTP; Tue, 13 May 2014 12:43:51 -0700 (PDT)
In-Reply-To: <1A30FD57-D593-4762-AE20-8E4B42168704@cisco.com>
References: <1A30FD57-D593-4762-AE20-8E4B42168704@cisco.com>
Date: Tue, 13 May 2014 12:43:51 -0700
Message-ID: <CAAchPMuVssgC7AUoK9EZ0ZpqQpJt-N3WDm0jd3TVURmSipFBTA@mail.gmail.com>
From: Mahesh Jethanandani <mjethanandani@gmail.com>
To: Brian Weis <bew@cisco.com>
Content-Type: multipart/alternative; boundary=001a113a65308f3b6b04f94d485c
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/J7nS13cB9gFdKEnBtfhzcC6RrbE
Cc: "<karp@ietf.org>" <karp@ietf.org>
Subject: Re: [karp] IETF 88 KARP WG Minutes
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Tue, 13 May 2014 19:44:00 -0000

--001a113a65308f3b6b04f94d485c
Content-Type: text/plain; charset=UTF-8

Back in the 88th IETF and in the minutes that were sent out then, it was
recorded that draft-mahesh-karp-rsvp-te-analysis should be ready for WG
adoption.

Any idea on when that can be made to happen?


On Tue, Dec 24, 2013 at 5:42 PM, Brian Weis <bew@cisco.com> wrote:

> Greetings,
>
> The KARP WG minutes from the Vancouver meeting have been posted. Many
> thanks to Tero Kivinen for providing them.
>         <http://www.ietf.org/proceedings/88/minutes/minutes-88-karp>
> Corrections may be sent to the list or to the chairs <
> karp-chairs@tools.ietf.org>.
>
> Joel & Brian
> _______________________________________________
> karp mailing list
> karp@ietf.org
> https://www.ietf.org/mailman/listinfo/karp
>



-- 
Mahesh Jethanandani
mjethanandani@gmail.com

--001a113a65308f3b6b04f94d485c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Back in the 88th IETF and in the minutes that were sent ou=
t then, it was recorded that draft-mahesh-karp-rsvp-te-analysis should be r=
eady for WG adoption.<div><br></div><div>Any idea on when that can be made =
to happen?</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue,=
 Dec 24, 2013 at 5:42 PM, Brian Weis <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:bew@cisco.com" target=3D"_blank">bew@cisco.com</a>&gt;</span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
Greetings,<br>
<br>
The KARP WG minutes from the Vancouver meeting have been posted. Many thank=
s to Tero Kivinen for providing them.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;<a href=3D"http://www.ietf.org/proceedings/=
88/minutes/minutes-88-karp" target=3D"_blank">http://www.ietf.org/proceedin=
gs/88/minutes/minutes-88-karp</a>&gt;<br>
Corrections may be sent to the list or to the chairs &lt;<a href=3D"mailto:=
karp-chairs@tools.ietf.org">karp-chairs@tools.ietf.org</a>&gt;.<br>
<br>
Joel &amp; Brian<br>
_______________________________________________<br>
karp mailing list<br>
<a href=3D"mailto:karp@ietf.org">karp@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/karp" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/karp</a><br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div dir=3D"=
ltr"><div>Mahesh Jethanandani<br></div><a href=3D"mailto:mjethanandani@gmai=
l.com" target=3D"_blank">mjethanandani@gmail.com</a><br></div>
</div>

--001a113a65308f3b6b04f94d485c--


From nobody Fri May 16 10:06:11 2014
Return-Path: <jmh@joelhalpern.com>
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 BDDE31A02CC; Fri, 16 May 2014 10:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 IJHo6_IDlC4D; Fri, 16 May 2014 10:06:09 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F113A1A02AE; Fri, 16 May 2014 10:06:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id B1AB5141E34; Fri, 16 May 2014 10:06:01 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-10.clppva.east.verizon.net [70.106.135.10]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id D7DC3141E33; Fri, 16 May 2014 10:06:00 -0700 (PDT)
Message-ID: <53764577.6070502@joelhalpern.com>
Date: Fri, 16 May 2014 13:05:59 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "lisp@ietf.org" <lisp@ietf.org>, "karp@ietf.org" <karp@ietf.org>
References: <9913.1400250296@sandelman.ca>
In-Reply-To: <9913.1400250296@sandelman.ca>
X-Forwarded-Message-Id: <9913.1400250296@sandelman.ca>
Content-Type: multipart/mixed; boundary="------------090905030802060406060007"
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/HsFSTX32Y4I0Pcxx1Ku30Qwt_o4
Subject: [karp] Fwd: NomCom 2014-2015 Call for Volunteers
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Fri, 16 May 2014 17:06:11 -0000

This is a multi-part message in MIME format.
--------------090905030802060406060007
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Please consider volunteering for the IETF nominating committee.
Broad community participation is important for our process.

Thank you,
Joel


-------- Original Message --------
Subject: NomCom 2014-2015 Call for Volunteers
Date: Fri, 16 May 2014 10:24:56 -0400
From: Michael Richardson <mcr+ietf@sandelman.ca>
Reply-To: nomcom-chair-2014@ietf.org
To: ietf@ietf.org


{I have to post using my subscribed address. Appologies for duplicates}

The IETF nominating committee (nomcom) process for 2014-15 has begun. The
IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
and the IESG (including IETF Chair).

Ten voting members for the nomcom are selected in a verifiably random
way from a pool of volunteers. The more volunteers, the better chance we 
have of
choosing a random yet representative cross section of the IETF population.

Let's break the 200 volunteer mark again this year!

The details of the operation of the nomcom can be found in RFC 3777,
and BCP10/RFC3797 details the selection algorithm.

Volunteers must have attended 3 of the past 5 IETF meetings.  As 
specified in
RFC 3777, that means three out of the five past meetings up to the time this
email announcement goes out to start the solicitation of volunteers.
The five meetings out of which you must have attended *three*
are IETF 85(Atlanta),      \
          86(Orlando),       \
          87(Berlin),         *** ANY THREE!
          88(Vancouver),     /
          89(London)        /

If you qualify, please volunteer.   However, much as we want this, 
before you
decide to volunteer, please be sure you are willing to forgo appointment
to any of the positions for which this nomcom is responsible.

The list of people and posts whose terms end with the March 2015 IETF
meeting, and thus the positions for which this nomcom is responsible, are

IAOC:
To be confirmed

IAB:
Joel Halpern
Russ Housley
Eliot Lear
Xing Li
Andrew Sullivan
Dave Thaler

IESG:
Pete Resnick (Applications)
Ted Lemon (Internet)
Joel Jaeggli (Operations and Management)
Richard Barnes (RAI)
Adrian Farrel* (Routing)
Stephen Farrell (Security)
Spencer Dawkins (Transport)
Jari Arkko (Gen)

(names with * have publically indicated they will not serve another term)

The primary activity for this nomcom will begin in July 2014 and should be
completed in January 2015.   The nomcom will have regularly scheduled
conference calls to ensure progress. (We might dogfood WebRTC)
There will be activities to collect requirements from the community, review
candidate questionnaires, review feedback from community members about
candidates, and talk to candidates.

Thus, being a nomcom member does require some time commitment; but it is 
also
a very rewarding experience.

It is very important that you be able to attend IETF91 to conduct 
interviews.
Being at IETF90 is useful for training.  Being at IETF92 is not essential.

Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours)
June 22, 2013, as follows:

To: nomcom-chair-2014@ietf.org
Subject: Nomcom 2014-15 Volunteer

Please include the following information in the email body:

  <Your Full Name>
     // First/Given Name followed by Last/Family Name
     // matching how you enter it in the IETF Registration Form)

  <Current Primary Affiliation>
     // Typically what goes in the Company field
     // in the IETF Registration Form
[<All email addresses used to register for the past 5 IETF meetings>]
  <Preferred email address>
  <Telephone number>
     // For confirmation if selected

You should expect an email response from me within 3 business days stating
whether or not you are qualified.  If you don't receive this response,
please re-send your email with the tag "RESEND"" added to the subject line.

If you are not yet sure if you would like to volunteer, please consider
that nomcom members play a very important role in shaping the leadership
of the IETF.  Questions by email or voice are welcome.
Volunteering for the nomcom is a great way to contribute to the IETF!

You can find a detailed timeline on the nomcom web site at:
     https://datatracker.ietf.org/nomcom/2014/

I will be publishing a more detailed target timetable, as well as details
of the randomness seeds to be used for the RFC 3797 selection process,
within the next couple weeks.

Thank you!
Michael Richardson
mcr+nomcom@sandelman.ca
nomcom-chair-2014@ietf.org





--------------090905030802060406060007
Content-Type: application/pgp-signature;
 name="Attached Message Part"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Attached Message Part"

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjEuNC4xMiAo
R05VL0xpbnV4KQoKaVFFVkF3VUJVM1lmdDRDTGNQdmQwTjFsQVFLNEVnZi9WZmxWbmdiTHU3
NEhpai83WUtDbGVLcG8ybWZUVi90NAplcWhacndkWkh1SlhrbTdlZWEzbk5TdG5jQXRiY0dD
R1hUZXY1WThEMkFMdkJtamdUZlpRano0YXNkcjVNU3BnCkZ3aEM1ZVNSRVJFbVpiSU5mbjdY
L2NtOHZFc1RpWjFDbndPUUdHMWxPVjFUQ1Q4TWg0aEFNYnZpZWJtRHdOdFkKTWVmU1VkV21S
YkF4TkdqbDJmQkRoeDRvV3lNaDNaa1hyWnNwMlNHMzloUWoweFZUcGEvdXJvMGRqNFB3Q0NK
SgpjTXFnbUVKd1V1VXpLc3RCdzY4U3BsT3B5ZUIreDZxZ1QwcmVaK0Z2RXhtbk8rZlhDdDRI
c25yRG9DQkREckp4CmdJQVBEaTVsdVpmSndzM1pxbmhJLzNoVTFNaHVpT0dickhRRkpoYURt
aiswTk9YbzNXbkR2dz09Cj1PUHM3Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo=
--------------090905030802060406060007--


From nobody Wed May 21 00:26:29 2014
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 7BDF81A0647 for <karp@ietfa.amsl.com>; Wed, 21 May 2014 00:26:26 -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 Cp935SKDLnGl for <karp@ietfa.amsl.com>; Wed, 21 May 2014 00:26:24 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72D1A1A0469 for <karp@ietf.org>; Wed, 21 May 2014 00:26:24 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s4L7QMVB005743; Wed, 21 May 2014 08:26:22 +0100
Received: from 950129200 ([217.206.228.219]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s4L7QLJ3005730 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 21 May 2014 08:26:21 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <karp@ietf.org>
Date: Wed, 21 May 2014 08:26:19 +0100
Message-ID: <02ae01cf74c5$f62bd200$e2837600$@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: Ac90xe+dXuN2Do6kTKmgsjLTeo0Odg==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20706.005
X-TM-AS-Result: No--17.563-10.0-31-10
X-imss-scan-details: No--17.563-10.0-31-10
X-TMASE-MatchedRID: LoYlyWOcz0NZgr1juo7z8KIjfGE5qvnLoddeo3DnwAtxV1qk8iqvqBEa gYlxo94PpLONrl4XYw3i7+zLvZ02QXOAMSqhBqB6fuyIS1ZjfrsZKp0SZ4P+dZM5bdP2sROgfdi +0/fshTj2OR+tLNhMf9rkLDt5TjPxq4TpBaxtJCcpa6LJktEjgNB43gDaHridr0ubZBNmRTK9ao +3x8LcxgRX9XoWT0H/YEBHGpRSkeg/mJEvNFL+dWgws6g0ewz22VnJ5DdrdqMcZFsYO/SuCOuXj zv9ldN+HT9iIIGMqIYVqzct6xmDyWKplHd7ThK12x/FmlC/aow6En2bnefhoApcq1+LTpsUo8WM kQWv6iV95l0nVeyiuDrm2CwlZwVRvECLuM+h4RB+3BndfXUhXQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/7ZgHb2EXZqw_fF58QESfHSayAxY
Cc: sec-ads@tools.ietf.org, rtg-ads@tools.ietf.org
Subject: [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 07:26:26 -0000

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


From nobody Wed May 21 00:30:17 2014
Return-Path: <manav.bhatia@alcatel-lucent.com>
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 76ED21A0484 for <karp@ietfa.amsl.com>; Wed, 21 May 2014 00:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 FdpkOoob9_lZ for <karp@ietfa.amsl.com>; Wed, 21 May 2014 00:30:13 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDFFF1A0469 for <karp@ietf.org>; Wed, 21 May 2014 00:30:13 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s4L7U6Tt003833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 May 2014 02:30:07 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id s4L7U4MK028419 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 21 May 2014 03:30:04 -0400
Received: from SG70YWXCHHUB03.zap.alcatel-lucent.com (135.253.2.37) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 21 May 2014 03:30:04 -0400
Received: from SG70YWXCHMBA05.zap.alcatel-lucent.com ([169.254.5.212]) by SG70YWXCHHUB03.zap.alcatel-lucent.com ([135.253.2.37]) with mapi id 14.02.0328.009; Wed, 21 May 2014 15:29:53 +0800
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "karp@ietf.org" <karp@ietf.org>
Thread-Topic: [karp] Time to wind up KARP
Thread-Index: Ac90xe+dXuN2Do6kTKmgsjLTeo0OdgAAD1jg
Date: Wed, 21 May 2014 07:29:52 +0000
Message-ID: <20211F91F544D247976D84C5D778A4C32E60B5C3@SG70YWXCHMBA05.zap.alcatel-lucent.com>
References: <02ae01cf74c5$f62bd200$e2837600$@olddog.co.uk>
In-Reply-To: <02ae01cf74c5$f62bd200$e2837600$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.253.19.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/I8EoLu8NC8fzkirUmeE3P3kpd84
Cc: "sec-ads@tools.ietf.org" <sec-ads@tools.ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
Subject: Re: [karp] Time to wind up KARP
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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 07:30:15 -0000

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 w=
riteup. 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
>=20
> Hi KARP working group,
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> Of course, there are a number of active individual drafts in the pipe
> as well.
>=20
> After discussion with the chairs and with Alia, and unless persuaded
> otherwise,
> I will close the KARP working group on 29th May.
>=20
> We would handle remaining work as follows:
>=20
> - 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.
>=20
> Please think about this and comment to the list.
>=20
> Thanks,
> Adrian
>=20
> _______________________________________________
> karp mailing list
> karp@ietf.org
> https://www.ietf.org/mailman/listinfo/karp


From nobody Wed May 21 02:22:37 2014
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


From nobody Wed May 21 04:45:58 2014
Return-Path: <jhaas@slice.pfrc.org>
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 D62121A033C for <karp@ietfa.amsl.com>; Wed, 21 May 2014 04:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level: 
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 LjaABGqAfDWY for <karp@ietfa.amsl.com>; Wed, 21 May 2014 04:45:56 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id E91EE1A0314 for <karp@ietf.org>; Wed, 21 May 2014 04:45:55 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id E74EEC26A; Wed, 21 May 2014 07:45:54 -0400 (EDT)
Date: Wed, 21 May 2014 07:45:54 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
Message-ID: <20140521114554.GA5675@pfrc>
References: <02ae01cf74c5$f62bd200$e2837600$@olddog.co.uk> <20211F91F544D247976D84C5D778A4C32E60B5C3@SG70YWXCHMBA05.zap.alcatel-lucent.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20211F91F544D247976D84C5D778A4C32E60B5C3@SG70YWXCHMBA05.zap.alcatel-lucent.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/HjY5fDH_KidYi8807Ckb5iLWq54
Cc: "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, "sec-ads@tools.ietf.org" <sec-ads@tools.ietf.org>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [karp] Time to wind up KARP
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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 11:45:57 -0000

On Wed, May 21, 2014 at 07:29:52AM +0000, Bhatia, Manav (Manav) wrote:
> 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.

I also reviewed the BFD karp analysis draft and considered it of good
quality.  

-- Jeff


From nobody Thu May 22 05:52:32 2014
Return-Path: <hartmans@mit.edu>
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 A9D031A0020 for <karp@ietfa.amsl.com>; Thu, 22 May 2014 05:52:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.214
X-Spam-Level: 
X-Spam-Status: No, score=-0.214 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_SOFTFAIL=0.665] autolearn=no
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 96oglRuN-5Tt for <karp@ietfa.amsl.com>; Thu, 22 May 2014 05:52:26 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B7591A001A for <karp@ietf.org>; Thu, 22 May 2014 05:52:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id EB32F20704; Thu, 22 May 2014 08:50:23 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQVOMiA_f6tN; Thu, 22 May 2014 08:50:18 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-50-177-27-27.hsd1.ma.comcast.net [50.177.27.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 22 May 2014 08:50:18 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 89330804C9; Thu, 22 May 2014 08:52:15 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
References: <02ae01cf74c5$f62bd200$e2837600$@olddog.co.uk> <20211F91F544D247976D84C5D778A4C32E60B5C3@SG70YWXCHMBA05.zap.alcatel-lucent.com> <02da01cf74d6$15c77410$41565c30$@olddog.co.uk>
"To: adrian@olddog.co.uk
Date: Thu, 22 May 2014 08:52:15 -0400
In-Reply-To: <02da01cf74d6$15c77410$41565c30$@olddog.co.uk> (Adrian Farrel's message of "Wed, 21 May 2014 10:21:44 +0100")
Message-ID: <tsloayqj7r4.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/u93iP7Mj4uXFzv2xxBVD2xVTq_s
Cc: mrw@painless-security.com, karp@ietf.org
Subject: Re: [karp] Time to wind up KARP
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Thu, 22 May 2014 12:52:31 -0000

Dacheng Zhang, Margaret wasserman and I are happy to work on a
management plane solution to  AKM.
We'd be happy to get a draft by the next IETF, although the first draft
probably wouldn't be complete.


Is there enough interest that this work could be reviewed if we did it?
Is it valuable enough for us to go work on an initial draft?


From nobody Thu May 22 22:52:33 2014
Return-Path: <internet-drafts@ietf.org>
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 E8FF71A0383; Thu, 22 May 2014 22:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 kp6FRw7X4T94; Thu, 22 May 2014 22:52:29 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 85F891A0385; Thu, 22 May 2014 22:52:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140523055229.11556.98731.idtracker@ietfa.amsl.com>
Date: Thu, 22 May 2014 22:52:29 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/NRpaRQnSp2pWW61R9uhLctuqzIU
Cc: karp@ietf.org
Subject: [karp] I-D Action: draft-ietf-karp-bfd-analysis-02.txt
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 23 May 2014 05:52:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Keying and Authentication for Routing Protocols Working Group of the IETF.

        Title           : Analysis of Bidirectional Forwarding Detection (BFD) Security According to KARP Design Guide
        Authors         : Manav Bhatia
                          Dacheng Zhang
                          Mahesh Jethanandani
	Filename        : draft-ietf-karp-bfd-analysis-02.txt
	Pages           : 8
	Date            : 2014-05-22

Abstract:
   This document analyzes the Bidirectional Forwarding Detection
   protocol (BFD) according to the guidelines set forth in section 4.2
   of KARP Design Guidelines [RFC6518].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-karp-bfd-analysis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-karp-bfd-analysis-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-karp-bfd-analysis-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu May 22 22:56:23 2014
Return-Path: <manav.bhatia@alcatel-lucent.com>
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 B9D471A0380 for <karp@ietfa.amsl.com>; Thu, 22 May 2014 22:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 qKlPrYoGaWFY for <karp@ietfa.amsl.com>; Thu, 22 May 2014 22:56:19 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 350E01A0383 for <karp@ietf.org>; Thu, 22 May 2014 22:56:19 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s4N5uB4o004700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 23 May 2014 00:56:12 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id s4N5uAnN018104 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 23 May 2014 01:56:11 -0400
Received: from SG70XWXCHHUB01.zap.alcatel-lucent.com (135.253.2.46) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 23 May 2014 01:56:10 -0400
Received: from SG70YWXCHMBA06.zap.alcatel-lucent.com ([169.254.6.138]) by SG70XWXCHHUB01.zap.alcatel-lucent.com ([135.253.2.46]) with mapi id 14.02.0247.003; Fri, 23 May 2014 13:56:09 +0800
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Thread-Topic: [karp] Time to wind up KARP
Thread-Index: Ac90xe+dXuN2Do6kTKmgsjLTeo0OdgAAD1jg//+ZswD//JClsA==
Date: Fri, 23 May 2014 05:56:08 +0000
Message-ID: <20211F91F544D247976D84C5D778A4C32E615E96@SG70YWXCHMBA06.zap.alcatel-lucent.com>
References: <02ae01cf74c5$f62bd200$e2837600$@olddog.co.uk> <20211F91F544D247976D84C5D778A4C32E60B5C3@SG70YWXCHMBA05.zap.alcatel-lucent.com> <02da01cf74d6$15c77410$41565c30$@olddog.co.uk>
In-Reply-To: <02da01cf74d6$15c77410$41565c30$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.253.19.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/ZI8aNRlQOxeADebUKOcjhCZ2U04
Cc: Jeff Haas <jhaas@juniper.net>, "karp@ietf.org" <karp@ietf.org>
Subject: Re: [karp] Time to wind up KARP
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Fri, 23 May 2014 05:56:21 -0000

Hi Adrian,

Its done.

The new version is here:
http://www.ietf.org/internet-drafts/draft-ietf-karp-bfd-analysis-02.txt

Cheers, Manav

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Wednesday, May 21, 2014 2:52 PM
> To: Bhatia, Manav (Manav)
> Cc: karp@ietf.org
> Subject: RE: [karp] Time to wind up KARP
>=20
> Hi,
>=20
> Can you start the process by refreshing the I-D?
>=20
> Thanks,
> Adrian
>=20
> > -----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


From nobody Tue May 27 16:30:55 2014
Return-Path: <uma.chunduri@ericsson.com>
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 47CC21A0671 for <karp@ietfa.amsl.com>; Tue, 27 May 2014 16:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id waK0n4PhpyJa for <karp@ietfa.amsl.com>; Tue, 27 May 2014 16:30:52 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDDDC1A02AF for <karp@ietf.org>; Tue, 27 May 2014 16:30:51 -0700 (PDT)
X-AuditID: c618062d-f79be6d000006b89-89-5384d011850e
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 66.72.27529.110D4835; Tue, 27 May 2014 19:49:05 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.03.0174.001; Tue, 27 May 2014 19:30:39 -0400
From: Uma Chunduri <uma.chunduri@ericsson.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "karp@ietf.org" <karp@ietf.org>
Thread-Topic: [karp] Time to wind up KARP
Thread-Index: Ac90xe+dXuN2Do6kTKmgsjLTeo0OdgFPFhVw
Date: Tue, 27 May 2014 23:30:38 +0000
Message-ID: <1B502206DFA0C544B7A60469152008633F2B304A@eusaamb105.ericsson.se>
References: <02ae01cf74c5$f62bd200$e2837600$@olddog.co.uk>
In-Reply-To: <02ae01cf74c5$f62bd200$e2837600$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
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==
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/Ju9pCzWgcRF2WzuPviTf7qcezgU
Cc: "sec-ads@tools.ietf.org" <sec-ads@tools.ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
Subject: Re: [karp] Time to wind up KARP
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Tue, 27 May 2014 23:30:54 -0000

Dear Adrian & Alia,

Please see comments in-line [Uma]:

--
Uma C.


-----Original Message-----
From: karp [mailto:karp-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Wednesday, May 21, 2014 12:26 AM
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 tim=
e:
AKM. However, as you know, there has been no movement on this despite a cou=
ple 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 protocol=
s, but when squeezed, there were not many people offering to do work on thi=
s, 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 we=
ll.

After discussion with the chairs and with Alia, and unless persuaded otherw=
ise, 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 fo=
llow routing work groups regularly.
=20
- The two remaining WG drafts will be completed as "AD Sponsored" with cros=
s-checks to the ISIS and BFD working groups.

[Uma]: Thanks.  I co-author IS-IS draft and any further suggestion/action i=
tem 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 abo=
ut.

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


[Uma]: Could you please specify which particular draft you were talking abo=
ut.
I have posted a new version for this  ID, http://datatracker.ietf.org/doc/d=
raft-chunduri-karp-kmp-router-fingerprints/   and I feel this is very usefu=
l 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 ro=
uting protocols (or for any protocol) then the OPS, SEC, and RTG ADs will f=
ind 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


From nobody Fri May 30 15:32:49 2014
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 620C11A064A for <karp@ietfa.amsl.com>; Fri, 30 May 2014 15:32:47 -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 bLjMjnaoq5UG for <karp@ietfa.amsl.com>; Fri, 30 May 2014 15:32:45 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 381DE1A0262 for <karp@ietf.org>; Fri, 30 May 2014 15:32:45 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s4UMWccJ011908; Fri, 30 May 2014 23:32:38 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s4UMWbdL011893 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 30 May 2014 23:32:38 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <karp@ietf.org>
Date: Fri, 30 May 2014 23:32:37 +0100
Message-ID: <039901cf7c57$0f9a8ea0$2ecfabe0$@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: Ac98Vw2tLJYNyJVQQHWbiH9TlqnuVQ==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20728.000
X-TM-AS-Result: No--15.317-10.0-31-10
X-imss-scan-details: No--15.317-10.0-31-10
X-TMASE-MatchedRID: arU9O/tsd00hvnLuzo4LTFu4M/xm4KZeXfZY2uc9ofYAIXlMppp3X4Zb NFr3ThNDI1j68AwVJtWHViUtZ9Duft/VfsVgOrakU+OjsPhIWDhA8JZETQujwjhgoAzehG32cUP QjSOUQN2yJZUU2uQ2m/6sJ3Vn4hFM7sOH2+VDrlVCnGIuUMP0VXOKOUMFh4P8Vz8J52OVy+S7Jy GQsl8KJ5X4lYa1QF/4tiRXYRqWr+slHrWFxb39ONFeEDiZr6ze3E5VFJRbiIT7I1hjCeCvFiTD5 Z6o6ig5MsvMh/8C+Dbl1WOr70Uc39qoygGFfC1GikPqVDA/EGvzWqWqi0pBARxkWxg79K4IxDjz QlDvmKwvQLdglQ2eCn88u7KwgTtzqOCArAiC12kdxBAG5/hkW2Wuy5Lm0L4/erp1WCSUvAYLxuG a5n0CeuLzNWBegCW2XC3N7C7YzrfkwjHXXC/4I5BlLa6MK1y4
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/ZtexxPNJ4xHg-g6BLiMfeGNx9FI
Cc: isis-chairs@tools.ietf.org, pim-chairs@tools.ietf.org, ccamp-chairs@tools.ietf.org
Subject: [karp] Closing 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: Fri, 30 May 2014 22:32:47 -0000

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.

draft-ietf-karp-ops-model
Is on the RFC Editor queue and has completed Auth48
Publication soon

draft-ietf-karp-bfd-analysis
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.

draft-ietf-karp-isis-analysis
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.

draft-chunduri-karp-kmp-router-fingerprints
Uma has recently posted a new revision.
This document can be advanced as AD sponsored when it is ready.

draft-bhatia-karp-pim-gap-analysis
This document needs work.
I'll ask the PIM chairs to run with this in the PIM WG.

draft-mahesh-karp-lmp-analysis
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.

Thanks,
Adrian


From nobody Fri May 30 16:06:15 2014
Return-Path: <iesg-secretary@ietf.org>
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 ED8001A0293; Fri, 30 May 2014 16:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 GUvvMzz6I2dc; Fri, 30 May 2014 16:06:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 330271A052E; Fri, 30 May 2014 16:06:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140530230609.6238.53855.idtracker@ietfa.amsl.com>
Date: Fri, 30 May 2014 16:06:09 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/UHm2G8GbqhKkPRyzyHamimwc2C0
Cc: karp@ietf.org
Subject: [karp] WG Action: Conclusion of Keying and Authentication for Routing Protocols (karp)
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
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: Fri, 30 May 2014 23:06:12 -0000

The Keying and Authentication for Routing Protocols (karp) working group 
in the Routing Area has concluded. The IESG contact persons are Adrian 
Farrel and Alia Atlas.

The mailing list will remain open.


From nobody Sat May 31 08:01:25 2014
Return-Path: <mjethanandani@gmail.com>
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 B8A7D1A08FA for <karp@ietfa.amsl.com>; Sat, 31 May 2014 08:01:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] 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 bCa--r74fdK8 for <karp@ietfa.amsl.com>; Sat, 31 May 2014 08:01:20 -0700 (PDT)
Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7BA21A08DD for <karp@ietf.org>; Sat, 31 May 2014 08:01:20 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id b6so2570976yha.32 for <karp@ietf.org>; Sat, 31 May 2014 08:01:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=E42dQRsZLA266eRP7AtGk0vOjpAQFE2hfSYSX+GFp9Q=; b=bXMoHxbf1Ye8RcOmkdEA11NCK1uyGmGrTJXFM0pw2N1zQgSKvio0xaK1CATIm5D1bj Olpvw7lGf6XBq1IGrmEN9Kq82yPtOAGseCAK6k4L3pQIOcrA15TNcYURUW0UxJLEfdyP To48plAGs6cXvkqMmSA322G9uenLH/o7ODCQoOrtmaETL9ckVbQ5+qBTaPMJPz28bwEg 8IL+OAO2ab1pHvpOGiah6VNd2AO4icUxSE11p1TkxXi+8+TJqJsIjPLwJ7N0VRLG4tf1 0rlOQLjY84fD638inenS/NMSqQOCP4RAEFyEujITGTJAqbxk3Wiq0MLRrFSBX42bMQ6C ZFxg==
X-Received: by 10.236.165.199 with SMTP id e47mr32891658yhl.12.1401548475761;  Sat, 31 May 2014 08:01:15 -0700 (PDT)
Received: from [192.168.1.108] (108-247-124-220.lightspeed.sntcca.sbcglobal.net. [108.247.124.220]) by mx.google.com with ESMTPSA id k50sm11324478yhc.21.2014.05.31.08.01.14 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 31 May 2014 08:01:15 -0700 (PDT)
References: <039901cf7c57$0f9a8ea0$2ecfabe0$@olddog.co.uk>
Mime-Version: 1.0 (1.0)
In-Reply-To: <039901cf7c57$0f9a8ea0$2ecfabe0$@olddog.co.uk>
Content-Type: multipart/alternative; boundary=Apple-Mail-B196FF17-B3EB-4052-8C0E-5EC521CF5D9A
Content-Transfer-Encoding: 7bit
Message-Id: <86F12B35-B569-4C8C-86C8-859BF259CB2F@gmail.com>
X-Mailer: iPad Mail (10B329)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Date: Sat, 31 May 2014 08:01:15 -0700
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/yrpUQk4I1sOgeXtoaL-H89qJESk
Cc: "isis-chairs@tools.ietf.org" <isis-chairs@tools.ietf.org>, "pim-chairs@tools.ietf.org" <pim-chairs@tools.ietf.org>, "ccamp-chairs@tools.ietf.org" <ccamp-chairs@tools.ietf.org>, "<karp@ietf.org>" <karp@ietf.org>
Subject: Re: [karp] Closing KARP
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Sat, 31 May 2014 15:01:22 -0000

--Apple-Mail-B196FF17-B3EB-4052-8C0E-5EC521CF5D9A
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Adrian,

There is one other draft that was reviewed and ready for last call. draft-ma=
hesh-karp-rsvp-te-analysis. How do you want to proceed on it?

Mahesh Jethanandani
mjethanandani@gmail.com

On May 30, 2014, at 3:32 PM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

> OK, thanks to those of you who have contacted me about the future of KARP w=
ork.
>=20
> I will ask the Secretariat to close the working group forthwith, and keep t=
he
> mailing list open.
>=20
> draft-ietf-karp-ops-model
> Is on the RFC Editor queue and has completed Auth48
> Publication soon
>=20
> draft-ietf-karp-bfd-analysis
> 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 publicat=
ion.
>=20
> draft-ietf-karp-isis-analysis
> Document almost complete.=20
> Needs a final push and review by the ISIS WG.
> I will AD sponsor it when it is ready.
>=20
> 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 OP=
SAWG
> but maybe it will belong in netmod.
>=20
> draft-chunduri-karp-kmp-router-fingerprints
> Uma has recently posted a new revision.
> This document can be advanced as AD sponsored when it is ready.
>=20
> draft-bhatia-karp-pim-gap-analysis
> This document needs work.
> I'll ask the PIM chairs to run with this in the PIM WG.
>=20
> draft-mahesh-karp-lmp-analysis
> This document needs work.
> I'll ask the CCAMP chairs to run with this in the CCAMP WG.
>=20
> 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.
>=20
> Finally, I want to thank you all, and especially the chairs, for the work d=
one
> by KARP.
>=20
> Thanks,
> Adrian
>=20
> _______________________________________________
> karp mailing list
> karp@ietf.org
> https://www.ietf.org/mailman/listinfo/karp

--Apple-Mail-B196FF17-B3EB-4052-8C0E-5EC521CF5D9A
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Adrian,</div><div><br></div><div>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?<br><br><b style=3D"=
-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition=
-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color:=
 rgba(77, 128, 180, 0.230469); ">Mahesh Jethanandani</b><div><span style=3D"=
-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition=
-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color:=
 rgba(77, 128, 180, 0.230469);"><a href=3D"mailto:mjethanandani@gmail.com">m=
jethanandani@gmail.com</a></span></div></div><div><br>On May 30, 2014, at 3:=
32 PM, "Adrian Farrel" &lt;<a href=3D"mailto:adrian@olddog.co.uk">adrian@old=
dog.co.uk</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><span>O=
K, thanks to those of you who have contacted me about the future of KARP wor=
k.</span><br><span></span><br><span>I will ask the Secretariat to close the w=
orking group forthwith, and keep the</span><br><span>mailing list open.</spa=
n><br><span></span><br><span>draft-ietf-karp-ops-model</span><br><span>Is on=
 the RFC Editor queue and has completed Auth48</span><br><span>Publication s=
oon</span><br><span></span><br><span>draft-ietf-karp-bfd-analysis</span><br>=
<span>The I-D has been refreshed and WG last call is complete.</span><br><sp=
an>The BFD working group has already reviewed the document.</span><br><span>=
Brian is working on a shepherd write-up and I will AD Sponsor the publicatio=
n.</span><br><span></span><br><span>draft-ietf-karp-isis-analysis</span><br>=
<span>Document almost complete. </span><br><span>Needs a final push and revi=
ew by the ISIS WG.</span><br><span>I will AD sponsor it when it is ready.</s=
pan><br><span></span><br><span>Management plane solution to AKM</span><br><s=
pan>Sam has offered to work on something here.</span><br><span>I'm sure he w=
ould welcome help if anyone is willing.</span><br><span>We can easily find a=
 home for this sort of work. I would start with the OPSAWG</span><br><span>b=
ut maybe it will belong in netmod.</span><br><span></span><br><span>draft-ch=
unduri-karp-kmp-router-fingerprints</span><br><span>Uma has recently posted a=
 new revision.</span><br><span>This document can be advanced as AD sponsored=
 when it is ready.</span><br><span></span><br><span>draft-bhatia-karp-pim-ga=
p-analysis</span><br><span>This document needs work.</span><br><span>I'll as=
k the PIM chairs to run with this in the PIM WG.</span><br><span></span><br>=
<span>draft-mahesh-karp-lmp-analysis</span><br><span>This document needs wor=
k.</span><br><span>I'll ask the CCAMP chairs to run with this in the CCAMP W=
G.</span><br><span></span><br><span>New work / other work:</span><br><span>-=
 No new or existing work is "banned" or blocked...</span><br><span> &nbsp;&n=
bsp;- Write your I-Ds and polish them</span><br><span>- This mailing list re=
mains open for general discussions</span><br><span>- Specific work (for exam=
ple analysis of protocols against the KARP</span><br><span> &nbsp;&nbsp;guid=
elines) should be taken to protocol-owning working groups</span><br><span>- W=
ork on TCP/AO for routing protocols (if anyone wishes to pursue it)</span><b=
r><span> &nbsp;needs to be distributed to the correct place. Some of it will=
 be specific</span><br><span> &nbsp;to enhancing BGP security and belongs in=
 IDR or SIDR, some of it may</span><br><span> &nbsp;be specific to other rou=
ting protocols and can be handled there. But</span><br><span> &nbsp;obviousl=
y, work on TCP/AO must also involve the Security Area and</span><br><span> &=
nbsp;(if it changes the protocol) the Transport Area. We'll handle these on<=
/span><br><span> &nbsp;a case-by-case basis as drafts are produced.</span><b=
r><span></span><br><span>Finally, I want to thank you all, and especially th=
e chairs, for the work done</span><br><span>by KARP.</span><br><span></span>=
<br><span>Thanks,</span><br><span>Adrian</span><br><span></span><br><span>__=
_____________________________________________</span><br><span>karp mailing l=
ist</span><br><span><a href=3D"mailto:karp@ietf.org">karp@ietf.org</a></span=
><br><span><a href=3D"https://www.ietf.org/mailman/listinfo/karp">https://ww=
w.ietf.org/mailman/listinfo/karp</a></span><br></div></blockquote></body></h=
tml>=

--Apple-Mail-B196FF17-B3EB-4052-8C0E-5EC521CF5D9A--