usefor-usepro-02 December 2004
[< Prev]
[TOC]
12. 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 chair
Alexey Melnikov <alexey.melnikov-usefor@isode.com>
]
Comments on this draft should preferably be sent to the mailing list
of the Usenet Format Working Group at
ietf-usefor@imc.org.
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 Control Messages
This present standard obsoletes certain control messages defined in
[RFC 1036] (see 6.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 - Notices
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Appendix C - Change Log
[This Appendix is to be removed prior to final publication.]
For version 01
1 Numerous texts describing protocol features related to
particular headers in parts of [ARTICLE] which were destined to
become part of [USEFOR] have been moved to appropriate locations
within section 7 of this document. Such revised texts will be
found in sections
7.2.2 Steps 4, 6, 7, 10, 11, 12;
7.2.3 Step 1(b);
7.3 introductory paragraphs, Steps 1, 4, 8, 9, and some final
paragraphs;
7.4 introductory and final paragraphs;
7.9.1 Step 5.
2 A section on "Duties of a Reading Agent" (7.8) has been added.
3 Some demotions MUST -> SHOULD -> MAY, as noted in pseudo-
comments, have been made or proposed in sections
7.3
7.3 Step 4.
4 Part of the procedure for examining Path-headers by relaying
agents has been moved to serving agents, as explained in
pseudo-comments in section 7.4.
5 Some renumbering of sections and minor textual clarifications.
For version 02
1 2nd para. of a-7 temporarily reinstated in section 6.
2 Para. in section 6 relating to propagation of control messages
and local policy removed to [USEAGE].]
3 Requirement for some relaying agents to examine control messages
for non-existent groups
6
7.3
4 Text regarding "aliasing out" brought into line with actual
practice.
7.3
5 More realistic wording regarding the expectations of reading
agents
7.7
7.4
6 "Precursor" is now defined for all cases in which a References
header may be used (even though "followup" is not always defined
under Alternative-1).
2.1
7 Provision is made for a poster to use a mailbox ending in
".invalid" in a From header (formerly in a-5.2).
7.5
8 "Inheritable" and "Variant" headers defined (formerly in a-
4.2.5).
2.3
9 Additional wording regarding function of verb/arguments/body in
control messages (formerly in a-6.13).
6
10 NOTE regarding not altering message indentifiers during
transport or copying added (formerly in a-5.3).
7.3
11 All mention of MIME-style parameters and extension-parameters
removed.
3.1
7.6
[< Prev]
[TOC]
#Diff to first older
--- ../usefor-usepro-01/Contact_Address.out September 2004
+++ ../usefor-usepro-02/Contact_Address.out December 2004
@@ -11,6 +11,7 @@
Phone: +44 161 436 6131
Email: chl@clw.cs.man.ac.uk
+
[
Working group chair
@@ -44,7 +45,6 @@
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.
@@ -121,52 +121,40 @@
Intellectual Property
The IETF takes no position regarding the validity or scope of any
- intellectual property or other rights that might be claimed to
+ Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
- might or might not be available; neither does it represent that it
- has made any effort to identify any such rights. Information on the
- IETF's procedures with respect to rights in standards-track and
- standards-related documentation can be found in BCP-11. Copies of
- claims of rights made available for publication and any assurances of
- licenses to be made available, or the result of an attempt made to
- obtain a general license or permission for the use of such
- proprietary rights by implementors or users of this specification can
- be obtained from the IETF Secretariat.
+ might or might not be available; nor does it represent that it has
+ made any independent effort to identify any such rights. Information
+ on the procedures with respect to rights in RFC documents can be
+ found in BCP 78 and BCP 79.
+
+ Copies of IPR disclosures made to the IETF Secretariat and any
+ assurances of licenses to be made available, or the result of an
+ attempt made to obtain a general license or permission for the use of
+ such proprietary rights by implementers or users of this
+ specification can be obtained from the IETF on-line IPR repository at
+ http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
- rights which may cover technology that may be required to practice
- this standard. Please address the information to the IETF Executive
- Director.
+ rights that may cover technology that may be required to implement
+ this standard. Please address the information to the IETF at ietf-
+ ipr@ietf.org.
Full Copyright Statement
- Copyright (C) The Internet Society (2003). All Rights Reserved
-
- This document and translations of it may be copied and furnished to
- others, and derivative works that comment on or otherwise explain it
- or assist in its implementation may be prepared, copied, published
- and distributed, in whole or in part, without restriction of any
- kind, provided that the above copyright notice and this paragraph are
- included on all such copies and derivative works. However, this
- document itself may not be modified in any way, such as by removing
- the copyright notice or references to the Internet Society or other
- Internet organizations, except as needed for the purpose of
- developing Internet standards in which case the procedures for
- copyrights defined in the Internet Standards process must be
- followed, or as required to translate it into languages other than
- English.
-
- The limited permissions granted above are perpetual and will not be
- revoked by the Internet Society or its successors or assigns.
-
- This document and the information contained herein is provided on an
- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
+ Copyright (C) The Internet Society (2004). This document is subject
+ to the rights, licenses and restrictions contained in BCP 78, and
+ except as set forth therein, the authors retain all their rights.
+
+ This document and the information contained herein are provided on an
+ "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
+ OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
+ ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
+ INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
+ INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
+ WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Appendix C - Change Log
@@ -198,4 +186,51 @@
pseudo-comments in section 7.4.
5 Some renumbering of sections and minor textual clarifications.
+
+ For version 02
+
+ 1 2nd para. of a-7 temporarily reinstated in section 6.
+
+ 2 Para. in section 6 relating to propagation of control messages
+ and local policy removed to [USEAGE].]
+
+ 3 Requirement for some relaying agents to examine control messages
+ for non-existent groups
+ 6
+ 7.3
+
+ 4 Text regarding "aliasing out" brought into line with actual
+ practice.
+ 7.3
+
+ 5 More realistic wording regarding the expectations of reading
+ agents
+ 7.7
+ 7.4
+
+ 6 "Precursor" is now defined for all cases in which a References
+ header may be used (even though "followup" is not always defined
+ under Alternative-1).
+ 2.1
+
+ 7 Provision is made for a poster to use a mailbox ending in
+ ".invalid" in a From header (formerly in a-5.2).
+ 7.5
+
+ 8 "Inheritable" and "Variant" headers defined (formerly in a-
+ 4.2.5).
+ 2.3
+
+ 9 Additional wording regarding function of verb/arguments/body in
+ control messages (formerly in a-6.13).
+ 6
+
+ 10 NOTE regarding not altering message indentifiers during
+ transport or copying added (formerly in a-5.3).
+ 7.3
+
+ 11 All mention of MIME-style parameters and extension-parameters
+ removed.
+ 3.1
+ 7.6