Re: ANNOUNCEMENT: The IETF Trustees invite your review andcomments on a proposed Work-Around to the Pre-5378 Problem

"Tom.Petch" <sisyphus@dial.pipex.com> Thu, 15 January 2009 10:01 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D0E13A65A5; Thu, 15 Jan 2009 02:01:32 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4331E3A68A4; Thu, 15 Jan 2009 02:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.972
X-Spam-Level:
X-Spam-Status: No, score=-1.972 tagged_above=-999 required=5 tests=[AWL=0.627, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l14ccKaezNGq; Thu, 15 Jan 2009 02:01:30 -0800 (PST)
Received: from mk-outboundfilter-6.mail.uk.tiscali.com (mk-outboundfilter-6.mail.uk.tiscali.com [212.74.114.14]) by core3.amsl.com (Postfix) with ESMTP id 03BE23A6407; Thu, 15 Jan 2009 02:01:29 -0800 (PST)
X-Trace: 68008183/mk-outboundfilter-6.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.100.131/None/sisyphus@dial.pipex.com
X-SBRS: None
X-RemoteIP: 62.188.100.131
X-IP-MAIL-FROM: sisyphus@dial.pipex.com
X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwEALOXbkk+vGSD/2dsb2JhbACDQ4oNwVIGhWg
X-IronPort-AV: E=Sophos;i="4.37,268,1231113600"; d="scan'208";a="68008183"
X-IP-Direction: IN
Received: from 1cust131.tnt1.lnd9.gbr.da.uu.net (HELO allison) ([62.188.100.131]) by smtp.pipex.tiscali.co.uk with SMTP; 15 Jan 2009 10:01:12 +0000
Message-ID: <007901c976ef$c2986b80$0601a8c0@allison>
From: "Tom.Petch" <sisyphus@dial.pipex.com>
To: Bill Fenner <fenner@fenron.com>
References: <70873A2B7F744826B0507D4B84903E60@noisy> <54974382E5FF41D3A40EFDF758DB8C49@DGBP7M81> <20090112211809.515993A67EA@core3.amsl.com> <00a501c9762c$77bec780$0601a8c0@allison> <54e226890901141035sf8297a1v3a64f166a7b3725f@mail.gmail.com>
Subject: Re: ANNOUNCEMENT: The IETF Trustees invite your review andcomments on a proposed Work-Around to the Pre-5378 Problem
Date: Thu, 15 Jan 2009 09:41:14 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Cc: trustees@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "Tom.Petch" <sisyphus@dial.pipex.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

----- Original Message -----
From: "Bill Fenner" <fenner@fenron.com>
To: "Tom.Petch" <sisyphus@dial.pipex.com>
Cc: "Russ Housley" <housley@vigilsec.com>; <trustees@ietf.org>; <ietf@ietf.org>
Sent: Wednesday, January 14, 2009 7:35 PM
Subject: Re: ANNOUNCEMENT: The IETF Trustees invite your review andcomments on a
proposed Work-Around to the Pre-5378 Problem


> On Wed, Jan 14, 2009 at 1:41 AM, Tom.Petch <sisyphus@dial.pipex.com> wrote:
> > Ed's original announcement also placed significance on 0100 UTC on 16th
December
> > appearing to allow a grace period up until then during which 5378 was not in
> > effect, since old boiler plate was acceptable.
>
> This is not quite accurate.  RFC 5378 became BCP 78 at the time of
> publication on November 11th; even the old text says
> "      This document is subject to the rights, licenses and restrictions
>       contained in BCP 78, and except as set forth therein, the authors
>       retain all their rights."
>
> So if you published an I-D with those words in it after RFC 5378 was
> published as BCP 78, then that I-D is subject to the rights, licenses
> and restrictions contained in RFC 5378.

Thanks for the correction.  I also had in mind contributions to mailing lists
where the Note Well - eg the one sent out to this list on 1 January 2009 -
references RFC5378 (or not as is the case in other settings) rather than  BCP78.
I am unclear whether this is by design or whether it is something that has yet
to be brought in line with current thinking.

Isn't it complicated?

Tom Petch

>
>   Bill

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf