[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Missing Path: header in USEPRO newgroup sample

To: Julien =?utf-8?q?=C3=89LIE?= <julien@xxxxxxxxxxxxxxx>
Subject: Re: Missing Path: header in USEPRO newgroup sample
From: Russ Allbery <rra@xxxxxxxxxxxx>
Date: Sat, 19 Dec 2009 12:02:30 -0800
Cc: "Usefor WG" <ietf-usefor@xxxxxxx>
In-reply-to: <> ("Julien =?utf-8?q?=C3=89LIE=22's?= message of "Sat, 19 Dec 2009 11:31:59 +0100")
List-archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-id: <ietf-usefor.imc.org>
List-unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
Organization: The Eyrie
References: <>
Sender: owner-ietf-usefor@xxxxxxxxxxxx
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Julien ÉLIE <julien@xxxxxxxxxxxxxxx> writes:

> In RFC 5537 (USEPRO), the newgroup control message example (§ 5.2.1.1)
> does not have the mandatory Path: header field.  It is only a
> proto-article here.

> A control message is defined in § 5 as an article which contains a
> Control: header field, so I believe a Path: header field should be added
> in the sample.

Yes, you're right.  That's probably worth an erratum.

-- 
Russ Allbery (rra@xxxxxxxxxxxx)             <http://www.eyrie.org/~eagle/>

References:
- Missing Path: header in USEPRO newgroup sample
  - From: Julien ÉLIE

Prev by Date: Missing Path: header in USEPRO newgroup sample
Previous by thread: Missing Path: header in USEPRO newgroup sample
Index(es):
- Date
- Thread