Re: [karp] KARP Agenda at IETF 76

"Gregory M. Lebovitz" <gregory.ietf@gmail.com> Wed, 28 October 2009 01:28 UTC

Return-Path: <gregory.ietf@gmail.com>
X-Original-To: karp@core3.amsl.com
Delivered-To: karp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3365E3A6860 for <karp@core3.amsl.com>; Tue, 27 Oct 2009 18:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level:
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[AWL=0.154, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JHku7V5HImsg for <karp@core3.amsl.com>; Tue, 27 Oct 2009 18:28:24 -0700 (PDT)
Received: from mail-pz0-f204.google.com (mail-pz0-f204.google.com [209.85.222.204]) by core3.amsl.com (Postfix) with ESMTP id 57AF13A67F7 for <karp@ietf.org>; Tue, 27 Oct 2009 18:28:24 -0700 (PDT)
Received: by pzk42 with SMTP id 42so259461pzk.31 for <karp@ietf.org>; Tue, 27 Oct 2009 18:28:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:x-mailer:date:to :from:subject:cc:in-reply-to:references:mime-version:content-type; bh=k7RquK1u9hJkp5EMlcrqycdzdG06UnPq7OA51tKfxqM=; b=vjKoEhPnfjqCJTgVt27g+TpeHtYQsKkHSSekYBmWTt8q63LRUCKj8otTdMpZz0AY/M oscAyBrkBmJUZ5+z02TzOTK9ZqvReZTWDLGxMKRW4VaYjVdpsggT3P042R0E0m+2a9Mz U2lCDHP7icOqL/SvxG9mzneebDZT5dWuKtfwE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:x-mailer:date:to:from:subject:cc:in-reply-to:references :mime-version:content-type; b=JOj/eRf035+xx7uHUOQLqIjDLpyBmiLBUL9Xz2k3UqV9sG/kHtlAcvyRvrdmb1241w B9Tiwnpu6lwML74NW+98Gn7H4iTcyxK2FsgHb/X+zxMD2j4V3VfC3Vj/QDAzgrbPSdzQ +QE8TmEfWX+N9CsbLWq6Q8ZwyhD6CrAjHgH8s=
Received: by 10.114.237.37 with SMTP id k37mr5256872wah.31.1256693316825; Tue, 27 Oct 2009 18:28:36 -0700 (PDT)
Received: from Gregory-T60.gmail.com (nat-service4.juniper.net [66.129.225.151]) by mx.google.com with ESMTPS id 20sm264314pzk.1.2009.10.27.18.28.33 (version=SSLv3 cipher=RC4-MD5); Tue, 27 Oct 2009 18:28:35 -0700 (PDT)
Message-ID: <4ae79e43.9413f30a.187e.1623@mx.google.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 27 Oct 2009 18:28:30 -0700
To: Brian Weis <bew@cisco.com>
From: "Gregory M. Lebovitz" <gregory.ietf@gmail.com>
In-Reply-To: <592901D5-7B45-4001-A784-3E341AFDB863@cisco.com>
References: <02562157-F43A-4151-9D11-7D0EB3151B16@cisco.com> <4ae79712.9613f30a.5387.159a@mx.google.com> <592901D5-7B45-4001-A784-3E341AFDB863@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: karp@ietf.org
Subject: Re: [karp] KARP Agenda at IETF 76
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion list for key management for routing and transport protocols <karp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Oct 2009 01:28:25 -0000

At 06:15 PM 10/27/2009, Brian Weis wrote:
>Hi Gregory,
>
>On Oct 27, 2009, at 5:57 PM, Gregory M. Lebovitz wrote:
>
>>At 08:12 PM 10/26/2009, Brian Weis wrote:
>>>Folks,

--snip--


>>Could we add this to the charter:
>>- Definition of the process of what work will be done in KARP vs in
>>routing WG's and how the overlaps will be handled.  - 10 min
>
>My expectation is that this will be naturally covered during the
>Charter Discussion and Open Discussion, as there are likely to be many
>opinions. I don't think 10 minutes would be long enough, but I'll
>confer with Joel on this request.

Either way is fine; I just want to ensure we address this issue 
explicitly, because people keep bringing it up.


>>To get more time for this process discussion, I'd suggest the
>>example preso of TCP-AO be shortened to 10 min. Justification: we
>>don't need to teach on -AO, just quickly show how we got from MD5 to
>>-AO as an example. Then we can take 5 min from the discussion at the
>>end, to create a total of 10 min for the definition of process part.
>>
>>Last, I'd like to see some of brief examples of work in progress on
>>KARP-like topics from the community. Several of you have sent me
>>things like these, from Vishwas:
>>
>>1. 
>>http://www.ietf.org/internet-drafts/draft-ietf-opsec-routing-protocols-crypto-issues-00.txt
>>is the draft I was talking about.
>>2. http://tools.ietf.org/html/rfc5310 is the IS-IS RFC.
>>3. http://tools.ietf.org/html/draft-ietf-ospf-hmac-sha-03 is the
>>equivalent OSPF draft
>>4. http://tools.ietf.org/html/draft-bhatia-manral-igp-crypto-requirements-03
>>is the draft for Crypto requirements.
>>
>>Would anyone like to give a 5 min preso on any of these things? Or
>>any other related work?
>
>There are actually more protocol documents available, and I don't
>think we'd have time to discuss them all in detail. It's my plan to
>cover them all lightly during the Survey agenda item. Does that sound
>reasonable to you?

Sure. I think we are trying to achieve the same thing here, which is 
to draw together all the different efforts going on all over the rtg 
and security areas, show that there is indeed a lot of interest and 
work in progress, and get them all going in somewhat the same 
direction. I think having one other presentation other than TCP-AO 
would be good, as an example. The work on multicast protocols or the 
OSPF would be good, because they share many similar issues. But I'm 
fine either way. Your call.

Gregory.


>Thanks,
>Brian
>
>>
>>Gregory.
>>
>>
>>
>>
>>>Thanks,
>>>Joel & Brian
>>>_______________________________________________
>>>karp mailing list
>>>karp@ietf.org
>>>https://www.ietf.org/mailman/listinfo/karp
>
>
>--
>Brian Weis
>Router/Switch Security Group, ARTG, Cisco Systems
>Telephone: +1 408 526 4796
>Email: bew@cisco.com
>
>