RFC 3930 on The Protocol versus Document Points of View in Computer Protocols

rfc-editor@rfc-editor.org Fri, 22 October 2004 23:06 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11048; Fri, 22 Oct 2004 19:06:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL8hO-0008Ks-Gv; Fri, 22 Oct 2004 19:19:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL7zE-0006eC-E7; Fri, 22 Oct 2004 18:34:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL7oW-0003o4-1f for ietf-announce@megatron.ietf.org; Fri, 22 Oct 2004 18:23:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02961 for <ietf-announce@ietf.org>; Fri, 22 Oct 2004 18:23:07 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL81J-0005k8-So for ietf-announce@ietf.org; Fri, 22 Oct 2004 18:36:29 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i9MMMTi14082; Fri, 22 Oct 2004 15:22:29 -0700 (PDT)
Message-Id: <200410222222.i9MMMTi14082@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 22 Oct 2004 15:22:29 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: rfc-editor@rfc-editor.org
Subject: RFC 3930 on The Protocol versus Document Points of View in Computer Protocols
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4

A new Request for Comments is now available in online RFC libraries.


        RFC 3930

        Title:      The Protocol versus Document Points of View in
                    Computer Protocols
        Author(s):  D. Eastlake 3rd
        Status:     Informational
        Date:       October 2004
        Mailbox:    Donald.Eastlake@motorola.com
        Pages:      15
        Characters: 36892
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-eastlake-proto-doc-pov-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3930.txt


This document contrasts two points of view: the "document" point of
view, where digital objects of interest are like pieces of paper
written and viewed by people, and the "protocol" point of view where
objects of interest are composite dynamic network messages.  Although
each point of view has a place, adherence to a document point of view
can be damaging to protocol design.  By understanding both points of
view, conflicts between them may be clarified and reduced.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc3930.txt"><ftp://ftp.isi.edu/in-notes/rfc3930.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce