[rfc-i] Now tell me how to communicate this as effectively in plaintext

Phillip Hallam-Baker hallam at gmail.com
Thu Apr 26 12:29:04 PDT 2012

On Thu, Apr 26, 2012 at 12:53 PM, Joe Touch <touch at isi.edu> wrote:
> On 4/25/2012 6:57 PM, Phillip Hallam-Baker wrote:
>> Lets consider a different problem.
>> One of our engineers has run an experiment on DNS response times on
>> running browser code. There is a lot of useful information there that
>> is relevant to DANE, PKIX and many other IETF work areas.
>> Wouldn't it be good to be able to present the results as graphs rather
>> than just tables?
> Yes, in a journal paper. Not sure why some of that needs to be in an RFC,
> though.

Because the case for certain protocol changes depends on empirical facts.

> Different publications have different purposes and different audiences. RFCs
> can - and do - refer to other kinds of documents, some even normatively,
> that are not RFCs.

The RFC format has limited the IETF to doing bad engineering devoid of
facts. I don't think that is sustainable.

Website: http://hallambaker.com/

More information about the rfc-interest mailing list