Re: WG Last call: draft-ietf-ipsec-isakmp-gss-auth-05.txt
Sheela Rowles <srowles@cisco.com> Wed, 05 April 2000 20:00 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 NAA04790; Wed, 5 Apr 2000 13:00:03 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id OAA09857 Wed, 5 Apr 2000 14:52:51 -0400 (EDT)
From: Sheela Rowles <srowles@cisco.com>
Message-Id: <200004051858.LAA23758@sigma.cisco.com>
Subject: Re: WG Last call: draft-ietf-ipsec-isakmp-gss-auth-05.txt
To: paul.hoffman@vpnc.org
Date: Wed, 05 Apr 2000 11:58:16 -0700
Cc: srowles@cisco.com, ddp@network-alchemy.com, briansw@microsoft.com, tytso@valinux.com, ipsec@lists.tislabs.com
In-Reply-To: <4.3.2.20000404150225.00d30d70@mail.vpnc.org> from "Paul Hoffman" at Apr 04, 2000 03:04:55 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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. Paul, Who would make this decision - that the spec is open for change vs being closed? thanks, Sheela > > >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