From owner-ietf-ltans@mail.imc.org Mon Mar 10 07:23:54 2008 Return-Path: X-Original-To: ietfarch-ltans-archive-ba2WohFa@core3.amsl.com Delivered-To: ietfarch-ltans-archive-ba2WohFa@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2308C28D092 for ; Mon, 10 Mar 2008 07:23:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.364 X-Spam-Level: X-Spam-Status: No, score=-1.364 tagged_above=-999 required=5 tests=[AWL=1.235, 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 99EbsATsPAG4 for ; Mon, 10 Mar 2008 07:23:53 -0700 (PDT) Received: from balder-227.proper.com (cl-240.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:ef::2]) by core3.amsl.com (Postfix) with ESMTP id 5D63128E18B for ; Mon, 10 Mar 2008 02:33:13 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m2A9DZ26018738 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Mar 2008 02:13:35 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m2A9DZh6018737; Mon, 10 Mar 2008 02:13:35 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:1112:1::20]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m2A9DY8n018731 for ; Mon, 10 Mar 2008 02:13:34 -0700 (MST) (envelope-from root@core3.amsl.com) Received: by core3.amsl.com (Postfix, from userid 0) id A396728E049; Mon, 10 Mar 2008 02:15:04 -0700 (PDT) Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org Cc: ietf-ltans@imc.org From: Internet-Drafts@ietf.org Subject: I-D Action:draft-ietf-ltans-dssc-02.txt Message-Id: <20080310091505.A396728E049@core3.amsl.com> Date: Mon, 10 Mar 2008 02:15:04 -0700 (PDT) Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Long-Term Archive and Notary Services Working Group of the IETF. Title : Data Structure for Security Suitabilities of Cryptographic Algorithms (DSSC) Author(s) : T. Kunz, et al. Filename : draft-ietf-ltans-dssc-02.txt Pages : 38 Date : 2008-03-10 In many application areas it must be possible to prove the existence and integrity of digital signed data. This proof depends on the security suitability of the used cryptographic algorithms. Because algorithms can become weak over the years, it is necessary to periodically evaluate these security suitabilities. When signing or verifying data, these evaluations must be considered. This document specifies a data structure for security suitabilities of cryptographic algorithms which may be automatically interpreted.Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ltans-dssc-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-ltans-dssc-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-03-10020637.I-D@ietf.org> --NextPart-- From owner-ietf-ltans@mail.imc.org Wed Mar 12 13:50:28 2008 Return-Path: X-Original-To: ietfarch-ltans-archive-ba2WohFa@core3.amsl.com Delivered-To: ietfarch-ltans-archive-ba2WohFa@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12ED23A69B3 for ; Wed, 12 Mar 2008 13:50:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.469 X-Spam-Level: X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13] 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 hKQMyEnkS-oS for ; Wed, 12 Mar 2008 13:50:27 -0700 (PDT) Received: from balder-227.proper.com (cl-240.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:ef::2]) by core3.amsl.com (Postfix) with ESMTP id 0856A3A68F6 for ; Wed, 12 Mar 2008 13:50:26 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m2CKWIUj012161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Mar 2008 13:32:19 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m2CKWIvA012160; Wed, 12 Mar 2008 13:32:18 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from scygmxsecs1.cygnacom.com (scygmxsecs1.cygnacom.com [65.242.48.253]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id m2CKWHjh012154 for ; Wed, 12 Mar 2008 13:32:18 -0700 (MST) (envelope-from CWallace@cygnacom.com) Received: (qmail 20924 invoked from network); 12 Mar 2008 20:24:13 -0000 Received: from CWallace@cygnacom.com by scygmxsecs1.cygnacom.com with EntrustECS-Server-7.4;12 Mar 2008 20:24:13 -0000 Received: from unknown (HELO scygexch1.cygnacom.com) (10.60.50.8) by scygmxsecs1.cygnacom.com with SMTP; 12 Mar 2008 20:24:13 -0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: DSSC comment Date: Wed, 12 Mar 2008 16:32:15 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: DSSC comment Thread-Index: AciEgCipvf66xFc0StWT5VW5hKd0Sg== From: "Carl Wallace" To: Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: There was a comment during the meeting regarding DSSC (that was raised last meeting too). Essentially, the question is why aren't parameters associated with a validity period, with a list of parameters appearing under an OID? This would avoid searching the list for RSA, for example, finding multiple entries and having to dig through the parameters until finding an appropriate entry. =20 From owner-ietf-ltans@mail.imc.org Tue Mar 18 02:30:10 2008 Return-Path: X-Original-To: ietfarch-ltans-archive-ba2WohFa@core3.amsl.com Delivered-To: ietfarch-ltans-archive-ba2WohFa@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 957C228C4D7 for ; Tue, 18 Mar 2008 02:30:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.74 X-Spam-Level: X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74] 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 eSz54J5joXLh for ; Tue, 18 Mar 2008 02:30:09 -0700 (PDT) Received: from balder-227.proper.com (cl-240.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:ef::2]) by core3.amsl.com (Postfix) with ESMTP id 98F1B28C4CD for ; Tue, 18 Mar 2008 02:30:09 -0700 (PDT) Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m2I9E7uJ011825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Mar 2008 02:14:07 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m2I9E73F011824; Tue, 18 Mar 2008 02:14:07 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id m2I9E4qF011815 for ; Tue, 18 Mar 2008 02:14:05 -0700 (MST) (envelope-from SusanneO@gmx.de) Received: (qmail 20812 invoked by uid 0); 18 Mar 2008 09:14:03 -0000 Received: from 213.157.4.156 by www036.gmx.net with HTTP; Tue, 18 Mar 2008 10:14:03 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 18 Mar 2008 10:14:03 +0100 From: "Susanne Okunick" In-Reply-To: <47DF85CE.5090803@pawisda.de> Message-ID: <20080318091403.146940@gmx.net> MIME-Version: 1.0 References: <47DF85CE.5090803@pawisda.de> Subject: Re: DSSC comment To: CWallace@cygnacom.com, ietf-ltans@imc.org X-Authenticated: #1167296 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1/DaTM/tgnDdXaE12RxRV9tVQ/FCJzXkYoXIIS5lq vQUG2FoOQk0InKk1xipUaK8OiuA3htbP87jg== Content-Transfer-Encoding: 8bit X-GMX-UID: 6rX5b0+eLi50NOjre2tpEWdrZml1ZNj+ Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: You are right. This would be more efficient. We will think about this issue and perhaps make changes on our structure. Thank you for this comment. Carl Wallace schrieb: > There was a comment during the meeting regarding DSSC (that was raised > last meeting too). Essentially, the question is why aren't parameters > associated with a validity period, with a list of parameters appearing > under an OID? This would avoid searching the list for RSA, for example, > finding multiple entries and having to dig through the parameters until > finding an appropriate entry. > -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m2I9E7uJ011825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Mar 2008 02:14:07 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m2I9E73F011824; Tue, 18 Mar 2008 02:14:07 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id m2I9E4qF011815 for ; Tue, 18 Mar 2008 02:14:05 -0700 (MST) (envelope-from SusanneO@gmx.de) Received: (qmail 20812 invoked by uid 0); 18 Mar 2008 09:14:03 -0000 Received: from 213.157.4.156 by www036.gmx.net with HTTP; Tue, 18 Mar 2008 10:14:03 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 18 Mar 2008 10:14:03 +0100 From: "Susanne Okunick" In-Reply-To: <47DF85CE.5090803@pawisda.de> Message-ID: <20080318091403.146940@gmx.net> MIME-Version: 1.0 References: <47DF85CE.5090803@pawisda.de> Subject: Re: DSSC comment To: CWallace@cygnacom.com, ietf-ltans@imc.org X-Authenticated: #1167296 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1/DaTM/tgnDdXaE12RxRV9tVQ/FCJzXkYoXIIS5lq vQUG2FoOQk0InKk1xipUaK8OiuA3htbP87jg== Content-Transfer-Encoding: 8bit X-GMX-UID: 6rX5b0+eLi50NOjre2tpEWdrZml1ZNj+ Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: You are right. This would be more efficient. We will think about this issue and perhaps make changes on our structure. Thank you for this comment. Carl Wallace schrieb: > There was a comment during the meeting regarding DSSC (that was raised > last meeting too). Essentially, the question is why aren't parameters > associated with a validity period, with a list of parameters appearing > under an OID? This would avoid searching the list for RSA, for example, > finding multiple entries and having to dig through the parameters until > finding an appropriate entry. > -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m2CKWIUj012161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Mar 2008 13:32:19 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m2CKWIvA012160; Wed, 12 Mar 2008 13:32:18 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from scygmxsecs1.cygnacom.com (scygmxsecs1.cygnacom.com [65.242.48.253]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id m2CKWHjh012154 for ; Wed, 12 Mar 2008 13:32:18 -0700 (MST) (envelope-from CWallace@cygnacom.com) Received: (qmail 20924 invoked from network); 12 Mar 2008 20:24:13 -0000 Received: from CWallace@cygnacom.com by scygmxsecs1.cygnacom.com with EntrustECS-Server-7.4;12 Mar 2008 20:24:13 -0000 Received: from unknown (HELO scygexch1.cygnacom.com) (10.60.50.8) by scygmxsecs1.cygnacom.com with SMTP; 12 Mar 2008 20:24:13 -0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: DSSC comment Date: Wed, 12 Mar 2008 16:32:15 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: DSSC comment Thread-Index: AciEgCipvf66xFc0StWT5VW5hKd0Sg== From: "Carl Wallace" To: Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: There was a comment during the meeting regarding DSSC (that was raised last meeting too). Essentially, the question is why aren't parameters associated with a validity period, with a list of parameters appearing under an OID? This would avoid searching the list for RSA, for example, finding multiple entries and having to dig through the parameters until finding an appropriate entry. =20 Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m2A9DZ26018738 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Mar 2008 02:13:35 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m2A9DZh6018737; Mon, 10 Mar 2008 02:13:35 -0700 (MST) (envelope-from owner-ietf-ltans@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-ltans@mail.imc.org using -f Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:1112:1::20]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m2A9DY8n018731 for ; Mon, 10 Mar 2008 02:13:34 -0700 (MST) (envelope-from root@core3.amsl.com) Received: by core3.amsl.com (Postfix, from userid 0) id A396728E049; Mon, 10 Mar 2008 02:15:04 -0700 (PDT) Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org Cc: ietf-ltans@imc.org From: Internet-Drafts@ietf.org Subject: I-D Action:draft-ietf-ltans-dssc-02.txt Message-Id: <20080310091505.A396728E049@core3.amsl.com> Date: Mon, 10 Mar 2008 02:15:04 -0700 (PDT) Sender: owner-ietf-ltans@mail.imc.org Precedence: bulk List-Archive: List-Unsubscribe: List-ID: --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Long-Term Archive and Notary Services Working Group of the IETF. Title : Data Structure for Security Suitabilities of Cryptographic Algorithms (DSSC) Author(s) : T. Kunz, et al. Filename : draft-ietf-ltans-dssc-02.txt Pages : 38 Date : 2008-03-10 In many application areas it must be possible to prove the existence and integrity of digital signed data. This proof depends on the security suitability of the used cryptographic algorithms. Because algorithms can become weak over the years, it is necessary to periodically evaluate these security suitabilities. When signing or verifying data, these evaluations must be considered. This document specifies a data structure for security suitabilities of cryptographic algorithms which may be automatically interpreted.Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ltans-dssc-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-ltans-dssc-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-03-10020637.I-D@ietf.org> --NextPart--