From gregory.ietf@gmail.com Fri Jun 1 01:09:33 2012 Return-Path: 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 92AA721F85C4 for ; Fri, 1 Jun 2012 01:09:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.309 X-Spam-Level: X-Spam-Status: No, score=-103.309 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, HTML_FONT_LOW_CONTRAST=0.124, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, 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 zvgS5exmtVVY for ; Fri, 1 Jun 2012 01:09:32 -0700 (PDT) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id BEBFD21F85C2 for ; Fri, 1 Jun 2012 01:09:32 -0700 (PDT) Received: by dacx6 with SMTP id x6so2426788dac.31 for ; Fri, 01 Jun 2012 01:09:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=j6WGYdUTcO+c+DmSEH3RpplrZF23WAnzD0wxGaCPCbA=; b=b5aMIZg/cF1AJxHc1ooM5S3j4P9wlJYnThaE/XKe9Yv2U9w+cYYkQQTh3ieXWHmTj+ Qky0TjScPZiZoPYakPOGYRP2YNGQT811xRFKHuJ5md8g+bIsasLflgTjZvKBegWB6uS7 1wq63WHXjN/i4btCbYeP4nGb6RzQaakgDGPGgNm6bvTgTV3Ejw068KrLsoSXCs8k9g+P ThQP3/vM+S+FKUUieBUIZS74LHqKl2Frr5GUJDfRAYu3symcMEuEIgGfnOpNSiAy0Zso vEVeZdyYD7XtsmcDEKRo9Ma+rrS/8sezFaIcGq5t5R2E/J7l9IktryJe6JBzBX1Xjr9t /h+A== MIME-Version: 1.0 Received: by 10.68.242.166 with SMTP id wr6mr8008066pbc.28.1338538172252; Fri, 01 Jun 2012 01:09:32 -0700 (PDT) Received: by 10.143.67.2 with HTTP; Fri, 1 Jun 2012 01:09:32 -0700 (PDT) Date: Fri, 1 Jun 2012 01:09:32 -0700 Message-ID: From: Gregory Lebovitz To: Uma Chunduri Content-Type: multipart/alternative; boundary=047d7b339c4f46802a04c164b46f Cc: "karp@ietf.org" Subject: [karp] Threats-reqs Issue 10 (was "Re: I-D Action: draft-ietf-karp-threats-reqs-05.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 08:09:33 -0000 --047d7b339c4f46802a04c164b46f Content-Type: text/plain; charset=ISO-8859-1 So we are agreed on all but two of your comments. One is on Req 21, and I've asked Manav to reply to that. The other is issue 10. See inline... On Thu, May 31, 2012 at 11:33 AM, Uma Chunduri wrote: > ** > Hi Gregory, > > Changes look fine to me. See my comments in-line..[Uma] > -- > Uma C. > > > ------------------------------ > *From:* Gregory Lebovitz [mailto:gregory.ietf@gmail.com] > *Sent:* Thursday, May 31, 2012 7:58 AM > *To:* Uma Chunduri; Bhatia, Manav (Manav) > *Cc:* karp@ietf.org; Brian Weis > > *Subject:* Re: [karp] I-D Action: draft-ietf-karp-threats-reqs-05.txt > > Hello, Uma. Thanks for your input. > > > On Fri, May 18, 2012 at 5:00 PM, Uma Chunduri wrote: > >> ** >> Dear Authors, >> >> I read this version and the document is in good shape. >> >> If, it's not too late, I have few comments on the 05 version. >> >> >> 1.a) Page 4: Section 1. Introduction >> Third Bullet: >> " o Create specifications for cryptographic validation of routing >> message content." >> "The third bullet is being addressed in the SIDR >> working group." >> Though we can understand what SIDR is doing - "routing message >> content" just doesn't imply BGP message? >> I can understand what you are trying to say, but IMO, what is said is >> not representative. >> >> > > How about this: > NEW: The third bullet is being addressed in other efforts within the IETF. > *For example, BGP message content validity is being addressed in the SIDR > working group. * > ** > --SNIP-- > >> 3. Section 1.1, Page 6: >> "If session or traffic >> keys are being used, KMP is responsible for generating them and >> determining when they should be renewed." >> >> This is not necessarily the only way as it sounds. KMP can also be >> used for only master key generation and >> traffic keys are generated from the same by the master key consumer. >> And also determining when the keys should >> be renewed may not be KMP function. So I am not quite you define KMP >> this way. >> > > Understood. How about this: > > NEW: In some routing protocols traffic keys are derived by the routing > protocol from session / master keys. In this case, KMP is responsible for > the session / master key generation. In other cases, there are only traffic > keys (and no session / master keys), and KMP is responsible for the traffic > key generation. > *tracker ID 10. > > *[Uma]: Perhaps you can drop "session/" in the above, as that sounds > more synonymous to traffic keys rather than master key (both places).* > > Yes, I think you are right. New text will be: *In some routing protocols traffic keys are derived by the routing protocol from a master key. In this case, KMP is responsible for the master key generation. In other cases, there are only traffic keys (and no master keys), and in such a case KMP is responsible for the traffic key generation. * * * *Gregory.* * * *-- SNIP --* > > -- ---- IETF related email from Gregory M. Lebovitz --047d7b339c4f46802a04c164b46f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
So we are agreed on all but two of your comments= . One is on Req 21, and I've asked Manav to reply to that. The other is= issue 10. See inline...

On Thu, May 31, 2012 at 11:33 AM, Uma Chunduri <uma.chunduri@erics= son.com> wrote:
Hi Gregory,
=A0
Changes=A0look fine to me. See my comments=20 in-line..[Uma]
--
Uma C.
=A0

From: Gregory Lebovitz=20 [mailto:gregory= .ietf@gmail.com]
Sent: Thursday, May 31, 2012 7:58=20 AM
To: Uma Chunduri; Bhatia, Manav (Manav)
Cc:=20 karp@ietf.org; Brian= Weis

Subject: Re: [karp] I-D Action:=20 draft-ietf-karp-threats-reqs-05.txt

Hello, Uma. Thanks for your input.=A0


On Fri, May 18, 2012 at 5:00 PM, Uma Chunduri <uma.chunduri@ericsson.com> wrote:
Dear=20 Authors,
=A0
I read this=20 version and the document is in good shape.
=A0
If, it's not too=20 late, I have few comments=A0on the 05 version.
=A0
=A0
1.a) Page 4: Section 1.=A0=20 Introduction
=A0=A0=A0 Third Bullet:
=A0=A0=A0=20 "=A0=A0 o=A0 Create specifications for cryptographic validation of= =20 routing
=A0=A0=A0=A0=A0 message=20 content."
=A0=A0=A0 "The third bullet is being addressed in = the=20 SIDR
=A0=A0 working group."
=A0=A0 Though we can understand=20 what SIDR is doing -=A0 "routing message content" just doesn= 9;t=20 imply=A0BGP message?
=A0=A0 I=20 can=A0understand what you are trying to say, but IMO, what i= s=20 said is not representative.
=A0
How about this:
NEW: The third bullet is being addressed in othe= r efforts=20 within the IETF.=A0For=20 example, BGP message content validity is being addressed in the SIDR workin= g=20 group.=A0
<= /b>=A0
=A0
--SNIP--=A0
=A0
3. Section 1.1, Page 6:
= =A0=A0=20 "If session or traffic
=A0=A0=A0=A0=A0 keys are being used,=20 KMP is responsible for generating them and
=A0=A0=A0=A0=A0=20 determining when they should be renewed."
=A0
=A0=A0 This is not necessaril= y the=20 only way as it sounds. KMP can also be used for only master key generatio= n and=20
=A0=A0 traffic keys are generated from the same by the master key=20 consumer. And also determining when the keys should
=A0=A0 be=20 renewed may not be KMP function. So I am not quite you define KMP this=20 way.
Understood. How about this:
NEW: =A0 In some routing protocols traffic keys = are=20 derived by the routing protocol from session / master keys. In this case,= =20 KMP=A0is responsible for the session / master key generation.=A0In other=20 cases, there are only traffic keys (and no session / master keys), and KMP = is=20 responsible for the traffic key generation.=A0
*tracker ID 10.
=A0
[Uma]: Perhaps=A0you=20 can=A0drop "session/" in the above, as that=A0sounds more synonym= ous to=20 traffic keys rather than=A0master key=A0(both=20 places).
=A0<= /span>

