RFC 2890 on Key and Sequence Number Extensions to GRE

RFC Editor <rfc-ed@ISI.EDU> Thu, 31 August 2000 00:31 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11792; Wed, 30 Aug 2000 20:31:02 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA00244 for ietf-123-outbound.10@ietf.org; Wed, 30 Aug 2000 20:25:01 -0400 (EDT)
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 UAA00099 for <all-ietf@loki.ietf.org>; Wed, 30 Aug 2000 20:03:47 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11319 for <all-ietf@ietf.org>; Wed, 30 Aug 2000 20:03:44 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA27920; Wed, 30 Aug 2000 17:03:44 -0700 (PDT)
Message-Id: <200008310003.RAA27920@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2890 on Key and Sequence Number Extensions to GRE
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 30 Aug 2000 17:03:44 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2890

        Title:	    Key and Sequence Number Extensions to GRE
        Author(s):  G. Dommety
        Status:     Standards Track
	Date:       August 2000
        Mailbox:    gdommety@cisco.com
        Pages:      7
        Characters: 14503
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-dommety-gre-ext-04.txt

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


GRE (Generic Routing Encapsulation) specifies a protocol for
encapsulation of an arbitrary protocol over another arbitrary network
layer protocol. This document describes extensions by which two
fields, Key and Sequence Number, can be optionally carried in the GRE
Header.

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/rfc2890.txt"><ftp://ftp.isi.edu/in-notes/rfc2890.txt>