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

To: "Stewart Bryant" <stbryant at cisco.com>, "Masataka Ohta" <mohta at necom830.hpcl.titech.ac.jp>, <ietf at ietf.org>
Subject: RE: Diagrams (Was RFCs should be distributed in XML)
From: "Yaakov Stein" <yaakov_s at rad.com>
Date: Thu, 17 Nov 2005 08:48:07 +0200
Cc:
List-help: <mailto:ietf-request@ietf.org?subject=help>
List-id: IETF-Discussion <ietf.ietf.org>
List-post: <mailto:ietf@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
Sender: ietf-bounces at ietf.org
Thread-index: AcXqvUuFE3TcD79aT8acKoxewzvFwAAhWIKQ
Thread-topic: Diagrams (Was RFCs should be distributed in XML)

 
>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.

Y(J)S

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

Follow-Ups:
- Re: Diagrams (Was RFCs should be distributed in XML)
  - From: Masataka Ohta

Prev by Date: Re: On revising 3777 as in draft-klensin-recall-rev-00
Next by Date: Re: On revising 3777 as in draft-klensin-recall-rev-00
Previous by thread: RE: Diagrams (Was RFCs should be distributed in XML)
Next by thread: Re: Diagrams (Was RFCs should be distributed in XML)
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

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

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.