Typos and new message-ID syntax in RFC 5538

Julien ÉLIE <julien@trigofacile.com> Wed, 11 November 2009 14:06 UTC

Return-Path: <owner-ietf-usefor@mail.imc.org>
X-Original-To: ietfarch-usefor-archive@core3.amsl.com
Delivered-To: ietfarch-usefor-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D5AB28C192 for <ietfarch-usefor-archive@core3.amsl.com>; Wed, 11 Nov 2009 06:06:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.994
X-Spam-Level:
X-Spam-Status: No, score=-2.994 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_50=0.001, HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, STOX_REPLY_TYPE=0.001]
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 HN0TvuK7q4Vj for <ietfarch-usefor-archive@core3.amsl.com>; Wed, 11 Nov 2009 06:06:29 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 0779428C18D for <usefor-archive@ietf.org>; Wed, 11 Nov 2009 06:06:28 -0800 (PST)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id nABE02N2031716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Nov 2009 07:00:02 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id nABE02Qx031715; Wed, 11 Nov 2009 07:00:02 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f
Received: from 42.mail-out.ovh.net (42.mail-out.ovh.net [213.251.189.42]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id nABDxxxJ031654 for <ietf-usefor@imc.org>; Wed, 11 Nov 2009 07:00:02 -0700 (MST) (envelope-from julien@trigofacile.com)
Received: (qmail 6442 invoked by uid 503); 11 Nov 2009 14:00:02 -0000
Received: from b9.ovh.net (HELO mail419.ha.ovh.net) (213.186.33.59) by 42.mail-out.ovh.net with SMTP; 11 Nov 2009 14:00:02 -0000
Received: from b0.ovh.net (HELO queueout) (213.186.33.50) by b0.ovh.net with SMTP; 11 Nov 2009 14:00:14 -0000
Received: from aaubervilliers-151-1-40-10.w83-112.abo.wanadoo.fr (HELO Iulius) (julien%trigofacile.com@83.112.151.10) by ns0.ovh.net with SMTP; 11 Nov 2009 14:00:12 -0000
Message-ID: <02FCE9AB44A54784A0946723975A84D3@Iulius>
From: Julien ÉLIE <julien@trigofacile.com>
To: Usefor WG <ietf-usefor@imc.org>
Subject: Typos and new message-ID syntax in RFC 5538
Date: Wed, 11 Nov 2009 14:59:52 +0100
Organization: TrigoFACILE -- http://www.trigofacile.com/
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="ISO-8859-15"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
X-Ovh-Tracer-Id: 14081630136854707641
X-Ovh-Remote: 83.112.151.10 (aaubervilliers-151-1-40-10.w83-112.abo.wanadoo.fr)
X-Ovh-Local: 213.186.33.20 (ns0.ovh.net)
X-Spam-Check: DONE|U 0.5/N
Sender: owner-ietf-usefor@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-Unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
List-ID: <ietf-usefor.imc.org>

Hi,

Shouldn't a few things be changed in draft-ellermann-news-nntp-uri-11
before its publication as RFC 5538?
Especially after the changed made in RFC 5536 (USEFOR)?

   For Netnews, a
   group "example" has the same name on any server carrying this group,
   exotic cases involving gateways not withstanding.

* "notwithstanding", in only one word?  (I do not understand otherwise
the sentence if it is the verb "to withstand".)


      URI producers have to percent-encode some characters as specified
   below (Section 4); otherwise, they MUST treat a "Message-ID" without
   angle brackets for 'news' URLs as is, i.e., case-sensitive,
   preserving quoted pairs and quoted strings.

* Quoted strings no longer exist.


       nntpURL         = "nntp:" server "/" group [ "/" article-number ]
       server          = "//" authority               ; see RFC 3986
       group           = 1*( group-char / pct-encoded )
       article-number  = 1*16DIGIT                    ; see RFC 3977
       group-char      = ALPHA / DIGIT / "-" / "+" / "_" / "."

* Is it wise to redefine <article-number> here, limited to 16 digits?
We already know that an article number has in pratice more than 16 digits
because a few servers (like Giganews) currently use 64-bit numbers
for article numbers.  Therefore, why explicitly refer to RFC 3977?
The limitation of 16 digits may be obsoleted by an extension.


   However, [RFC5536] does not (yet) permit characters outside of
   <group-char> and so, to keep the syntax simple, the additional
   characters are here covered by <pct-encoded> as defined in [RFC3986],

* Shouldn't the sentence be changed?  "(yet)" is strange.  It appears
twice RFC 5538.


   Please note that "%20" (space) and "%3E" (">") are not allowed.  A
   "%5C" (backslash, "\") can only occur in four combinations, as shown
   above.  Examples:

       news://server.example/ab.cd@example.com
       news:%22do..ts%22@example.com
       news:ab.cd@%5B2001:DB8::CD30%5D

* The second example is invalid.  Two consecutive dots are not allowed.
Quoted strings are no longer allowed.


     mid-left        = 1*( mid-atext / "." ) /      ; <dot-atom-text>
                       ( "%22" mid-quote "%22" )    ; <no-fold-quote>
     mid-quote       = 1*( mid-atext / "." /        ; <mqtext> incl.
                           mid-special /            ; '\"' / "[" / "]"
                           "%5C%22" / "%5B" / "%5D" )

* This syntax is no longer allowed.


   As noted above (Section 2.2), the presence of an "@" in a 'news' URI
   disambiguates <article> and <newsgroups> for URI consumers.  The new
   <message-id> construct specified in [RFC3977] does not require an
   "@".

* But RFC 5536 (USEFOR) requires one.


   SON-OF-1036

* If its RFC number is known, it could be specified.


   The work on a successor of [RFC2822] hopefully ends up with a
   simplified syntax for both sides of a "Message-ID".

* This sentence should be removed.  The syntax has been simplified by
RFC 5322.


   [RFC4289] requires an RFC for the access types registry.  Because
   [SON-OF-1036] was never published as an RFC, the following paragraph
   quotes the relevant definition:

      NOTE: In the specific case where it is desired to essentially make
      another article PART of the current one, e.g., for annotation of
      the other article, MIME's "message/external-body" convention can
      be used to do so without actual inclusion. "news-message-ID" was
      registered as a standard external-body access method, with a
      mandatory NAME parameter giving the message ID and an optional
      SITE parameter suggesting an NNTP site that might have the article
      available (if it is not available locally), by IANA 22 June 1993.

* Maybe the paragraph can be removed:  SON-OF-1036 will soon be published
as an historic RFC.


   Please note that 'news' URLs offer a very similar and (today) more
   common way to access articles by their Message-ID; compare [RFC2017].

* "Message-ID" with quotes (all other occurrences use one in the document).

-- 
Julien ÉLIE

« C'est la goutte d'eau qui fait déborder le vase et qui met
le feu aux poudres. »