
From jmh@joelhalpern.com  Sat Oct  8 19:19:42 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8478A21F849C for <karp@ietfa.amsl.com>; Sat,  8 Oct 2011 19:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBJ5jIA5pLBB for <karp@ietfa.amsl.com>; Sat,  8 Oct 2011 19:19:42 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes-ipv6.tigertech.net [IPv6:2604:4f00::1:0:0:16]) by ietfa.amsl.com (Postfix) with ESMTP id 13A4921F849B for <karp@ietf.org>; Sat,  8 Oct 2011 19:19:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id E94BD43B310 for <karp@ietf.org>; Sat,  8 Oct 2011 19:19:41 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.104] (pool-71-161-52-27.clppva.btas.verizon.net [71.161.52.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 2DF5F43B30F for <karp@ietf.org>; Sat,  8 Oct 2011 19:19:41 -0700 (PDT)
Message-ID: <4E9104B8.30701@joelhalpern.com>
Date: Sat, 08 Oct 2011 22:19:36 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "karp@ietf.org" <karp@ietf.org>
References: <F6BF0DF7-1529-497A-9642-85CD8E100DF4@vigilsec.com>
In-Reply-To: <F6BF0DF7-1529-497A-9642-85CD8E100DF4@vigilsec.com>
X-Forwarded-Message-Id: <F6BF0DF7-1529-497A-9642-85CD8E100DF4@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [karp] Fwd: Re: Russ Housley's Discuss on draft-ietf-karp-design-guide-05: (with DISCUSS and COMMENT)
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 09 Oct 2011 02:19:42 -0000

Russ Housley raised a discuss as to whether the design guidelines 
document should address the "common framework" for applying security to 
routing protocols that is called for in our charter.

there are multiple opinions on this.

Russ asked what the WG's opinion is, which seems an appropriate question.

So, folks, comments?

Thank you,
Joel

-------- Original Message --------
Subject: Re: Russ Housley's Discuss on draft-ietf-karp-design-guide-05: 
(with DISCUSS and COMMENT)
Date: Thu, 6 Oct 2011 13:18:05 -0400
From: Russ Housley <housley@vigilsec.com>
To: Joel M. Halpern <jmh@joelhalpern.com>
CC: The IESG <iesg@ietf.org>, karp-chairs@tools.ietf.org, 
draft-ietf-karp-design-guide@tools.ietf.org

Joel:

Having worked through the use of the crypto key table for TCP-AO and 
IS-IS, I am quite confident that the approaches that KARP will employ 
are fairly clear.  Sam came to essentially the same place on his OSPF work.

...
Russ


> Thank you Russ.
> I expect the authors will address your comments 1, 2, and 4.
>
> I want to discuss item 3 and your comment a bit.
>
> With regard to item 3, you ask that this document provide a sgtarting point on the common frameworks for applying security to the routing protocols.
> Unfortunately, that would require that we actually know and have agreement on what those common frameworks are.  As we do not have that in hand, and we have chosen not to hold up all KARP related routing protocol security work until we do have such, I am very reluctant to hold this document up while we figure that out.
...
> Yours,
> Joel M. Halpern
>
> On 10/6/2011 9:32 AM, Russ Housley wrote:
>> Russ Housley has entered the following ballot position for
>> draft-ietf-karp-design-guide-05: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
...
>>   3.  The KARP WG charter says:
>>
>>     Routing protocols use a range of transport mechanisms and
>>     communication relationships. There are also differences in
>>     details among the various protocols. The working group will
>>     attempt to describe the security relevant characteristics of
>>     routings protocols, such as the use or non-use of TCP, or the
>>     frequent use of group communication versus purely pairwise
>>     communication. Using these characteristics, the working group
>>     will then provide suitable common frameworks that can be applied,
>>     and tailored, to improve the communication security of the routing
>>     protocols.
>>
>>   This document covers much of this material.  It talks about
>>   "transport mechanisms" and "communications relationships".
>>   It covers part of the material I would expect in a discussion of
>>   "security relevant characteristics of routings protocols".  It
>>   covers the difference in "group" and "pairwise" communications.
>>   It does not come up with "common frameworks".  I suggest that
>>   this document is a very good start at this charter deliverable.
>>
...

From internet-drafts@ietf.org  Mon Oct 10 16:28:13 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F2021F8C31; Mon, 10 Oct 2011 16:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ee+Z40t7a7ws; Mon, 10 Oct 2011 16:28:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF26321F8A64; Mon, 10 Oct 2011 16:28:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.60
Message-ID: <20111010232812.12220.43971.idtracker@ietfa.amsl.com>
Date: Mon, 10 Oct 2011 16:28:12 -0700
Cc: karp@ietf.org
Subject: [karp] I-D Action: draft-ietf-karp-design-guide-06.txt
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 10 Oct 2011 23:28:13 -0000

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

	Title           : Keying and Authentication for Routing Protocols (KARP) D=
esign Guidelines
	Author(s)       : Gregory M. Lebovitz
                          Manav Bhatia
	Filename        : draft-ietf-karp-design-guide-06.txt
	Pages           : 29
	Date            : 2011-10-10

      This document is one of a series concerned with defining a
      roadmap of protocol specification work for the use of modern
      cryptographic mechanisms and algorithms for message
      authentication in routing protocols.  In particular, it defines
      the framework for a key management protocol that may be used to
      create and manage session keys for message authentication and
      integrity.

   =


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-karp-design-guide-06.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-karp-design-guide-06.txt

From jmh@joelhalpern.com  Wed Oct 12 10:49:59 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2B6321F8B9C; Wed, 12 Oct 2011 10:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fw4gZRqbiZFu; Wed, 12 Oct 2011 10:49:59 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes-ipv6.tigertech.net [IPv6:2604:4f00::1:0:0:16]) by ietfa.amsl.com (Postfix) with ESMTP id 2E10F21F8B86; Wed, 12 Oct 2011 10:49:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 032AD43010A; Wed, 12 Oct 2011 10:49:59 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [192.168.243.68] (unknown [212.99.116.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 627404300A4; Wed, 12 Oct 2011 10:49:58 -0700 (PDT)
Message-ID: <4E95D344.30302@joelhalpern.com>
Date: Wed, 12 Oct 2011 13:49:56 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "lisp@ietf.org" <lisp@ietf.org>, "karp@ietf.org" <karp@ietf.org>
References: <20111011210422.209AB21F8EC6@ietfa.amsl.com>
In-Reply-To: <20111011210422.209AB21F8EC6@ietfa.amsl.com>
X-Forwarded-Message-Id: <20111011210422.209AB21F8EC6@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [karp] Fwd: Nomcom 2011-2012: Call for community feedback
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
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, 12 Oct 2011 17:49:59 -0000

-------- Original Message --------
Subject: Nomcom 2011-2012: Call for community feedback
Date: Tue, 11 Oct 2011 14:04:22 -0700 (PDT)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
CC: ietf@ietf.org

As per RFC 5680, NomCom 2011-2012 is issuing a call to the entire IETF
community for feedback on the Willing Nominees for the open IETF
positions. Nominations for the open positions are now closed and the
list of willing nominees is now quite stable.

Why is feedback important?
==========================

Feedback is information you think will help NomCom make a decision on
selecting candidates for open IETF positions. Feedback should be based
on information you know first hand about an individual nominee.
Community feedback is the most important input that determines who
fills the open positions. We cannot properly execute the task of
selecting the best candidates for the open positions without **YOUR**
participation and feedback.

Review the list of willing nominees and open positions
======================================================

The open list is currently available on the Nomcom page and the entire
community is invited to provide feedback on all nominees.  You can
provide your comments on all willing nominees at the following URL:

https://www.ietf.org/group/nomcom/2011/input/

where the list of willing nominees is available and sorted by open
position.

IMPORTANT NOTE: Access to the Provide Feedback pages requires an
www.ietf.org login. Logins used for previous years' nomcom pages used
the tools.ietf.org login, which is separate. To get a www.ietf.org
login if you don't already have one, please go to this page:
https://datatracker.ietf.org/accounts/create/

Means of providing feedback to the NomCom
=========================================

You can use one (or more) of the following methods to provide feedback
to the Nomcom:

- The best method is to enter it directly on the NomCom website at
https://www.ietf.org/group/nomcom/2011/input/ . Click on the name of
the person who you are providing feedback about and enter the text you
want to provide us.

- Send an email to nomcom11@ietf.org and be sure to identify the
nominee and position the feedback pertains to.

- Contact one (or more) of the Nomcom members by email.

- Contact us in person in Taipei during our office hours. (to be
   announced soon)

- You can provide **anonymous** feedback by contacting either the
Nomcom chair or any of the Nomcom members who will anonymize it for
the rest of the members.

I would like to thank everyone who has provided us feedback already,
and hope that more people from the community will take time to provide
us further feedback.

Suresh Krishnan
Chair, NomCom 2011-2012
nomcom-chair@ietf.org
suresh.krishnan@ericsson.com
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf


From internet-drafts@ietf.org  Wed Oct 19 04:26:46 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A96ED21F8AF5; Wed, 19 Oct 2011 04:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5eK0rSCcyU1f; Wed, 19 Oct 2011 04:26:46 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4371F21F8A67; Wed, 19 Oct 2011 04:26:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.60
Message-ID: <20111019112646.2555.26078.idtracker@ietfa.amsl.com>
Date: Wed, 19 Oct 2011 04:26:46 -0700
Cc: karp@ietf.org
Subject: [karp] I-D Action: draft-ietf-karp-design-guide-07.txt
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
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, 19 Oct 2011 11:26:46 -0000

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

	Title           : Keying and Authentication for Routing Protocols (KARP) D=
esign Guidelines
	Author(s)       : Gregory M. Lebovitz
                          Manav Bhatia
	Filename        : draft-ietf-karp-design-guide-07.txt
	Pages           : 31
	Date            : 2011-10-19

      This document is one of a series concerned with defining a
      roadmap of protocol specification work for the use of modern
      cryptographic mechanisms and algorithms for message
      authentication in routing protocols.  In particular, it defines
      the framework for a key management protocol that may be used to
      create and manage session keys for message authentication and
      integrity.

   =


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-karp-design-guide-07.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-karp-design-guide-07.txt

From internet-drafts@ietf.org  Sun Oct 23 17:05:12 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C200821F8B76; Sun, 23 Oct 2011 17:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2traOOLSdFp6; Sun, 23 Oct 2011 17:05:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44AE621F8B72; Sun, 23 Oct 2011 17:05:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.61
Message-ID: <20111024000512.20768.18488.idtracker@ietfa.amsl.com>
Date: Sun, 23 Oct 2011 17:05:12 -0700
Cc: karp@ietf.org
Subject: [karp] I-D Action: draft-ietf-karp-ops-model-01.txt
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 24 Oct 2011 00:05:12 -0000

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

	Title           : Operations Model for Router Keying
	Author(s)       : Sam Hartman
                          Dacheng Zhang
	Filename        : draft-ietf-karp-ops-model-01.txt
	Pages           : 23
	Date            : 2011-10-23

   Developing an operational and management model for routing protocol
   security that works across protocols will be critical to the success
   of routing protocol security efforts.  This document discusses issues
   and begins to consider development of these models.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-karp-ops-model-01.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-karp-ops-model-01.txt

From hartmans@mit.edu  Sun Oct 23 17:11:37 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A01F221F8AAC for <karp@ietfa.amsl.com>; Sun, 23 Oct 2011 17:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.952
X-Spam-Level: 
X-Spam-Status: No, score=-102.952 tagged_above=-999 required=5 tests=[AWL=-0.687, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m-YD1rAQUx0s for <karp@ietfa.amsl.com>; Sun, 23 Oct 2011 17:11:37 -0700 (PDT)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 390A521F8AB0 for <karp@ietf.org>; Sun, 23 Oct 2011 17:11:37 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 3AAE920274 for <karp@ietf.org>; Sun, 23 Oct 2011 20:12:35 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 333AA4239; Sun, 23 Oct 2011 20:11:04 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: karp@ietf.org
Date: Sun, 23 Oct 2011 20:11:04 -0400
Message-ID: <tslbot7gsfb.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [karp] draft-ietf-karp-ops-model
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 24 Oct 2011 00:11:37 -0000

We've lightly updated the karp ops model document in order to unexpire
it and to improve readability a bit.

For this document to really make forward progress, we need to have a
number of discussions:

1) I think it would be valuable to make an effort to update the key
table draft and make decisions related to that draft in order to address
questions coming out of draft-ietf-karp-ops-model, the integration of
key table support in OSPF, and our attempts to use the key table in
automated key management.  In other words, we have some experience
trying to use the key table abstraction in specs and now we should go
sit down in a small group work through what worked well and what didn't
and propose some stuff to the WG to consider.

2) The WG needs to consider some questions about what scope keys needs
to be represented at and how we want to do that in our operational
model.
This will be easier after 1.

3) We need to get together with operators and understand their
requirements for upgrade and deployment and how that interacts with
KARP.

4) We need to get together with router vendors--particularly the folks
that focus on configuration schemas and management models--and make some
decisions about what we want to require in order for people to be able
to manage KARP. Vendors can of course go beyond this.


From internet-drafts@ietf.org  Mon Oct 31 13:23:14 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA39511E820B; Mon, 31 Oct 2011 13:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-3ZSiIPgiAo; Mon, 31 Oct 2011 13:23:14 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E03E11E8201; Mon, 31 Oct 2011 13:23:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.62
Message-ID: <20111031202314.20519.27025.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2011 13:23:14 -0700
Cc: karp@ietf.org
Subject: [karp] I-D Action: draft-ietf-karp-crypto-key-table-02.txt
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 31 Oct 2011 20:23:14 -0000

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

	Title           : Database of Long-Lived Symmetric Cryptographic Keys
	Author(s)       : Russell Housley
                          Tim Polk
	Filename        : draft-ietf-karp-crypto-key-table-02.txt
	Pages           : 10
	Date            : 2011-10-31

   This document specifies the information contained in a database of
   long-lived cryptographic keys used by many different security
   protocols.  The database design supports both manual and automated
   key management.  In many instances, the security protocols do not
   directly use the long-lived key, but rather a key derivation function
   is used to derive a short-lived key from a long-lived key.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-karp-crypto-key-table-02.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-karp-crypto-key-table-02.txt
