[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ESP transform with RC5
The IETF process must support the definition of technologies that
can e produced by vendors for a profit.
Since this is an informational RFC in any event, it doesn't matter
much. RFC 1602 puts certain restrictions on standards-track RFCs;
it says nothing whatsoever about patents and non-standards documents.
It's also worth noting that RC5 poses some interesting technical issues.
For example, it is parameterized, and none of the key management mechanisms
we are considering seem to support that. Possibly, the parameters could
be encoded as part of the key -- but we're moving down a track in which
keys are true-random numbers. Besides, it may be necessary to negotiate
some of the parameters under certain circumstances -- some folks may only
have 40-bit RC5 implementations available to them, for the usual obvious
reasons.