RFC1719 on A Direction for IPng

"Joyce K. Reynolds" <jkrey@isi.edu> Fri, 16 December 1994 20:12 UTC

Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06702; 16 Dec 94 15:12 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa12535; 16 Dec 94 15:12 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06689; 16 Dec 94 15:12 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06637; 16 Dec 94 15:07 EST
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa12437; 16 Dec 94 15:07 EST
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA18489>; Fri, 16 Dec 1994 12:06:57 -0800
Message-Id: <199412162006.AA18489@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1719 on A Direction for IPng
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 16 Dec 1994 12:07:55 -0800
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

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


        RFC 1719:

        Title:      A Direction for IPng
        Author:     P. Gross
        Mailbox:    phill_gross@mcimail.com
        Pages:      5
        Characters: 11,118
        Updates/Obsoletes:  none


This document was submitted to the IPng Area in response to RFC 1550.
Publication of this document does not imply acceptance by the IPng
Area of any ideas expressed within.  Comments should be submitted to
the big-internet@munnari.oz.au mailing list.  This RFC specifies
criteria related to mobility for consideration in design and selection
of the Next Generation of IP.

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 IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

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

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  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@ISI.EDU.  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.
ftp://ds.internic.net/rfc/rfc1719.txt"><ftp://ds.internic.net/rfc/rfc1719.txt>