RFC1698 on ThinOSI Upper-Layers Cookbook (fwd)

[Peter Furniss <[e-mail]>]

In case you missed it, the thinosi cookbook has now been published,
over seven months after publication was requested. The delay was
caused by a change of Area Director (to the fourth AD in our
lifetime), her understandable delay in reviewing it (since she was
also IPng AD) and get in the queue behind the assigned numbers RFC.

Still, it is finally out.


Forwarded message:
From [e-mail] Tue Oct 25 23:04:06 1994
Via: UK.AC.NSFNET-RELAY; Tue, 25 Oct 94  22:03 GMT
Message-Id: <[e-mail]>
To: IETF-Announce:;@IETF.CNRI.Reston.VA.US
Subject: RFC1698 on ThinOSI Upper-Layers Cookbook
Cc: [e-mail]
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 25 Oct 94 13:42:40 PDT
Original-Sender: [e-mail]
From: "Joyce K. Reynolds" <[e-mail]>
Sender: [e-mail]


--NextPart


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


        RFC 1698:

        Title:      Octet Sequences for Upper-Layer OSI
                    to Support Basic Communications Applications
        Author:     P. Furniss
        Mailbox:    [e-mail]
        Pages:      29
        Characters: 67,433
        Updates/Obsoletes:  none


This RFC states particular octet sequences that comprise the OSI
upper-layer protocols (Session, Presentation and ACSE) when used to
support applications with "basic communications requirements". These
include OSI application protocols such as X.400 P7 and Directory
Access Protocol, and "migrant" protocols, originally defined for use
over other transports.  This RFC is the product of the Minimal OSI
Upper-Layers Working Group of the IETF.

This memo provides information for the Internet community.  This memo
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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="[e-mail]"

Content-Type: text/plain
Content-ID: <[e-mail]>

SEND /rfc/rfc1698.txt

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc1698.txt";
        site="ds.internic.net";
        access-type="anon-ftp";
        directory="rfc"

Content-Type: text/plain
Content-ID: <[e-mail]>

--OtherAccess--
--NextPart--