Re: WG Last call: draft-ietf-ipsec-isakmp-gss-auth-05.txt
Paul Hoffman <paul.hoffman@vpnc.org> Tue, 04 April 2000 23:03 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id QAA06695; Tue, 4 Apr 2000 16:03:39 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id RAA04647 Tue, 4 Apr 2000 17:58:43 -0400 (EDT)
Message-Id: <4.3.2.20000404150225.00d30d70@mail.vpnc.org>
X-Sender: phoffvpnc@mail.vpnc.org
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Tue, 04 Apr 2000 15:04:55 -0700
To: Sheela Rowles <srowles@cisco.com>, ddp@network-alchemy.com, briansw@microsoft.com
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: WG Last call: draft-ietf-ipsec-isakmp-gss-auth-05.txt
Cc: tytso@valinux.com, srowles@cisco.com, ipsec@lists.tislabs.com
In-Reply-To: <200003310157.RAA26908@sigma.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
At 05:57 PM 3/30/00 -0800, Sheela Rowles wrote: >My understanding is that the isakmp-gss draft is an informational draft, >that basically documents one vendor's implementation (Microsoft). >As it turns out, we are also implementing the draft (we = Cisco), >and so wondered if this should be considered as a future RFC rather >than an informational draft. Is there anyone else out there >who plans to implement this? The fact that more than one company is implementing from the draft is not the deciding factor for whether it should go on standards track. If the spec is not open to change (such as if it is a description of how the originating company implemented the protocol), it should be an Informational RFC. If the spec is open for change and better design, it might be appropriate on standards track. >In any case, since this is an informational draft (documenting >Microsoft's work in this area, the draft needs to be modified >to reflect some differences between the draft and Microsoft's >current implementation: Exactly right. Anything in the spec that doesn't match Microsoft's implementation should be fixed during this last-call phase. --Paul Hoffman, Director --VPN Consortium
- WG Last call: draft-ietf-ipsec-isakmp-gss-auth-05… Sheela Rowles
- Re: WG Last call: draft-ietf-ipsec-isakmp-gss-aut… Paul Hoffman
- Re: WG Last call: draft-ietf-ipsec-isakmp-gss-aut… Sheela Rowles
- Re: WG Last call: draft-ietf-ipsec-isakmp-gss-aut… Paul Hoffman