[893] in Kerberos_V5_Development
Re: Proposed Kerberos V5 Password Changing Algorithm
daemon@ATHENA.MIT.EDU (Theodore Ts'o)
Tue Mar 14 15:14:01 1995
Date: Tue, 14 Mar 1995 15:13:49 +0500
From: Theodore Ts'o <tytso@MIT.EDU>
To: John Gilmore <gnu@cygnus.com>
Cc: "Theodore Ts'o" <tytso@MIT.EDU>, krbdev@MIT.EDU
In-Reply-To: John Gilmore's message of Tue, 14 Mar 1995 12:01:50 -0800,
<199503142001.MAA27996@cygnus.com>
Date: Tue, 14 Mar 1995 12:01:50 -0800
From: John Gilmore <gnu@cygnus.com>
We're defining a new protocol. There's no point in making options in
it. If you think MIME is the way to go, let's make it standard.
Document it clearly so that "simple" clients can just check or skip
the MIME headers and printf the message. It's not clear to me what
a "complex" client would do -- fork off a copy of metamail to print
an error message? That sounds highly error-prone to me!
MIME is only really needed to support internationalization, as an
adjunct to supporting multi-lingual support. We need something a
kerberos password changing standard out fast, and trying to deal with
internationalization issues is not how you get something out fast. In
any cavse, until the export issues are settled, in my opinion I18N
issues are a waste of time anyway. For that reason, I don't intend to
implement these in the first release of the reference implementation.
On the other hand, I do want to leave room for future implementations to
handle the I18N issues. You're right that the MIME specification
probably needs to be nailed down better --- I'm not a MIME expert,
though. If we can't nail it down in time, I may simply yank all mention
of MIME and Language negotiations from the specification for now.
- Ted
