Re: [OPSEC] The plan... / adoption of draft-bhatia-manral-igp-crypto-requirements-04
Joel Jaeggli <joelja@bogus.com> Sat, 05 December 2009 08:07 UTC
Return-Path: <joelja@bogus.com>
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 780803A67B7 for <opsec@core3.amsl.com>; Sat, 5 Dec 2009 00:07:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.915
X-Spam-Level:
X-Spam-Status: No, score=-1.915 tagged_above=-999 required=5 tests=[AWL=-0.685, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, MIME_8BIT_HEADER=0.3]
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 5SfrZM-M2mpY for <opsec@core3.amsl.com>; Sat, 5 Dec 2009 00:07:14 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 49AB93A6774 for <opsec@ietf.org>; Sat, 5 Dec 2009 00:07:14 -0800 (PST)
Received: from [192.168.1.151] (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.3/8.14.3) with ESMTP id nB5872fB050873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 5 Dec 2009 08:07:03 GMT (envelope-from joelja@bogus.com)
Message-ID: <4B19C002.5070800@bogus.com>
Date: Fri, 04 Dec 2009 18:05:54 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Alfred � <ah@TR-Sys.de>
References: <200912042240.XAA27245@TR-Sys.de>
In-Reply-To: <200912042240.XAA27245@TR-Sys.de>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Sat, 05 Dec 2009 08:07:03 +0000 (UTC)
Cc: opsec@ietf.org
Subject: Re: [OPSEC] The plan... / adoption of draft-bhatia-manral-igp-crypto-requirements-04
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Dec 2009 08:07:15 -0000
Thanks, that's an awesome offer of help. Alfred � wrote: > At Sun, 22 Nov 2009 07:13:49 +0530, Glen Kent wrote: > >>> ... >>> >>> draft-bhatia-manral-igp-crypto-requirements-04 - test for inclusion as a >>> wg document >>> >>> Document can be reviewed here: >>> >>> http://tools.ietf.org/html/draft-bhatia-manral-igp-crypto-requirements-04 >>> >> I firmly believe that we need such a document and fully support this. >> >> Glen > > +1 > > > I had reviewed all three of the "more recent" RFCs referred to in > that synoptical draft, and I share the opinion that such synopsis > and evaluation document gives very useful guidance. > I commit to perform a detailed review of the draft -- but this will > certainly take me some time again, perhaps late in January. > > > I'd also like to draw the group's attention to a short individual > draft originating from DNSEXT and DNSOP, > http://tools.ietf.org/html/draft-ogud-iana-protocol-maintenance-words-02 > that aims at establishing schematic keywords (a la RFC 2119) for use > in IANA registry to indicate maintenance/support levels (as seen by the > IETF/IESG) of protocol options, in particular cryptographic algorithms. > One objective is to establish a more lightweight and uniform method > to indicate and maintain implementation requirements. > > This efforts is somehow related to the above draft and seems to be > very useful from an operational perspective, and I'd like to encourage > you to review and support this draft; publication already is requested; > Russ Housley is shepherding the document (GEN area, lacking a wg, needs > a couple of drafts to justify its persistence :-) ) and I expect IETF LC > soon. > > > Kind regards, > Alfred H�nes. >
- Re: [OPSEC] The plan... / adoption of draft-bhati… Alfred Hönes
- Re: [OPSEC] The plan... / adoption of draft-bhati… Joel Jaeggli