RFC 453 UNKNOWN EMAIL · MEETING

Meeting announcement to discuss a network mail system

An announcement of a meeting to discuss how network mail should work.

On rfc-editor.org ↗
PUBLISHED
February 1973
AUTHORS
M.D. Kudlick
STREAM
Legacy
DOI
10.17487/RFC0453

RFC text

Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                                 Michael D. Kudlick
RFC # 453                                             SRI-ARC
NIC # 14317                                           February 7, 1973


         Meeting Announcement to Discuss a Network Mail System

Purpose

The purpose of this RFC is to announce a meeting at SRI-ARC on the
Network Mail problem discussed at the January 1973 Principal
Investigators' Meeting in San Diego.

We have set the meeting for Thursday, February 22, 1973, at 8:30 AM in
the SRI-ARC conference room.  If a second day is is needed, Friday would
be used.

The agenda will include a discussion of the problem, and a discussion of
alternate solutions.

The goal of the meeting is to produce a clear definition of what the
solution ought to be, what steps have to be taken, and who should do
what.

The results of the meeting will be published as an RFC for further
dialogue, as is done with other suggested protocols.

Aspects of the Problem

There are already several subsystems existing on the Network whose
function is to send and receive mail.

The principal problem is to coordinates and extend these subsystems so
that

    a.  uniform user and site identifications are used,

    b.  the File Transfer Protocol is utilized to allow mail to be
        originated and distributed anywhere on the Network without
        having to go through a central system.

    c.  there is an option for the sender to record the dialogue and
        have it catalogued for others to read and reference, and

    d.  There is a way to handle mail for TIP users.

        A suggestion made in the past to have a typewriter type terminal
        permanently attached to TIP's to record all hardcopy messages
        directed to that TIP should be reviewed.

We (SRI-ARC) have been looking into the problem of using the File
Transfer Protocol to allow NIC Journal mail to be sent and delivered
over the Network, without the user having to know and use NLS.  We
intend to integrate this function with the Tenex SNDMSG capabilities.
For some preliminary internal ARC discussion on this subject, you may be
interested in reading two Journal items, one by Charles Irby (IJOURNAL,
14308,1:w) and the other by Jim White (IJOURNAL, 14312,1:w).

    We realize that there are many benefits to this approach, but would
    like to have such a scheme fit into an agreed upon Network wide
    message and document sending protocol.

    Especially important to us is that questions concerning user and
    site identification, recorded and unrecorded dialogue, and
    coordination among other mail subsystems on the Network, be fully
    understood and mutually resolved at the design level before
    implementation work proceeds.

    We therefore want to discuss these issues at the Network Mail
    meeting February 22.

Role of the NIC

In conjunction with the above discussion, we will consider offering the
services of the Network Information Center in three related areas:

    to implement and maintain identification files for all network users
    and sites;

        (These files could be made available in sequential form through
        a standard socket so that Network sites could either query them
        or periodically obtain updated copy.)

    to record in the NIC Journal that mail which the sender wishes to
    have recorded, and to catalogue those items for later reference;

    to distribute Journal or message mail through the Network via File
    Transfer Protocols if requested;

    to provide and use NIC dialogue group identifications, in order to
    make it simpler to send items to several persons who had a common
    interest.

Network Mail Meeting Logistics

If you or anyone at your site would like to attend the meeting, please
notify Mil Jernigan (MEJ) at SRI-ARC:
    phone (415) 326-6200 ext. 4775

If you request it, we will make motel reservations for you.

Signed ... MD Kudlick










       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by Alex McKenzie with    ]
       [ support from GTE, formerly BBN Corp.             9/99 ]

ISO Plain Language

On this page
PROBLEMSeveral Network subsystems already handled mail, but their user and site identities and delivery methods needed coordination.
MECHANISMSRI-ARC schedules a meeting to discuss the mail problem, alternate solutions, and what steps participants should take.
WHAT IT ISThe notice says the meeting results would be published as an RFC for further discussion. It defines no mail protocol.

§1The Meeting Announcement

Michael Kudlick announces a meeting at SRI-ARC about the Network Mail problem discussed at the January 1973 Principal Investigators' Meeting. The meeting was scheduled for February 22, with a second day available if needed.

The goal was to define what a solution should do, what steps were needed, and who should do them. Results were to be published as an RFC.

The announcement sets a time and place for people to discuss network mail. It aims to turn that discussion into a clear plan.

§2Problems for the Mail System

The RFC notes that several Network subsystems already send and receive mail. The meeting was to consider common user and site identifications, use of FTP for mail distribution, an option to record dialogue for later reference, and a way to handle mail for TIP users.

SRI-ARC was exploring how FTP could deliver NIC Journal mail without requiring users to know NLS.

Different systems already handled mail, but they needed to work together. The meeting would consider shared identities, delivery, records, and service for TIP users.

§3Possible NIC Services

The meeting would also consider whether the Network Information Center could maintain identification files for users and sites, record selected mail in the NIC Journal, distribute mail through FTP, and provide group identifications for sending to several people.

The RFC asks people who want to attend to contact SRI-ARC.

The NIC might help maintain address information, keep selected messages, and distribute mail. These were topics for discussion, not commitments made by this notice.