RFC 4101 on Writing Protocol Models

rfc-editor@rfc-editor.org Mon, 27 June 2005 22:18 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn1wJ-00037t-3E; Mon, 27 Jun 2005 18:18:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dn1wG-00037l-5s for ietf-announce@megatron.ietf.org; Mon, 27 Jun 2005 18:18:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02616 for <ietf-announce@ietf.org>; Mon, 27 Jun 2005 18:18:44 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dn2LT-00028e-9T for ietf-announce@ietf.org; Mon, 27 Jun 2005 18:44:52 -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 j5RMIMt03580; Mon, 27 Jun 2005 15:18:22 -0700 (PDT)
Message-Id: <200506272218.j5RMIMt03580@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: Mon, 27 Jun 2005 15:18:22 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4101 on Writing Protocol Models
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

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


        RFC 4101

        Title:      Writing Protocol Models
        Author(s):  E. Rescorla, IAB
        Status:     Informational
        Date:       June 2005
        Mailbox:    ekr@rtfm.com, iab@iab.org
        Pages:      22
        Characters: 47287
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-iab-model-03.txt

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


The IETF process depends on peer review.  However, IETF documents
are generally written to be useful for implementors, not
reviewers.  In particular, while great care is generally taken to
provide a complete description of the state machines and bits on
the wire, this level of detail tends to get in the way of initial
understanding.  This document describes an approach for providing
protocol "models" that allow reviewers to quickly grasp the essence
of a system.

This document is a product of the Internet Architecture Board.

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/rfc4101.txt"><ftp://ftp.isi.edu/in-notes/rfc4101.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce