[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Informational RFC to be: draft-shah-extreme-eaps-05.txt

To: RFC Editor <rfc-editor@rfc-editor.org>
Subject: Re: Informational RFC to be: draft-shah-extreme-eaps-05.txt
From: Thomas Narten <narten@us.ibm.com>
Date: Wed, 22 Jan 2003 14:49:02 -0500
Cc: IESG <iesg@ietf.org>, rja@extremenetworks.com, sshah@extremenetworks.com, my@extremenetworks.com
In-reply-to: Message from rfc-editor@rfc-editor.org of "Tue, 21 Jan 2003 15:52:35 PST." <20030121235235.GI7311@isi.edu>

> This RFC-to-be was submitted to the RFC Editor to be published as
> Informational: draft-shah-extreme-eaps-01.txt.

Quick note:

the document contains the wording:

   This document is an Internet-Draft and is NOT offered in accordance
   with Section 10 of RFC-2026, and the author does not provide the IETF
   with any rights other than to publish as an Internet-Draft.

I.e., it would not seem that we have the right to publish as an
RFC. 

Is it intended that this document is to be published as an RFC with a
no-derivative rights clause?

Thomas

Follow-Ups:
- Re: Informational RFC to be: draft-shah-extreme-eaps-05.txt
  - From: RJ Atkinson <rja@extremenetworks.com>

References:
- Informational RFC to be: draft-shah-extreme-eaps-05.txt
  - From: RFC Editor <rfc-editor@rfc-editor.org>

Prev by Date: Re: Draft response on .Com & .Net issue
Next by Date: Re: 56th IETF Meeting Scheduling - Draft Agenda
Previous by thread: Informational RFC to be: draft-shah-extreme-eaps-05.txt
Next by thread: Re: Informational RFC to be: draft-shah-extreme-eaps-05.txt
Index(es):
- Date
- Thread