From keyprov-bounces@ietf.org Wed Apr 18 03:50:40 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1He4w4-0004M8-NJ; Wed, 18 Apr 2007 03:50:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1He4w3-0004Lu-LM for keyprov@ietf.org; Wed, 18 Apr 2007 03:50:39 -0400 Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1He4w2-0002UP-DR for keyprov@ietf.org; Wed, 18 Apr 2007 03:50:39 -0400 Received: (qmail invoked by alias); 18 Apr 2007 07:50:37 -0000 Received: from socks1.netz.sbs.de (EHLO [192.35.17.26]) [192.35.17.26] by mail.gmx.net (mp021) with SMTP; 18 Apr 2007 09:50:37 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1/6k7NF0DX6/xbap+f9X33QaSw/x4SJ0Ewx9zqmFu lwuH7TzwnoauMB Message-ID: <4625CDCB.9080404@gmx.net> Date: Wed, 18 Apr 2007 09:50:35 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: keyprov@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0f1ff0b0158b41ac6b9548d0972cdd31 Subject: [KEYPROV] test X-BeenThere: keyprov@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Provisioning of Symmetric Keys \(keyprov\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: keyprov-bounces@ietf.org please ignore. _______________________________________________ KEYPROV mailing list KEYPROV@ietf.org https://www1.ietf.org/mailman/listinfo/keyprov From keyprov-bounces@ietf.org Wed Apr 18 05:25:50 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1He6QA-0003lZ-6w; Wed, 18 Apr 2007 05:25:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1He6Q9-0003lD-30 for keyprov@ietf.org; Wed, 18 Apr 2007 05:25:49 -0400 Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1He6Q7-000103-Pk for keyprov@ietf.org; Wed, 18 Apr 2007 05:25:49 -0400 Received: (qmail invoked by alias); 18 Apr 2007 09:25:46 -0000 Received: from socks1.netz.sbs.de (EHLO [192.35.17.26]) [192.35.17.26] by mail.gmx.net (mp002) with SMTP; 18 Apr 2007 11:25:46 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX18DSOR7QYYDdF0Kgx7vO0ghbq3ahA1lBWyTjjr60b 7sxRVFtwYWLpmQ Message-ID: <4625E41A.90607@gmx.net> Date: Wed, 18 Apr 2007 11:25:46 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: keyprov@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Subject: [KEYPROV] Meeting Minutes X-BeenThere: keyprov@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Provisioning of Symmetric Keys \(keyprov\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: keyprov-bounces@ietf.org Hi all, here are the meeting minutes from the IETF #68 KEYPROV working group meeting: http://www3.ietf.org/proceedings/07mar/minutes/keyprov.txt Please take a look at them. Ciao Hannes _______________________________________________ KEYPROV mailing list KEYPROV@ietf.org https://www1.ietf.org/mailman/listinfo/keyprov From keyprov-bounces@ietf.org Fri Apr 20 11:24:07 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Heuxy-0007a8-NF; Fri, 20 Apr 2007 11:24:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Heuxx-0007a3-Lu for keyprov@ietf.org; Fri, 20 Apr 2007 11:24:05 -0400 Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Heuxv-0007UJ-4M for keyprov@ietf.org; Fri, 20 Apr 2007 11:24:05 -0400 Received: (qmail invoked by alias); 20 Apr 2007 15:24:01 -0000 Received: from socks1.netz.sbs.de (EHLO [192.35.17.26]) [192.35.17.26] by mail.gmx.net (mp002) with SMTP; 20 Apr 2007 17:24:01 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX18UoqQk5IYUukAte8mKjTkp63QryXJJhl/GAzRWPG eCjQKHmDPfCeRe Message-ID: <4628DB11.8060704@gmx.net> Date: Fri, 20 Apr 2007 17:24:01 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: keyprov@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: [KEYPROV] Status Update X-BeenThere: keyprov@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Provisioning of Symmetric Keys \(keyprov\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: keyprov-bounces@ietf.org Hi all, I would like to give you a brief status update since we finally got this mailing list up and running. It took some time... At the IETF#68 KEYPROV meeting Andrea and Ming gave presentations about their proposals. You can find their slides at: https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=68 (search for KEYPROV) Andrea and Ming also brainstormed about the idea of merging the two proposals. You can find their thoughts in this presentation: http://www3.ietf.org/proceedings/07mar/slides/keyprov-0/sld1.htm A number of open issues surfaced and these issues will be discussed in the next few weeks. During the IETF#68 working group meeting we, Phillip and myself, indicated that we would like to schedule some conference calls to have the possibility to speak about open issues. Since we have to announce these conference calls ahead of time I would like todo this with a subsequent mail. Ciao Hannes & Phillip _______________________________________________ KEYPROV mailing list KEYPROV@ietf.org https://www1.ietf.org/mailman/listinfo/keyprov From keyprov-bounces@ietf.org Fri Apr 20 11:39:04 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HevCS-00051h-0t; Fri, 20 Apr 2007 11:39:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HevCQ-0004vq-V2 for keyprov@ietf.org; Fri, 20 Apr 2007 11:39:02 -0400 Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HevCP-0002dI-GF for keyprov@ietf.org; Fri, 20 Apr 2007 11:39:02 -0400 Received: (qmail invoked by alias); 20 Apr 2007 15:39:00 -0000 Received: from socks1.netz.sbs.de (EHLO [192.35.17.26]) [192.35.17.26] by mail.gmx.net (mp017) with SMTP; 20 Apr 2007 17:39:00 +0200 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1+iswhbgzai8029KE0fKyh1FVXHWEMPC+m1Y0xPCe bFladCdX1eQGxN Message-ID: <4628DE94.6080502@gmx.net> Date: Fri, 20 Apr 2007 17:39:00 +0200 From: Hannes Tschofenig User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: keyprov@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Subject: [KEYPROV] Announcement for Phone Conference Calls X-BeenThere: keyprov@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Provisioning of Symmetric Keys \(keyprov\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: keyprov-bounces@ietf.org Hi all, we would like to have the possibility of scheduling phone conference calls. In order to do so we have to announce them ahead of time. Please let us know your availability either by adding your name to the subsequent Wiki page or by sending us a mail: http://www.tschofenig.priv.at/twiki/bin/view/KeyProv/PhoneConferences To edit the Wiki page please use the following credentials: Username: KeyprovGroup Passwd: keyprov-ietf We suggest to schedule the phone conference at 11:00 EDT = 17:00 CEST = 15:00 UTC. For the duration I anticipate roughly an hour. Please speak up if this is not convenient for you. We will do this work according to the rules outlined in RFC 2418 and http://www.ietf.org/IESG/STATEMENTS/Design-Teams.txt A list of discussion topics will be available before the phone conference starts. Deadline to respond: 30th April 2007 Ciao Hannes & Phillip _______________________________________________ KEYPROV mailing list KEYPROV@ietf.org https://www1.ietf.org/mailman/listinfo/keyprov From keyprov-bounces@ietf.org Fri Apr 20 19:06:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hf2Bq-0005BS-Lb; Fri, 20 Apr 2007 19:06:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hf2Bp-0005A6-0D for keyprov@ietf.org; Fri, 20 Apr 2007 19:06:53 -0400 Received: from gateway1.rsasecurity.com ([216.162.240.250]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Hf2Bn-0007RG-Nk for keyprov@ietf.org; Fri, 20 Apr 2007 19:06:52 -0400 Received: from hyperion.rsasecurity.com by gateway1.rsasecurity.com via smtpd (for ietf-mx.ietf.ORG [156.154.16.150]) with SMTP; Fri, 20 Apr 2007 19:06:51 -0400 Received: from sdtihq24.securid.com (sdtihq24.na.rsa.net [10.100.8.152]) by hyperion.na.rsa.net (MOS 3.8.3-GA) with ESMTP id DBS44199; Fri, 20 Apr 2007 19:09:52 +0500 (GMT-5) Received: from rsana-ex-hq1.NA.RSA.NET (rsana-ex-hq1.na.rsa.net [10.100.8.50]) by sdtihq24.securid.com (8.12.10/8.12.9) with ESMTP id l3KN6oIA019421 for ; Fri, 20 Apr 2007 19:06:50 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 20 Apr 2007 19:06:49 -0400 Message-ID: <017630AA6DF2DF4EBC1DD4454F8EE2970AA66863@rsana-ex-hq1.NA.RSA.NET> Thread-Topic: Protocol merge options thread-index: AceDoJOgXYU8+w1cRyu8SMe7VHPt/g== From: "Doherty, Andrea" To: X-Spam-Score: 0.1 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Subject: [KEYPROV] Protocol merge options X-BeenThere: keyprov@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Provisioning of Symmetric Keys \(keyprov\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: keyprov-bounces@ietf.org All, During the IETF-68 meeting, Mingliang and I presented options for merging three explicit DSKPP capabilities into CT-KIP (ref. slides 5-8 in http://www3.ietf.org/proceedings/07mar/slides/keyprov-0/sld1.htm). Before creating a converged protocol specification, there are open issues that require discussion and resolution (noted in Slide 10 of reference above). =20 I'll present two of those issues here to stimulate discussion: 1. Guiding principle for strongly typing request and response parameters a. Avoid use of "any" types if a strong type declaration is possible PROS: =20 * "any" makes schema validation and code automation difficult. =20 * Payload is currently a generic type, which will make interop hard because the schema cannot specify it while such information may be specified through a profile. CONS:=20 * The "any" type gives flexibility (alternatively, the protocol will be less flexible and less general if strong type declarations are enforced) * CT-KIP already uses "processContents=3Dstrict" to ensure a schema is in place.=20 * "any" is effectively only used in CT-KIP for the payload=20 b. How would can future extensibility for the payload type be provided without "any"? 2. Keep the core protocol simple and flexible, allowing organizations to define their own extensions a. One suggestion was to reserve protocol extensions for non-standard features or provider specific information. For example, since payload is used in core protocol, a proposal is to have the request and response payload explictly declared as part of the standard body instead of using an extension. PROS: This is one option for addressing the interoperability concern. CONS: =20 * Extensions do give flexibility. For example, consider their well-known usage with X.509. * There are no "critical" extensions in CT-KIP. b. A better way to ensure interoperability could be to extend the algorithms and capabilities negotiation between the client and server to include the payload format. I invite you to comment on the above. Andrea _______________________________________________ KEYPROV mailing list KEYPROV@ietf.org https://www1.ietf.org/mailman/listinfo/keyprov