IETF Logo Mail Archive

Re: [karp] Last Call: <draft-ietf-karp-ops-model-07.txt> (Operations Model for Router Keying) to Informational RFC

Danny McPherson <danny@tcb.net> Mon, 29 July 2013 17:02 UTC

Return-Path: <danny@tcb.net>
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 0E64A21F9A44 for <karp@ietfa.amsl.com>; Mon, 29 Jul 2013 10:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level:
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 pkCC7qGW2Qdf for <karp@ietfa.amsl.com>; Mon, 29 Jul 2013 10:02:15 -0700 (PDT)
Received: from mail.friendswithtools.org (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id DA78321E8093 for <karp@ietf.org>; Mon, 29 Jul 2013 09:55:59 -0700 (PDT)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id 791AA30004D for <karp@ietf.org>; Mon, 29 Jul 2013 16:55:32 +0000 (UTC)
Received: from dhcp-138f.meeting.ietf.org (dhcp-138f.meeting.ietf.org [130.129.19.143]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id BCDEE30004A; Mon, 29 Jul 2013 10:55:30 -0600 (MDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <tsltxjdvhcs.fsf@mit.edu>
Date: Mon, 29 Jul 2013 12:55:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2946F5C1-FA69-4E47-983A-0D3565C9DDFF@tcb.net>
References: <20130729063557.22039.63212.idtracker@ietfa.amsl.com> <tsltxjdwxtv.fsf@mit.edu> <21DC453F-A434-463F-9F69-D036675507FB@tcb.net> <tsltxjdvhcs.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1508)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Mon Jul 29 10:55:32 2013
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 51f69e8442075158818419
X-DSPAM-Factors: 27, wrong+#+How, 0.40000, 2013+at, 0.40000, to+#+#+#+validation, 0.40000, time+#+#+#+permit, 0.40000, never+digitally, 0.40000, Subject*Model+#+Router, 0.40000, Subject*Router+Keying, 0.40000, Routers+#+to, 0.40000, enough+#+#+#+receivers, 0.40000, that+receivers, 0.40000, Subject*Model+for, 0.40000, of+integrity, 0.40000, a+#+#+be, 0.40000, meant+New, 0.40000, hartmans+#+#+edu, 0.40000, Sam+#+#+these, 0.40000, AM+#+Hartman, 0.40000, Routers+need, 0.40000, Mime-Version*OS+X, 0.40000, enough+time, 0.40000, generation+#+#+protected, 0.40000, Subject*Call+#+Operations, 0.40000, Subject*to+Informational, 0.40000, signing+is, 0.40000, To*Hartman+hartmans-ietf, 0.40000, Sam+#+addressing, 0.40000, Mime-Version*6.5+1508, 0.40000
Cc: ietf@ietf.org, karp@ietf.org
Subject: Re: [karp] Last Call: <draft-ietf-karp-ops-model-07.txt> (Operations Model for Router Keying) to Informational RFC
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, 29 Jul 2013 17:02:32 -0000

On Jul 29, 2013, at 5:35 AM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
> 
> I like your text below except that signing is the wrong word.
> How about generation of integrity-protected messages?

Yeah, that's what I meant..  New text WFM, thanks [again] Sam for addressing these concerns!

-danny



> These messages are almost never digitally signed.

> Proposed text:
> 
>> Routers need to
>>     have tight enough time synchronization that receivers permit a key
>>     to be utilized for validation prior to the first use of that key for signing or
>>     availability will be impacted.
>

v2.23.0 | Report a Bug | By Email