public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Owen Rees <owen.rees@hp.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: Your setting Return-Path to YOU in your cygwin@cygwin postings
Date: Wed, 04 Mar 2009 17:04:00 -0000	[thread overview]
Message-ID: <0E63A1E9C219A9822515737A@orees.hpl.hp.com> (raw)
In-Reply-To: <49AEAECD.5030506@gmail.com>

--On Wednesday, March 04, 2009 16:39:41 +0000 Dave Korn wrote:

>   Yes, you're right.  Looking at the history, it's never made it to the
> status of an STD, but there was an IETF draft proposal (which is actually
> one stage more advanced than an RFC):
>
> http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-
> to-00.txt
>

To quote RFC2026:

2.2  Internet-Drafts

   During the development of a specification, draft versions of the
   document are made available for informal review and comment by
   placing them in the IETF's "Internet-Drafts" directory, which is
   replicated on a number of Internet hosts.  This makes an evolving
   working document readily available to a wide audience, facilitating
   the process of review and revision.

   An Internet-Draft that is published as an RFC, or that has remained
   unchanged in the Internet-Drafts directory for more than six months
   without being recommended by the IESG for publication as an RFC, is
   simply removed from the Internet-Drafts directory.  At any time, an
   Internet-Draft may be replaced by a more recent version of the same
   specification, restarting the six-month timeout period.

   An Internet-Draft is NOT a means of "publishing" a specification;
   specifications are published through the RFC mechanism described in
   the previous section.  Internet-Drafts have no formal status, and are
   subject to change or removal at any time.

      ********************************************************
      *                                                      *
      *   Under no circumstances should an Internet-Draft    *
      *   be referenced by any paper, report, or Request-    *
      *   for-Proposal, nor should a vendor claim compliance *
      *   with an Internet-Draft.                            *
      *                                                      *
      ********************************************************


That, and the rest of RFC2026 makes it clear that a "internet draft" has 
lower status than an RFC - it is typically a proposal that may eventually 
turn into an RFC. On the subject of expiry:

draft-ietf-drums-mail-followup-to-00.txt
Expires: May 1998

It has not been followed up for over 10 years so I think that indicates the 
status of the proposal as far as the IETF process is concerned.

-- 
Owen Rees; speaking personally, and not on behalf of HP.
========================================================
Hewlett-Packard Limited.   Registered No: 690597 England
Registered Office:  Cain Road, Bracknell, Berks RG12 1HN

  parent reply	other threads:[~2009-03-04 17:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49ADA916.40700@columbus.rr.com>
     [not found] ` <49ADBA0D.6040405@gmail.com>
     [not found]   ` <49ADEF5E.3060804@columbus.rr.com>
     [not found]     ` <49ADF5B5.5000102@gmail.com>
     [not found]       ` <49AE0F52.1060006@columbus.rr.com>
2009-03-04 11:59         ` Dave Korn
2009-03-04 12:30           ` Owen Rees
2009-03-04 16:30             ` Dave Korn
2009-03-04 16:45               ` Christopher Faylor
2009-03-04 17:04               ` Owen Rees [this message]
2009-03-04 18:16                 ` Dave Korn
2009-03-05 10:57                   ` Owen Rees
2009-03-05 13:18                     ` Dave Korn
2009-03-05 15:56                       ` Owen Rees
2009-03-05 18:32                         ` Morgan Gangwere

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0E63A1E9C219A9822515737A@orees.hpl.hp.com \
    --to=owen.rees@hp.com \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).