usefor-article-12 November 2003
[< Prev]
[TOC] [ Next >]
13. Contact Address
Editor
Charles. H. Lindsey
5 Clerewood Avenue
Heald Green
Cheadle
Cheshire SK8 3JU
United Kingdom
Phone: +44 161 436 6131
Email: chl@clw.cs.man.ac.uk
[
Working group chairs
Andrew Gierth <andrew@erlenstar.demon.co.uk>
Pete Resnick <presnick@qualcomm.com>
]
Comments on this draft should preferably be sent to the mailing list
of the Usenet Format Working Group at
usenet-format@landfield.com.
This draft expires six months after the date of publication (see Page
1) (i.e. in May 2004).
Appendix A.1 - A-News Article Format
The obsolete "A News" article format consisted of exactly five lines
of header information, followed by the body. For example:
Aeagle.642
news.misc
cbosgd!mhuxj!mhuxt!eagle!jerry
Fri Nov 19 16:14:55 1982
Usenet Etiquette - Please Read
body
body
body
The first line consisted of an "A" followed by an article ID
(analogous to a message identifier and used for similar purposes).
The second line was the list of newsgroups. The third line was the
path. The fourth was the date, in the format above (all fields fixed
width), resembling an Internet date but not quite the same. The fifth
was the subject.
This format is documented for archeological purposes only. Articles
MUST NOT be generated in this format.
Appendix A.2 - Early B-News Article Format
The obsolete pseudo-Internet article format, used briefly during the
transition between the A News format and the modern format, followed
the general outline of a MAIL message but with some non-standard
headers. For example:
From: cbosgd!mhuxj!mhuxt!eagle!jerry (Jerry Schwarz)
Newsgroups: news.misc
Title: Usenet Etiquette -- Please Read
Article-I.D.: eagle.642
Posted: Fri Nov 19 16:14:55 1982
Received: Fri Nov 19 16:59:30 1982
Expires: Mon Jan 1 00:00:00 1990
body
body
body
The From-header contained the information now found in the Path-
header, plus possibly the full name now typically found in the From-
header. The Title-header contained what is now the Subject-content.
The Posted-header contained what is now the Date-content. The
Article-I.D.-header contained an article ID, analogous to a message
identifier and used for similar purposes. The Newsgroups- and
Expires-headers were approximately as now. The Received-header
contained the date when the latest relaying agent to process the
article first saw it. All dates were in the above format, with all
fields fixed width, resembling an Internet date but not quite the
same.
This format is documented for archeological purposes only. Articles
MUST NOT be generated in this format.
Appendix A.3 - Obsolete Headers
Early versions of news software following the modern format sometimes
generated headers like the following:
Relay-Version: version B 2.10 2/13/83; site cbosgd.UUCP
Posting-Version: version B 2.10 2/13/83; site eagle.UUCP
Date-Received: Friday, 19-Nov-82 16:59:30 EST
Relay-Version contained version information about the relaying agent
that last processed the article. Posting-Version contained version
information about the posting agent that posted the article. Date-
Received contained the date when the last relaying agent to process
the article first saw it (in a slightly nonstandard format).
In addition, this present standard obsoletes certain headers defined
in [Son-of-1036] (see 6.22):
Also-Control: cancel <9urrt98y53@site.example>
See-Also: <i4g587y@site1.example> <kgb2231+ee@site2.example>
Article-Names: comp.foo:charter
Article-Updates: <i4g587y@site1.example>
Also-Control indicated a control message that was also intended to be
filed as a normal article. See-Also listed related articles, but
without the specific relationship with followups that pertains to the
References-header. Article-Names indicated some special significance
of that article in relation to the indicated newsgroup. Article-
Updates indicated that an earlier article was updated, without at the
same time being superseded.
These headers are documented for archeological purposes only.
Articles containing these headers MUST NOT be generated.
Appendix A.4 - Obsolete Control Messages
This present standard obsoletes certain control messages defined in
[RFC 1036] (see 7.5), all of which had the effect of requesting a
description of a relaying or serving agent's software, or its peering
arrangements with neighbouring sites, to be emailed to the article's
reply address. Whilst of some utility when Usenet was much smaller
than it is now, they had become no more than a tool for the malicious
sending of mailbombs. Moreover, many organizations now consider
information about their internal connectivity to be confidential.
version
sendsys
whogets
senduuname
"Version" requested details of the transport software in use at a
site. "Sendsys" requested the full list of newsgroups taken, and the
peering arrangements. "Who gets" was similar, but restricted to a
named newsgroup. "Senduuname" resembled "sendsys" but restricted to
the list of peers connected by UUCP.
Historically, a checkgroups body consisting of one or two lines, the
first of the form "-n newsgroup", caused check-groups to apply to
only that single newsgroup.
Historically, an article posted to a newsgroup whose name had exactly
three components of which the third was "ctl" signified that article
was to be taken as a control message. The Subject-header specified
the actions, in the same way the Control-header does now.
These forms are documented for archeological purposes only; they MUST
NO LONGER be used.
Appendix B - Collected Syntax
Appendix B.1 - Characters, Atoms and Folding
In the following syntactic rules, numbers in the left hand margin
indicate rules taken from other documents, specifically:
1 from [RFC 2231] having regard to errata contained in [RFC
Errata];
2 from [RFC 2822] with the exception of those elements described
therein as "obsolete";
3 from [RFC 2373];
4 from [RFC 2234];
5 from [RFC 2045].
Where the number is followed by an asterisk ('*'), it indicates that
the rule in question has been modified for the purposes of this
standard.
4 ALPHA = %x41-5A / ; A-Z
%x61-7A ; a-z
2 CFWS = *([FWS] comment) ( ([FWS] comment) / FWS )
4 CR = %x0D ; carriage return
4 CRLF = CR LF
4 DIGIT = %x30-39 ; 0-9
4 DQUOTE = %d34 ; quote mark
2 FWS = ([*WSP CRLF] 1*WSP); folding whitespace
4 HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
4 HTAB = %x09 ; horizontal tab
4 LF = %x0A ; line feed
2 NO-WS-CTL = %d1-8 / ; US-ASCII control characters
%d11 / ; which do not include the
%d12 / ; carriage return, line feed,
%d14-31 / ; and whitespace characters
%d127
4 SP = %x20 ; space
4 WSP = SP / HTAB ; whitespace characters
2 atext = ALPHA / DIGIT /
"!" / "#" / ; Any character except
"$" / "%" / ; controls, SP, and specials.
"&" / "'" / ; Used for atoms
"*" / "+" /
"-" / "/" /
"=" / "?" /
"^" / "_" /
"`" / "{" /
"|" / "}" /
"~"
2 atom = [CFWS] 1*atext [CFWS]
2* ccontent = ctext / quoted-pair / comment / encoded-word
charset = <registered character set name>
; [RFC 2978]
2 comment = "(" *([FWS] ccontent) [FWS] ")"
2 ctext = NO-WS-CTL / ; all of <text> except
%d33-39 / ; SP, HTAB, "(", ")"
%d42-91 / ; and "\"
%d93-126
1 encoded-word = "=?" charset ["*" language] "?" encoding
"?" encoded-text "?="
2 dcontent = dtext / quoted-pair
2 dot-atom = [CFWS] dot-atom-text [CFWS]
2 dot-atom-text = 1*atext *( "." 1*atext )
2 dtext = NO-WS-CTL / ; Non white space controls
%d33-90 / ; The rest of the US-ASCII
%d94-126 ; characters not including
; "[", "]", or "
extended-phrase = ( [CFWS] encoded-word [CFWS] / word )
*( [CFWS] encoded-word [CFWS] / word /
[CFWS] "." [CFWS] )
language = <registered language tag>
; [RFC 3066]
2* phrase = 1*( [CFWS] encoded-word [CFWS] / word ) /
extended-phrase
2 qcontent = qtext / quoted-pair
2 qtext = NO-WS-CTL / ; all of <text> except
%d33 / ; SP, HTAB, "\" and DQUOTE
%d35-91 /
%d93-126
2 quoted-pair = "\" text
2 quoted-string = [CFWS] DQUOTE
*( [FWS] qcontent ) [FWS]
DQUOTE [CFWS]
2 specials = "(" / ")" / ; Special characters used in
"<" / ">" / ; other parts of the syntax
"[" / "]" /
":" / ";" /
"@" / "\" /
"," / "." /
DQUOTE
2 text = %d1-9 / ; all US-ASCII characters except
%d11-12 / ; NUL, CR and LF
%d14-127
5 tspecials = "(" / ")" / "<" / ">" / "@" /
"," / ";" / ":" / "\" / DQUOTE /
"/" / "[" / "]" / "?" / "="
2* unstructured = 1*( [FWS] ( utext / encoded-word ) ) [FWS]
2 utext = NO-WS-CTL / ; Non white space controls
%d33-126 ; The rest of US-ASCII
2 word = atom / quoted-string
Appendix B.2 - Basic Forms
2 addr-spec = local-part "@" domain
2 address = mailbox / group
2 address-list = address *( "," address )
2 angle-addr = [CFWS] "<" addr-spec ">" [CFWS]
article = 1*( header CRLF ) separator body
1 attribute = 1*attribute-char
1 attribute-char = <any (US-ASCII) CHAR except SPACE, CTLs,
"*", "'", "%", or tspecials>
body = *( *998text CRLF )
2 display-name = phrase
2 date = day month year
2 date-time = [ day-of-week "," ] date FWS time [CFWS]
2 day = [FWS] 1*2DIGIT
2 day-name = "Mon" / "Tue" / "Wed" / "Thu" /
"Fri" / "Sat" / "Sun"
2 day-of-week = [FWS] day-name
2 domain = dot-atom / domain-literal
2 domain-literal = [CFWS] "[" *([FWS] dcontent) [FWS] "]" [CFWS]
[< Prev]
[TOC] [ Next >]
#Diff to first older
--- ../usefor-article-11/Contact_Address.out June 2003
+++ ../usefor-article-12/Contact_Address.out November 2003
@@ -11,6 +11,8 @@
Phone: +44 161 436 6131
Email: chl@clw.cs.man.ac.uk
+
+
[
Working group chairs
@@ -25,7 +27,7 @@
usenet-format@landfield.com.
This draft expires six months after the date of publication (see Page
- 1) (i.e. in Dec 2003).
+ 1) (i.e. in May 2004).
Appendix A.1 - A-News Article Format
@@ -42,9 +44,9 @@
body
The first line consisted of an "A" followed by an article ID
- (analogous to a message ID and used for similar purposes). The
- second line was the list of newsgroups. The third line was the path.
- The fourth was the date, in the format above (all fields fixed
+ (analogous to a message identifier and used for similar purposes).
+ The second line was the list of newsgroups. The third line was the
+ path. The fourth was the date, in the format above (all fields fixed
width), resembling an Internet date but not quite the same. The fifth
was the subject.
@@ -75,11 +77,12 @@
header. The Title-header contained what is now the Subject-content.
The Posted-header contained what is now the Date-content. The
Article-I.D.-header contained an article ID, analogous to a message
- ID and used for similar purposes. The Newsgroups- and Expires-headers
- were approximately as now. The Received-header contained the date
- when the latest relaying agent to process the article first saw it.
- All dates were in the above format, with all fields fixed width,
- resembling an Internet date but not quite the same.
+ identifier and used for similar purposes. The Newsgroups- and
+ Expires-headers were approximately as now. The Received-header
+ contained the date when the latest relaying agent to process the
+ article first saw it. All dates were in the above format, with all
+ fields fixed width, resembling an Internet date but not quite the
+ same.
This format is documented for archeological purposes only. Articles
MUST NOT be generated in this format.
@@ -89,7 +92,6 @@
Early versions of news software following the modern format sometimes
generated headers like the following:
-
Relay-Version: version B 2.10 2/13/83; site cbosgd.UUCP
Posting-Version: version B 2.10 2/13/83; site eagle.UUCP
Date-Received: Friday, 19-Nov-82 16:59:30 EST
@@ -159,7 +161,8 @@
In the following syntactic rules, numbers in the left hand margin
indicate rules taken from other documents, specifically:
- 1 from [RFC 2231];
+ 1 from [RFC 2231] having regard to errata contained in [RFC
+ Errata];
2 from [RFC 2822] with the exception of those elements described
therein as "obsolete";
3 from [RFC 2373];
@@ -181,6 +184,9 @@
4 HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
4 HTAB = %x09 ; horizontal tab
4 LF = %x0A ; line feed
+
+
+
2 NO-WS-CTL = %d1-8 / ; US-ASCII control characters
%d11 / ; which do not include the
%d12 / ; carriage return, line feed,
@@ -204,8 +210,6 @@
charset = <registered character set name>
; [RFC 2978]
2 comment = "(" *([FWS] ccontent) [FWS] ")"
-
-
2 ctext = NO-WS-CTL / ; all of <text> except
%d33-39 / ; SP, HTAB, "(", ")"
%d42-91 / ; and "\"
@@ -235,6 +239,12 @@
2 quoted-string = [CFWS] DQUOTE
*( [FWS] qcontent ) [FWS]
DQUOTE [CFWS]
+
+
+
+
+
+
2 specials = "(" / ")" / ; Special characters used in
"<" / ">" / ; other parts of the syntax
"[" / "]" /
@@ -242,8 +252,8 @@
"@" / "\" /
"," / "." /
DQUOTE
-2 text = %d1-9 / ; all UTF-8 characters except
- %d11-12 / ; US-ASCII NUL, CR and LF
+2 text = %d1-9 / ; all US-ASCII characters except
+ %d11-12 / ; NUL, CR and LF
%d14-127
5 tspecials = "(" / ")" / "<" / ">" / "@" /
"," / ";" / ":" / "\" / DQUOTE /