Yes, I think you a= re right. New text will be:
In some routing protocols traffic keys are derived by the routing prot= ocol from a master key. In this case, KMP is responsible for the master key= generation. In other cases, there are only traffic keys (and no master key= s), and in such a case KMP is responsible for the traffic key generation.

Gregory.

-- SNIP --
=A0

-= -
----
IETF related email from
Gregory M. Lebovitz

--047d7b339c4f46802a04c164b46f-- From hartmans@mit.edu Wed Jun 6 11:37:46 2012 Return-Path: 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 0DC5511E80B2 for ; Wed, 6 Jun 2012 11:37:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.507 X-Spam-Level: X-Spam-Status: No, score=-103.507 tagged_above=-999 required=5 tests=[AWL=-1.242, 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 tNq2yyQXaNkD for ; Wed, 6 Jun 2012 11:37:45 -0700 (PDT) Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 5298211E80C7 for ; Wed, 6 Jun 2012 11:37:38 -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 8EF012043E; Wed, 6 Jun 2012 14:37:27 -0400 (EDT) Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 19FAC4151; Wed, 6 Jun 2012 14:37:34 -0400 (EDT) From: Sam Hartman To: Sean Turner References: <02717414-847B-4E3C-9F47-7AE30947F052@cisco.com> <4FB7FAC3.70701@ieca.com> <4FC3BE9D.7080506@ieca.com> Date: Wed, 06 Jun 2012 14:37:34 -0400 In-Reply-To: <4FC3BE9D.7080506@ieca.com> (Sean Turner's message of "Mon, 28 May 2012 14:06:21 -0400") Message-ID: 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 Cc: Sam Hartman , karp@ietf.org Subject: Re: [karp] WGLC of draft-ietf-karp-ospf-analysis-03 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 18:37:46 -0000 Hi. Looking at the draft I'd prefer to address your two comments by updating the solutions work section to add a paragraph describing what has been accomplished. I think that works better than working the solution work back in throughout the rest of the draft. The intent of this analysis was to capture the work that lead to deciding we need the solutions. >>>>> "Sean" == Sean Turner writes: Sean> Also should this sentence be changed: Sean> OLD: Sean> A security solution will be developed for OSPFv2 and OSPFv3 based on Sean> the OSPFv2 cryptographic authentication option. Sean> NEW: Sean> A security solution will be developed for OSPFv3 based on the OSPFv2 Sean> cryptographic authentication option. No, it's correct as written. we're updating both ospfv2 and v3. For both we're using the existing v2 as a basis. For v3 it's an entirely new option. For v2 it's a new option that handles source address, requires enough constraints that we get inter-connection replay, etc. From internet-drafts@ietf.org Wed Jun 6 11:52:11 2012 Return-Path: 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 5A2DC21F8859; Wed, 6 Jun 2012 11:52:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.525 X-Spam-Level: X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, 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 h6MRhDRgx9uL; Wed, 6 Jun 2012 11:52:10 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5215A21F8895; Wed, 6 Jun 2012 11:52:10 -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: 4.02 Message-ID: <20120606185210.9053.37680.idtracker@ietfa.amsl.com> Date: Wed, 06 Jun 2012 11:52:10 -0700 Cc: karp@ietf.org Subject: [karp] I-D Action: draft-ietf-karp-ospf-analysis-04.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 18:52:11 -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 : Analysis of OSPF Security According to KARP Design Guide Author(s) : Sam Hartman Dacheng Zhang Filename : draft-ietf-karp-ospf-analysis-04.txt Pages : 12 Date : 2012-06-06 This document analyzes OSPFv2 and OSPFv3 according to the guidelines set forth in section 4.2 of draft-ietf-karp-design-guide. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-karp-ospf-analysis-04.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-ospf-analysis-04.txt The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-karp-ospf-analysis/ From turners@ieca.com Wed Jun 6 12:21:00 2012 Return-Path: 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 D03C021F87D4 for ; Wed, 6 Jun 2012 12:21:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.093 X-Spam-Level: X-Spam-Status: No, score=-102.093 tagged_above=-999 required=5 tests=[AWL=0.172, 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 kbI718UT4o1l for ; Wed, 6 Jun 2012 12:21:00 -0700 (PDT) Received: from gateway09.websitewelcome.com (gateway09.websitewelcome.com [67.18.124.12]) by ietfa.amsl.com (Postfix) with ESMTP id 702A621F87D3 for ; Wed, 6 Jun 2012 12:21:00 -0700 (PDT) Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway09.websitewelcome.com (Postfix) with ESMTP id E2D467C8875B3 for ; Wed, 6 Jun 2012 14:20:59 -0500 (CDT) Received: from [96.231.120.23] (port=46446 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1ScLmt-0003oI-KF; Wed, 06 Jun 2012 14:20:59 -0500 Message-ID: <4FCFAD9A.4070707@ieca.com> Date: Wed, 06 Jun 2012 15:20:58 -0400 From: Sean Turner User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Sam Hartman References: <02717414-847B-4E3C-9F47-7AE30947F052@cisco.com> <4FB7FAC3.70701@ieca.com> <4FC3BE9D.7080506@ieca.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator1743.hostgator.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ieca.com X-BWhitelist: no X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: (thunderfish.local) [96.231.120.23]:46446 X-Source-Auth: sean.turner@ieca.com X-Email-Count: 5 X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20= Cc: karp@ietf.org Subject: Re: [karp] WGLC of draft-ietf-karp-ospf-analysis-03 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 19:21:01 -0000 Sam, That's okay by me. spt On 6/6/12 2:37 PM, Sam Hartman wrote: > Hi. > Looking at the draft I'd prefer to address your two comments by updating > the solutions work section to add a paragraph describing what has been > accomplished. > I think that works better than working the solution work back in > throughout the rest of the draft. > The intent of this analysis was to capture the work that lead to > deciding we need the solutions. >>>>>> "Sean" == Sean Turner writes: > Sean> Also should this sentence be changed: > > Sean> OLD: > > Sean> A security solution will be developed for OSPFv2 and OSPFv3 based on > Sean> the OSPFv2 cryptographic authentication option. > > Sean> NEW: > > Sean> A security solution will be developed for OSPFv3 based on the OSPFv2 > Sean> cryptographic authentication option. > > > No, it's correct as written. we're updating both ospfv2 and v3. For > both we're using the existing v2 as a basis. For v3 it's an entirely > new option. For v2 it's a new option that handles source address, > requires enough constraints that we get inter-connection replay, etc. > From internet-drafts@ietf.org Sat Jun 23 17:28:43 2012 Return-Path: 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 EA74E21F8683; Sat, 23 Jun 2012 17:28:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.448 X-Spam-Level: X-Spam-Status: No, score=-102.448 tagged_above=-999 required=5 tests=[AWL=0.151, 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 pBqw4oNGIKXN; Sat, 23 Jun 2012 17:28:43 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BBB121F867B; Sat, 23 Jun 2012 17:28:43 -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: 4.21 Message-ID: <20120624002843.17335.73994.idtracker@ietfa.amsl.com> Date: Sat, 23 Jun 2012 17:28:43 -0700 Cc: karp@ietf.org Subject: [karp] I-D Action: draft-ietf-karp-routing-tcp-analysis-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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2012 00:28:44 -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 Pro= tocols Working Group of the IETF. Title : Analysis of BGP, LDP, PCEP and MSDP Issues According to = KARP Design Guide Author(s) : Mahesh Jethanandani Keyur Patel Lianshu Zheng Filename : draft-ietf-karp-routing-tcp-analysis-02.txt Pages : 17 Date : 2012-06-23 Abstract: This document analyzes BGP, LDP, PCEP and MSDP according to guidelines set forth in section 4.2 of Keying and Authentication for Routing Protocols Design Guidelines [RFC6518]. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-karp-routing-tcp-analysis-02 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-routing-tcp-analysis-02 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Fri Jun 29 05:30:16 2012 Return-Path: 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 120B921F8726; Fri, 29 Jun 2012 05:30:16 -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 GOIIJ5T-2xxH; Fri, 29 Jun 2012 05:30:15 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A95E21F8620; Fri, 29 Jun 2012 05:30:10 -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: 4.21p1 Message-ID: <20120629123010.7535.24029.idtracker@ietfa.amsl.com> Date: Fri, 29 Jun 2012 05:30:10 -0700 Cc: karp@ietf.org Subject: [karp] I-D Action: draft-ietf-karp-crypto-key-table-03.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2012 12:30:16 -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 Pro= tocols Working Group of the IETF. Title : Database of Long-Lived Symmetric Cryptographic Keys Author(s) : Russell Housley Tim Polk Sam Hartman Dacheng Zhang Filename : draft-ietf-karp-crypto-key-table-03.txt Pages : 12 Date : 2012-06-29 Abstract: This document specifies the information contained in a conceptual database of long-lived cryptographic keys used by many different security protocols. The database is designed to support both manual and automated key management. In addition to describing the schema for the database, this document describes the operations that can be performed on the database as well as the requirements for the security protocols that wish to use the database. In many typical scenarios, 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. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-karp-crypto-key-table There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-karp-crypto-key-table-03 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-karp-crypto-key-table-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From jmh@joelhalpern.com Fri Jun 29 16:01:25 2012 Return-Path: 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 E339121F86A5 for ; Fri, 29 Jun 2012 16:01:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.361 X-Spam-Level: X-Spam-Status: No, score=-102.361 tagged_above=-999 required=5 tests=[AWL=-0.096, 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 p6+QuOOLRi2y for ; Fri, 29 Jun 2012 16:01:25 -0700 (PDT) Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8F821F86A4 for ; Fri, 29 Jun 2012 16:01:25 -0700 (PDT) Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 7CEA6558015 for ; Fri, 29 Jun 2012 16:01:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 18B951C9BE1 for ; Fri, 29 Jun 2012 16:01:25 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net Received: from [10.10.10.105] (pool-71-161-52-145.clppva.btas.verizon.net [71.161.52.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 8E9781C9BE0 for ; Fri, 29 Jun 2012 16:01:24 -0700 (PDT) Message-ID: <4FEE33BE.7080609@joelhalpern.com> Date: Fri, 29 Jun 2012 19:01:18 -0400 From: "Joel M. Halpern" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: "karp@ietf.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [karp] WG LC: draft-ietf-karp-routing-tcp-analysis-02 to Informational 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2012 23:01:26 -0000 This beings a two week WG last call to determine if folk support submitting the draft: http://datatracker.ietf.org/doc/draft-ietf-karp-routing-tcp-analysis/?include_text=1 to our AD for publication as an Informational RFC. Please send comments of support, or raising issues or concerns, to the WG email list. (Comments with explanation are much more useful than those without.) Given the weekend, the LC will run till 8pm PDT on 16-July-2012. Thank you, Joel M. Halpern and Brian Weis co-chairs