RFC 2784 on Generic Routing Encapsulation

RFC Editor <rfc-ed@ISI.EDU> Thu, 16 March 2000 21:21 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24218; Thu, 16 Mar 2000 16:21:18 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id QAA02947 for ietf-123-outbound.10@ietf.org; Thu, 16 Mar 2000 16:05:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id NAA01375 for <all-ietf@loki.ietf.org>; Thu, 16 Mar 2000 13:04:46 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12626 for <all-ietf@ietf.org>; Thu, 16 Mar 2000 13:04:46 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA20646; Thu, 16 Mar 2000 10:04:46 -0800 (PST)
Message-Id: <200003161804.KAA20646@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2784 on Generic Routing Encapsulation
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 16 Mar 2000 10:04:46 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2784

        Title:	    Generic Routing Encapsulation (GRE)
        Author(s):  D. Farinacci, T. Li, S. Hanks, D. Meyer, P. Traina
        Status:     Standards Track
	Date:       March 2000
        Mailbox:    dino@procket.com, tony1@home.net,
                    stan_hanks@enron.net, dmm@cisco.com,
                    pst@juniper.net 
        Pages:      9
        Characters: 16627
	Updates/Obsoletes/SeeAlso: None
        I-D Tag:    draft-meyer-gre-update-03.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2784.txt


This document specifies a protocol for encapsulation of an arbitrary
network layer protocol over another arbitrary network layer protocol.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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.echo 
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/rfc2784.txt"><ftp://ftp.isi.edu/in-notes/rfc2784.txt>