Re: [karp] WGLC of draft-ietf-karp-ospf-analysis-03

Sean Turner <turners@ieca.com> Mon, 28 May 2012 18:06 UTC

Return-Path: <turners@ieca.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 63EAC21F8672 for <karp@ietfa.amsl.com>; Mon, 28 May 2012 11:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.105
X-Spam-Level:
X-Spam-Status: No, score=-102.105 tagged_above=-999 required=5 tests=[AWL=0.160, 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 6N9vIxhT6FPy for <karp@ietfa.amsl.com>; Mon, 28 May 2012 11:06:23 -0700 (PDT)
Received: from gateway13.websitewelcome.com (gateway13.websitewelcome.com [67.18.82.4]) by ietfa.amsl.com (Postfix) with ESMTP id EC60D21F866D for <karp@ietf.org>; Mon, 28 May 2012 11:06:22 -0700 (PDT)
Received: by gateway13.websitewelcome.com (Postfix, from userid 5007) id 9338971E292DE; Mon, 28 May 2012 13:06:22 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway13.websitewelcome.com (Postfix) with ESMTP id 85A7971E292A3 for <karp@ietf.org>; Mon, 28 May 2012 13:06:22 -0500 (CDT)
Received: from [71.191.15.83] (port=41263 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <turners@ieca.com>) id 1SZ4Kk-00079k-6w; Mon, 28 May 2012 13:06:22 -0500
Message-ID: <4FC3BE9D.7080506@ieca.com>
Date: Mon, 28 May 2012 14:06:21 -0400
From: Sean Turner <turners@ieca.com>
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 <hartmans-ietf@mit.edu>
References: <02717414-847B-4E3C-9F47-7AE30947F052@cisco.com> <4FB7FAC3.70701@ieca.com> <tsld35oeed0.fsf@mit.edu>
In-Reply-To: <tsld35oeed0.fsf@mit.edu>
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) [71.191.15.83]:41263
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
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 <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, 28 May 2012 18:06:23 -0000

On 5/28/12 7:26 AM, Sam Hartman wrote:
>>>>>> "Sean" == Sean Turner<turners@ieca.com>  writes:
>
>      Sean>  Quick question: Should the OSPFv3 section discuss RFC 6506:
>      Sean>  Supporting Authentication Trailer for OSPFv3?
>
> I guess we can update to add a reference if you like. I kind of view
>   this as work that lead to that RFC though.

I think it's worth pointing out that one of the follow-on documents that 
this analysis was going to produce is completed.

Also should this sentence be changed:

OLD:

A security solution will be developed for OSPFv2 and OSPFv3 based on the 
OSPFv2 cryptographic authentication option.

NEW:

A security solution will be developed for OSPFv3 based on the OSPFv2 
cryptographic authentication option.

Shouldn't this draft also discuss the

Only talking about OPSFv3?  It seems odd to develop a security solution 
for OSPv2 based on the already defined OSPFv3 option.

Isn't [I-D.ietf-ospf-security-extension-manual-keying] also a solution 
output that should be discussed in s5?


some nits from nitchecker:

Need an IANA considerations section.

r/I-D.ietf-opsec-routing-protocols-crypto-issues/RFC6309

r/draft-ietf-opsec-routing-protocols-crypto-issues/RFC6309

r/draft-ietf-karp-threats-reqs-04/draft-ietf-karp-threats-reqs-05

r/draft-ietf-ospf-security-extension-manual-keying-01/draft-ietf-ospf-security-extension-manual-keying-02

spt