Re: Diagrams (Was RFCs should be distributed in XML)

[Marshall Eubanks <tme at multicasttech.com>]

For true archival storage, nothing can beat the elegance and  
simplicity of engravings on stone.

I believe that this site in Georgia has plenty  of room for even the  
most complicated RFC's :

http://www.cviog.uga.edu/Projects/gainfo/statues/guidestones.htm

I had occasion to discuss this thread recently with some  
participants, and we agreed that this  seems to be the direction it's  
heading.

I suspect it would also help to keep protocols simple.

(Financial disclosure : I have  relatives who own quarries in this  
area.)

Regards
Marshall Eubanks

On Nov 17, 2005, at 8:30 AM, Masataka Ohta wrote:

> Yaakov Stein wrote:
>
> > > It's good that protocols needing more than 72 ASCII characters are
> > > forbidden.
>
> > Just imagine what elegantly simple protocols we would have
> > if we required the descriptions to be in Morse code.
>
> Good idea.
>
> It's a better approach to enforce much simpler protocols.
>
> 						Masataka Ohta
>
>
> _______________________________________________
> Ietf mailing list
> Ietf at ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf