[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
authors 48 hours: RFC 2890 <draft-dommety-gre-ext-04.txt> NOW AVAILABLE
- To: gre list <gre@ops.ietf.org>
- Subject: authors 48 hours: RFC 2890 <draft-dommety-gre-ext-04.txt> NOW AVAILABLE
- From: Randy Bush <randy@psg.com>
- Date: Tue, 22 Aug 2000 22:58:28 -0400
- Delivery-date: Tue, 22 Aug 2000 19:59:05 -0700
- Envelope-to: gre-data@psg.com
------- start of forwarded message -------
From: RFC Editor <rfc-ed@ISI.EDU>
To: gdommety@cisco.com
Cc: rfc-ed@ISI.EDU, bwijnen@lucent.com, randy@psg.com
Subject: authors 48 hours: RFC 2890 <draft-dommety-gre-ext-04.txt> NOW AVAILABLE
Date: Tue, 22 Aug 2000 16:31:05 -0700 (PDT)
Message-Id: <200008222331.QAA10204@jet.isi.edu>
****IMPORTANT*****
Updated 2000/08/22
RFC AUTHOR(S):
--------------
This is your LAST CHANCE to make changes to your RFC to be:
draft-dommety-gre-ext-04.txt, once the document is published we
*WILL NOT* make any changes.
Please check your document at
ftp://ftp.isi.edu/in-notes/authors/rfc2890.txt
You have 48 hours (2 WORK days) to look over your document for any
last minute editorial nits, *especially check your code.* If the main
editor of your document is out of town, or if you are going out of
town you may request an extension. Extensions are granted at the
prerogative of the RFC Editor.
Frequently INCORRECT information includes
- Contact Information
- References (are they up to date)
- Section Numbers
(especially if you originally put the copyright somewhere
other than the VERY end of the document, or if you numbered
the "Status of the Memo" field)
Please send us the changes, *DO NOT* send a new document with the
changes made. (If we think that the changes might be more than
editorial we will contact the AD or the IESG to confirm that the
changes do not require review.)
Send us the changes in THIS format.
1)*** SECTION #'s*** [i.e. Section 5, 2nd paragraph]
2) the text you want changed,
3) the new correct text and
4) if the changes are spacing or indentation than please note
that.
FOR EXAMPLE:
Section 5.6, 3rd paragraph
OLD:
The quick brown fox jumped over the lazy dog.
NEW:
The quick brown dog jumps over the lazy fox.
^^^ ^ ^^^
If you have a whole paragraph to replace you do not need to use
the arrow to point out the differences
INTRODUCTION, 2nd paragraph
Replace OLD:
alsdfja;sldjf;lajsd;fljas;dlfj;
With NEW:
nv;alkjd;lsf;aoisj;ltjka;sldkjf
Spacing or indentation problems...
Section 10, 1st paragraph (remove spaces between bit
and of, add space after butter)
OLD:
Better botter bought a bit
of bitter butterMary mary quite contrary
NEW:
Better botter bought a bit of bitter butter
Mary mary quite contrary
If we do not hear from you within 48 hours of this email, the document
will be published to the community at large AS IS.
Thanks for your cooperation,
-RFC Editor
====================================================================
A new Request for Comments is now available from ftp.isi.edu. As
the contact for a primary RFC library, you are responsible for
retrieving this RFC from ISI and installing it in your RFC library.
The official RFC announcement will be sent to the public distribution
list in one working day from this posting.
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
pathname: ftp://ftp.isi.edu/in-notes/rfc2890.txt
======================================================================
------- end of forwarded message -------