IETF Logo Mail Archive

Re: [SPKM] Interoperability

Nicolas Williams <Nicolas.Williams@sun.com> Tue, 31 October 2006 21:44 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf1PR-0002WQ-Go; Tue, 31 Oct 2006 16:44:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gf1Or-0002Eg-Hq for spkm@ietf.org; Tue, 31 Oct 2006 16:44:01 -0500
Received: from nwkea-mail-4.sun.com ([192.18.42.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gf1CN-0002dL-Od for spkm@ietf.org; Tue, 31 Oct 2006 16:31:09 -0500
Received: from centralmail4brm.central.Sun.COM ([129.147.62.198]) by nwkea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k9VLV7AK009425 for <spkm@ietf.org>; Tue, 31 Oct 2006 13:31:07 -0800 (PST)
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by centralmail4brm.central.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL, v2.2) with ESMTP id k9VLV6cx010626 for <spkm@ietf.org>; Tue, 31 Oct 2006 14:31:06 -0700 (MST)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.13.6+Sun/8.13.6) with ESMTP id k9VLV6e7022398; Tue, 31 Oct 2006 15:31:06 -0600 (CST)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.13.6+Sun/8.13.6/Submit) id k9VLV6gK022397; Tue, 31 Oct 2006 15:31:06 -0600 (CST)
Date: Tue, 31 Oct 2006 15:31:06 -0600
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [SPKM] Interoperability
Message-ID: <20061031213105.GV28107@binky.Central.Sun.COM>
References: <tsl4ptkthkp.fsf@cz.mit.edu> <20061031211246.GT28107@binky.Central.Sun.COM> <tsliri0rxo7.fsf@cz.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <tsliri0rxo7.fsf@cz.mit.edu>
User-Agent: Mutt/1.5.7i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: spkm@ietf.org
X-BeenThere: spkm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Low Infrastructure Public Key GSS mechanism <spkm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/spkm>, <mailto:spkm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/spkm>
List-Post: <mailto:spkm@ietf.org>
List-Help: <mailto:spkm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/spkm>, <mailto:spkm-request@ietf.org?subject=subscribe>
Errors-To: spkm-bounces@ietf.org

On Tue, Oct 31, 2006 at 04:19:04PM -0500, Sam Hartman wrote:
> >>>>> "Nicolas" == Nicolas Williams <Nicolas.Williams@sun.com> writes:
> 
>     Nicolas> On Tue, Oct 31, 2006 at 02:23:50PM -0500, Sam Hartman
>     Nicolas> wrote:
>     >> * When will we get a spec out?  How long will the market wait?
>     >> Sometimes, you have to accept that the market will deploy
>     >> something and you have little influence on it.  In those cases
>     >> it's better to write a compelling spec and hope that people
>     >> will migrate.  Other times, if you can stretch to meet market
>     >> timing, you can avoid the market deploying something that does
>     >> not meet your spec.  That is very desirable.
> 
>     Nicolas> If we cannot get a spec that will meet our needs in time
>     Nicolas> for the market then the proposed protocol could go to
>     Nicolas> Informational and a spec that does meet our needs can
>     Nicolas> later go to Proposed-Standard, using a different OID.
> 
> Yes.
> I don't consider it a failure if the market has to do something while we work on a spec.
> 
> I will not sponsor this as informational, but nothing stops the
> authors from going to the rfc editor.

Right.  I think this is a possible outcome of the BoF.

Nico
-- 

_______________________________________________
SPKM mailing list
SPKM@ietf.org
https://www1.ietf.org/mailman/listinfo/spkm

v2.23.0 | Report a Bug | By Email