Re: Last Call: draft-ellermann-news-nntp-uri (The 'news' and 'nntp' URI Schemes) to Proposed Standard

"Tom.Petch" <sisyphus@dial.pipex.com> Fri, 22 February 2008 20:28 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAA2B3A6D1E; Fri, 22 Feb 2008 12:28:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.837
X-Spam-Level:
X-Spam-Status: No, score=-0.837 tagged_above=-999 required=5 tests=[AWL=-0.444, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
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 yFC91M50b2db; Fri, 22 Feb 2008 12:28:20 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6D093A68DF; Fri, 22 Feb 2008 12:28:20 -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 C216E3A68DF for <ietf@core3.amsl.com>; Fri, 22 Feb 2008 12:28:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 byfRTyFE9jrc for <ietf@core3.amsl.com>; Fri, 22 Feb 2008 12:28:19 -0800 (PST)
Received: from mk-outboundfilter-2.mail.uk.tiscali.com (mk-outboundfilter-2.mail.uk.tiscali.com [212.74.114.38]) by core3.amsl.com (Postfix) with ESMTP id AD31D3A6780 for <ietf@ietf.org>; Fri, 22 Feb 2008 12:28:18 -0800 (PST)
X-Trace: 11533665/mk-outboundfilter-2.mail.uk.tiscali.com/PIPEX/$ACCEPTED/pipex-temporary-group/213.116.60.83
X-SBRS: None
X-RemoteIP: 213.116.60.83
X-IP-MAIL-FROM: sisyphus@dial.pipex.com
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFq/vkfVdDxT/2dsb2JhbABBijWkHgQ
X-IP-Direction: IN
Received: from 1cust83.tnt106.lnd4.gbr.da.uu.net (HELO allison) ([213.116.60.83]) by smtp.pipex.tiscali.co.uk with SMTP; 22 Feb 2008 20:28:12 +0000
Message-ID: <006501c87588$ba59aba0$0601a8c0@allison>
From: "Tom.Petch" <sisyphus@dial.pipex.com>
To: ietf@ietf.org
References: <20080219011834.B426E3A6951@core3.amsl.com>
Subject: Re: Last Call: draft-ellermann-news-nntp-uri (The 'news' and 'nntp' URI Schemes) to Proposed Standard
Date: Fri, 22 Feb 2008 17:57:08 +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
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: <http://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: <http://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

I have read this I-D and believe it should be published as an RFC.

The author has a challenging task in that on the one hand, there is a pressing
need to provide a replacement for parts of the, by now very ancient, RFC1738
while on the other, the subject matter is a moving target and it will be
possible for some time to come to defer publication and then to produce a more
up-to-date, perhaps better, version.  I think that the author gets the balance
right and that this should be published.  Perhaps, in a year or two, when the
surrounding landscape is more stable, there will be scope for a revision but
that it would be wrong to defer publication on account of that possibility.

I did not understand the second paragraph of s8.3 at first and believe that this
should be made clearer, in line with the explanation that the author provided on
the uri.w3.org mailing list.

Tom Petch


----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Sent: Tuesday, February 19, 2008 2:18 AM
Subject: Last Call: draft-ellermann-news-nntp-uri (The 'news' and 'nntp' URI
Schemes) to Proposed Standard


> The IESG has received a request from an individual submitter to consider
> the following document:
>
> - 'The 'news' and 'nntp' URI Schemes '
>    <draft-ellermann-news-nntp-uri-08.txt> as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive comments to the
> ietf@ietf.org mailing lists by 2008-03-17. Exceptionally,
> comments may be sent to iesg@ietf.org instead. In either case, please
> retain the beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ellermann-news-nntp-uri-08.txt
>
>
> IESG discussion can be tracked via
>
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13153&rf
c_flag=0
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> http://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
IETF mailing list
IETF@ietf.org
http://www.ietf.org/mailman/listinfo/ietf