RE: Last Call for Comments: Proposed work-around to the Pre-5378 Problem
"Wes Beebee (wbeebee)" <wbeebee@cisco.com> Fri, 13 February 2009 18:54 UTC
Return-Path: <wbeebee@cisco.com>
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 B96CA3A6A5C; Fri, 13 Feb 2009 10:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 KQG8aOEzcp6Q; Fri, 13 Feb 2009 10:54:04 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id DBE5F3A6805; Fri, 13 Feb 2009 10:54:03 -0800 (PST)
X-IronPort-AV: E=Sophos; i="4.38,203,1233532800"; d="scan'208,217"; a="36985512"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 13 Feb 2009 18:54:10 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n1DIsAfh010948; Fri, 13 Feb 2009 13:54:10 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n1DIsAaF028933; Fri, 13 Feb 2009 18:54:10 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 13 Feb 2009 13:54:10 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C98E0C.7451F32C"
Subject: RE: Last Call for Comments: Proposed work-around to the Pre-5378 Problem
Date: Fri, 13 Feb 2009 13:54:09 -0500
Message-ID: <BB56240F3A190F469C52A57138047A0301B8C8D1@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <9e8bc9820902121653w30b162d7q4666503cf160c643@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Last Call for Comments: Proposed work-around to the Pre-5378 Problem
Thread-Index: AcmOCu64UXGBR/KgR9KLxjXNiwrcqgAANg7Q
References: <9e8bc9820902052128i1fe6ba93ved493e7ac2ac5e5d@mail.gmail.com> <9e8bc9820902121653w30b162d7q4666503cf160c643@mail.gmail.com>
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: Ed Juskevicius <edj.etc@gmail.com>, ietf@ietf.org, ietf-announce@ietf.org, wgchairs@ietf.org, iab@iab.org, iesg@ietf.org, rfc-editor@rfc-editor.org
X-OriginalArrivalTime: 13 Feb 2009 18:54:10.0203 (UTC) FILETIME=[747F6EB0:01C98E0C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6309; t=1234551250; x=1235415250; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=wbeebee@cisco.com; z=From:=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.co m> |Subject:=20RE=3A=20Last=20Call=20for=20Comments=3A=20Propo sed=20work-around=20to=20the=20Pre-5378=20Problem |Sender:=20 |To:=20=22Ed=20Juskevicius=22=20<edj.etc@gmail.com>,=20<iet f@ietf.org>,=0A=20=20=20=20=20=20=20=20<ietf-announce@ietf.o rg>,=20<wgchairs@ietf.org>,=20<iab@iab.org>,=0A=20=20=20=20= 20=20=20=20<iesg@ietf.org>,=20<rfc-editor@rfc-editor.org>; bh=SbPeVKYOUpNtWceHpP9LxqigktOiA2PMdVFB57MH1OE=; b=RIIX2cr/Y1TyNCv9pAnMVnbZGY+v4WQbDHiZTfMkZ/udisgA7AQKR2sxyF 9SWJqRwgDk8SlqTxdbGSpbHeDrtkcMUtrVCPZWYsFv01+HxZMXCtYv2Hhewc y+941Buas9;
Authentication-Results: rtp-dkim-1; header.From=wbeebee@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Cc: Trustees <trustees@ietf.org>, "Contreras, Jorge" <Jorge.Contreras@wilmerhale.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
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>
X-List-Received-Date: Fri, 13 Feb 2009 18:54:05 -0000
When will http://xml.resource.org/ and xml2rfc be updated to include this? Are there any changes we need to make to our input xml files? - Wes ________________________________ From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ed Juskevicius Sent: Thursday, February 12, 2009 7:53 PM To: ietf@ietf.org; ietf-announce@ietf.org; wgchairs@ietf.org; iab@iab.org; iesg@ietf.org; rfc-editor@rfc-editor.org Cc: Trustees; Contreras,Jorge Subject: Re: Last Call for Comments: Proposed work-around to the Pre-5378 Problem I am pleased to announce that the IETF Trustees have just finished work on a revision to our "Legal Provisions Relating to IETF Documents" policy. The revision includes optional new legend text in Section 6.c.iii of the policy to serve as a work-around for people experiencing the "pre-5378 problem." Please note the newly approved policy is dated 2009-02-12. Please also note that the Effective Date of this revised policy has been set to 2009-02-15. The old policy (effective from November 10, 2008) remains in force until 00h00 UTC on February 15th. The approved text is available now on IETF Trust website at http://trustee.ietf.org/policyandprocedures.html Please look for the document dated 2009-02-12, just below the heading labeled "DRAFT Policy and Procedures Being Developed." On or shortly after February 15th, the Trust website will be updated so as to archive all of the recent draft versions of the new policy, and to make it easier to navigagte to the newly approved policy. Please review the new policy so you are aware of the latest copyright statements and other boilerplate legend text that will be required on all contributions to the IETF starting on February 15, 2009. Regards, and Thanks in advance, Ed Juskevicius, on behalf of the IETF Trustees edj.etc@gmail.com
- Last Call for Comments: Proposed work-around to t… Ed Juskevicius
- Re: Last Call for Comments: Proposed work-around … Henrik Levkowetz
- Re: Last Call for Comments: Proposed work-around … Tom.Petch
- Re: Last Call for Comments: Proposed work-around … TSG
- Re: Last Call for Comments: Proposed work-around … Thomas Narten
- Re: Last Call for Comments: Proposed work-around … John C Klensin
- RE: Last Call for Comments: Proposed work-around … Ed Juskevicius
- RE: Last Call for Comments: Proposed work-around … Ed Juskevicius
- Re: Last Call for Comments: Proposed work-around … Simon Josefsson
- Re: [Trustees] Last Call for Comments: Proposed w… Ray Pelletier
- Re: [Trustees] Last Call for Comments: Proposed w… Thomas Narten
- Re: [Trustees] Last Call for Comments: Proposed w… Ray Pelletier
- Re: [Trustees] Last Call for Comments: Proposed w… Marshall Eubanks
- Re: [Trustees] Last Call for Comments: Proposed w… Simon Josefsson
- RE: [Trustees] Last Call for Comments: Proposed w… Contreras, Jorge
- RE: [Trustees] Last Call for Comments: Proposed w… John C Klensin
- RE: [Trustees] Last Call for Comments: Proposed w… SM
- RE: [Trustees] Last Call for Comments: Proposed w… John C Klensin
- Re: [Trustees] Last Call for Comments: Proposed w… Ray Pelletier
- RE: [Trustees] Last Call for Comments: Proposed w… Contreras, Jorge
- RE: [Trustees] Last Call for Comments: Proposed w… John C Klensin
- RE: [Trustees] Last Call for Comments: Proposed w… SM
- Re: [Trustees] Last Call for Comments: Proposed w… Ray Pelletier
- Re: [Trustees] Last Call for Comments: Proposed w… Thomas Narten
- Re: [Trustees] Last Call for Comments: Proposed w… Marshall Eubanks
- Re: [Trustees] Last Call for Comments: Proposed w… Thomas Narten
- RE: [Trustees] Last Call for Comments: Proposed w… Contreras, Jorge
- RE: [Trustees] Last Call for Comments: Proposed w… Contreras, Jorge
- Re: [Trustees] Last Call for Comments: Proposed w… Cullen Jennings
- Re: [Trustees] Last Call for Comments: Proposed w… Marshall Eubanks
- Re: [Trustees] Last Call for Comments: Proposed w… Ed Juskevicius
- Re: Last Call for Comments: Proposed work-around … Ed Juskevicius
- RE: Last Call for Comments: Proposed work-around … Wes Beebee (wbeebee)
- Re: [Trustees] Last Call for Comments: Proposed w… Ray Pelletier
- Re: [Trustees] Last Call for Comments: Proposed w… John C Klensin
- Re: [Trustees] Last Call for Comments: Proposed w… Ray Pelletier
- IASA irresponsibility? (was: Re: [IAB] [Trustees]… John C Klensin
- RE: IASA irresponsibility? (was: Re: [IAB] [Trust… Ed Juskevicius
- Re: [IAB] IASA irresponsibility? (was: Re: [Trust… John C Klensin
- Re: [Trustees] Last Call for Comments: Proposed w… Julian Reschke
- Re: [Trustees] Last Call for Comments: Proposed w… Ray Pelletier
- Re: [xml2rfc] [IAB] [Trustees] Last Call for Comm… ned+ietf
- Re: [Trustees] [xml2rfc] Last Call for Comments: … Bob Hinden
- Re: [xml2rfc] [Trustees] Last Call for Comments: … Bill Fenner
- Re: [xml2rfc] [Trustees] Last Call for Comments: … Bill Fenner
- Re: [IAB] [xml2rfc] [Trustees] Last Call for Comm… John C Klensin