Re: IETF copying conditions

From: Stephane Bortzmeyer <bortzmeyer at nic.fr>
To: michael.dillon at bt.com
Cc: ietf at ietf.org
Date: Fri, 19 Sep 2008 13:53:42 +0200
In-reply-to: <C0F2465B4F386241A58321C884AC7ECC081E1D13 at E03MVZ2-UKDY.domain1.systemhost.net>
References: <alpine.LSU.1.10.0809181408230.30778 at hermes-1.csi.cam.ac.uk> <C0F2465B4F386241A58321C884AC7ECC081E1D13 at E03MVZ2-UKDY.domain1.systemhost.net>

On Thu, Sep 18, 2008 at 02:57:32PM +0100,
 michael.dillon at bt.com <michael.dillon at bt.com> wrote 
 a message of 36 lines which said:

> What law would prevent me from publishing the following
> GW-SMTP document?
> 
> ----snip-----
> Gee-Whizz SMTP is a derivative of IETF.
> 
> In RFC 2821 replace all occurences of HELO with GDAY.
> ----snip-----

Very good demonstration. That's precisely while the whole 3978bis
effort is flawed.
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

References:
- Re: IETF copying conditions
  - From: Tony Finch
- RE: IETF copying conditions
  - From: michael.dillon

Prev by Date: Re: IETF copying conditions
Next by Date: Re: IETF copying conditions
Previous by thread: Re: IETF copying conditions
Next by thread: Re: IETF copying conditions
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: IETF copying conditions

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.