On Thu, 25 Aug 2005, Bill Sommerfeld wrote:
[normative specification is in the RFC series, vs. somewhere else and
just copied or described in an info/exp RFC]
At least to me, these two categories should be treated differently.
Can you explain why?
Cryptographic algorithms are, in general, har
--On 24. august 2005 17:24 -0400 Sam Hartman <[EMAIL PROTECTED]> wrote:
iesg> It is customary to include normative references to
iesg> informational documents describing cryptographic algorithms.
iesg> However the procedures of RFC 3967 require that this
iesg> normative referen
On Thu, 2005-08-25 at 06:48, Pekka Savola wrote:
> I think there needs to be separation of two different kinds of
> documents,
>
> 1) informational, because the normative specification is elsewhere
> (usually another standards organization) and we could reference the
> normative spec directly
On Wed, 24 Aug 2005, Bill Sommerfeld wrote:
In particular, there is a long-established tradition of specifying
cryptographic algorithms as "Informational" documents, and referring to
them from standards-track documents.
I think there needs to be separation of two different kinds of
documents,
> "John" == John C Klensin <[EMAIL PROTECTED]> writes:
John> --On Wednesday, August 24, 2005 17:24 -0400 Sam Hartman
John> <[EMAIL PROTECTED]> wrote:
>>> "iesg" == The IESG <[EMAIL PROTECTED]> writes:
>>
iesg> This last call is being reissued because this
>> docume
On Wed, 2005-08-24 at 19:14, John C Klensin wrote:
> Even if one believes that it is desirable, 3967 already weakens
> traditional norms for documents on the IETF standards track. A
> suggestion that further weakening is needed definitely calls for
> some discussion, at least IMO.
There is con
--On Wednesday, August 24, 2005 17:24 -0400 Sam Hartman
<[EMAIL PROTECTED]> wrote:
"iesg" == The IESG <[EMAIL PROTECTED]> writes:
iesg> This last call is being reissued because this
document iesg> contains a normative reference to an
informational RFC:
iesg> RFC 2144 The CAST-
> "iesg" == The IESG <[EMAIL PROTECTED]> writes:
iesg> This last call is being reissued because this document
iesg> contains a normative reference to an informational RFC:
iesg> RFC 2144 The CAST-128 Encryption Algorithm. C. Adams. May
iesg> 1997.
iesg> It is customary to
