> why the implementation description has to be an RFC? clog up the RFCs because this is engineering, not academic research; no requirement for original contribution. having the workings of a protocol implementation well documented helps others interoperate, gives them ideas for their own implementations, ... we have a long trail of vendorX's implementation of coffee ice cream. it is helpful. < insert snark comparison to 342 'bright ideas' about how to get one's name on an rfc for useless work > randy
