[rfc-i] [IAB Trac] #266: Requirement for "Clear Printing"
mcr+ietf at sandelman.ca
Fri Feb 15 12:55:43 PST 2013
>>>>> "Ted" == Ted Lemon <mellon at fugue.com> writes:
Ted> Just as a counterpoint, I always work from the electronic
Ted> version of the RFC (nowadays--I used to use paper just like
Ted> you), and I refer to parts of drafts by section number and
Ted> paragraph, not by page number, because I don't feel safe in
Ted> assuming that the person with whom I am communicating is
When commenting, I also do this, but also for IDs, because repaging
after editing someone else's comments might move things.
I'd be *happiest* if our HTML output format had lots and lots of
When writing code, I tend to print important parts, such as packet
formats, and I tend to glue them to the wall. Back in 1998, some
of us thought that http://datatracker.ietf.org/doc/draft-nossik-pax-pdl/
would have been useful to describe packet formats.
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr at sandelman.ca http://www.sandelman.ca/ | ruby on rails [
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 307 bytes
Desc: not available
More information about the rfc-interest