OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: FW: padata-type ?

Title: FW: padata-type ?


I asked on IETF kerberos WG about referencing rfc1510. The concensus is that we should not since RFC number will change fairly soon when IESG approve the Kerberos 5, Specification 2 (aka clarifications).

I just got your email which suggests you have chosen to refer to it as Kerberos anyway, so this email is just FYI.


-----Original Message-----
From: Jeffrey Hutzelman [mailto:jhutz@cmu.edu]
Sent: 12 April 2004 20:28
To: Tim Alsop; Sam Hartman
Cc: ietf-krb-wg@anl.gov
Subject: RE: padata-type ?

On Monday, April 12, 2004 18:15:23 +0100 Tim Alsop
<Tim.Alsop@CyberSafe.Ltd.UK> wrote:

> The reason for asking is that I am working with another standard (not
> IETF controlled) that will make reference to the Kerberos standard, so I
> want to make sure if we mention rfc1510 that this rfc number is going to
> be the correct rfc in the future. If I understand you correctly, a new
> number will be allocated when clarifications is approved by IESG so we
> should make this clear in our documentation.

That is correct.  RFC's are immutable; once published, an RFC never changes
(the rfc-editor does maintain a list of errata in published RFC's at
http://www.rfc-editor.org/errata.html, but the originial documents are
never modified).

RFC1510 describes Kerberos V, Specification 1.

Once approved, kerberos-clarifications will be published as a new RFC; this
will obsolete RFC1510 and (in combination with the crypto and AES
documents) will describe Kerberos V, Specification 2.

In most cases it is desirable in a standards context for normative
references to be to a particular version of the specification.  For IETF
standards, you can do this by referring to a particular RFC.  In a few
cases, you actually want a reference to "the current version", whatever
that happens to be.  The IETF way to do this is to refer to an STD number;
however, these numbers are currently assigned only to full Internet

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
   Sr. Research Systems Programmer
   School of Computer Science - Research Computing Facility
   Carnegie Mellon University - Pittsburgh, PA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]