1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
|
<pre>Internet Engineering Task Force (IETF) F. Ellermann
Request for Comments: 5538 xyzzy
Category: Standards Track April 2010
ISSN: 2070-1721
<span class="h1">The 'news' and 'nntp' URI Schemes</span>
Abstract
This memo specifies the 'news' and 'nntp' Uniform Resource Identifier
(URI) schemes that were originally defined in <a href="./rfc1738">RFC 1738</a>. The purpose
of this document is to allow <a href="./rfc1738">RFC 1738</a> to be made obsolete while
keeping the information about these schemes on the Standards Track.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/5538">http://www.rfc-editor.org/info/5538</a>.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
<span class="grey">Ellermann Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. Background . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. 'nntp' URIs . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. 'news' URIs . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2.3">2.3</a>. Query Parts, Fragments, and Normalization . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3">3</a>. Syntax of 'nntp' URIs . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4">4</a>. Syntax of 'news' URIs . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-5">5</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6">6</a>. Internationalization Considerations . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-8.1">8.1</a>. 'snews' URIs . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-8.2">8.2</a>. 'news-message-ID' Access Type . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-9">9</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-9.1">9.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-9.2">9.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#appendix-A">Appendix A</a>. Collected ABNF . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#appendix-B">Appendix B</a>. Detailed Example . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<span class="grey">Ellermann Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The first definition for many URI schemes appears in [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>]. This
memo extracts the 'news' and 'nntp' URI schemes from it to allow that
material to remain on the Standards Track if [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>] is moved to
"historic" status. It belongs to a series of similar documents like
[<a href="./rfc4156" title=""The wais URI Scheme"">RFC4156</a>], [<a href="./rfc4157" title=""The prospero URI Scheme"">RFC4157</a>], [<a href="./rfc4248" title=""The telnet URI Scheme"">RFC4248</a>], and [<a href="./rfc4266" title=""The gopher URI Scheme"">RFC4266</a>], which are discussed
on the <mailto:uri@w3.org> list.
The definitions for the 'news' and 'nntp' URI schemes given here are
updates from [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>] based on modern usage of these schemes. This
memo intentionally limits its description of the 'news' URI scheme to
essential features supposed to work with "any browser" and Network
News Transfer Protocol (NNTP) server.
[<a id="ref-RFC3986">RFC3986</a>] specifies how to define schemes for URIs; it also explains
the term "Uniform Resource Locator" (URL). The Network News Transfer
Protocol (NNTP) is specified in [<a href="./rfc3977" title=""Network News Transfer Protocol (NNTP)"">RFC3977</a>]. The Netnews Article
Format is defined in [<a href="./rfc5536" title=""Netnews Article Format"">RFC5536</a>].
The key word "MUST" in this memo is to be interpreted as described in
[<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. UTF-8 is specified in [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>]. The syntax uses the
ABNF defined in [<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Background</span>
The 'news' and 'nntp' URI schemes identify resources on an NNTP
server, individual articles, individual newsgroups, or sets of
newsgroups.
User agents like Web browsers supporting these schemes use the NNTP
protocol to access the corresponding resources. The details of how
they do this, e.g., employing a separate or integrated newsreader,
depend on the implementation. The default <port> associated with
NNTP in [<a href="./rfc3977" title=""Network News Transfer Protocol (NNTP)"">RFC3977</a>] is 119.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. 'nntp' URIs</span>
The 'nntp' URI scheme identifies articles in a newsgroup on a
specific NNTP server. In [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] terminology, this means that
'nntp' URIs have a non-empty <authority> component; there is no
default <host> as for the 'file' or 'news' URI schemes.
Netnews is typically distributed among several news servers, using
the same newsgroup names but local article numbers. An article
available as number 10 in group "example" on server
"news.example.com" has most likely a different number on any other
<span class="grey">Ellermann Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
server where the same article is still available. Users allowed to
read and post articles on "their" server may not be allowed to access
articles on an "arbitrary" server specified in an 'nntp' URI.
For these reasons, the use of the 'nntp' URI scheme is limited, and
it is less widely supported by user agents than the similar 'news'
URI scheme.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. 'news' URIs</span>
The 'news' URI scheme identifies articles by their worldwide unique
"Message-ID", independent of the server and the newsgroup.
Newsreaders support access to articles by their "Message-ID", without
the overhead of a URI scheme. In simple cases, they do this directly
as an NNTP client of a default or currently used server as configured
by the user. More general user agents use the 'news' URI scheme to
distinguish "Message-IDs" from similar constructs such as other URI
schemes in contexts such as a plain text message body.
The 'news' URI scheme also allows the identification of newsgroups or
sets of newsgroups independent of a specific server. For Netnews, a
group "example" has the same name on any server carrying this group,
exotic cases involving gateways notwithstanding. To distinguish
"Message-IDs" and newsgroup names, the 'news' URI scheme relies on
the "@" between local part (left-hand side) and domain part (right-
hand side) of "Message-IDs".
[<a id="ref-RFC1738">RFC1738</a>] offered only one wildcard for sets of newsgroups in 'news'
URIs, a "*" used to refer to "all available newsgroups". In common
practice, this was extended to varying degrees by different user
agents. An NNTP extension known as <wildmat>, specified in [<a href="./rfc2980" title=""Common NNTP Extensions"">RFC2980</a>]
and now part of the base NNTP specification, allows pattern matching
in the style of the [<a href="#ref-POSIX" title=""The Open Group Base Specifications Issue 6"">POSIX</a>] "find" command. For the purpose of this
memo, this means that some additional special characters have to be
allowed in 'news' URIs, some of them percent-encoded as required by
the overall [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] URI syntax. User agents and NNTP servers not
yet compliant with [<a href="./rfc3977" title=""Network News Transfer Protocol (NNTP)"">RFC3977</a>] do not implement all parts of this new
feature.
Another commonly supported addition to the [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>] syntax is the
optional specification of a server at the beginning of 'news' URIs.
This optional <authority> component follows the overall [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]
syntax, preceded by a double slash "//" and terminated by the next
slash "/", question mark "?", number sign "#", or the end of the URI.
<span class="grey">Ellermann Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Query Parts, Fragments, and Normalization</span>
Fragments introduced by a number sign "#" are specified in [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>];
the semantics is independent of the URI scheme, and the resolution
depends on the media type.
This memo doesn't specify a query part introduced by a question mark
"?" for the 'news' and 'nntp' URI schemes, but some implementations
are known to use query parts instead of fragments internally to
address parts of a composite media type [<a href="./rfc2046" title=""Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"">RFC2046</a>] in Multipurpose
Internet Mail Extensions (MIME).
There are no special "." or ".." path segments in 'news' and 'nntp'
URLs. Please note that "." and ".." are not valid <newsgroup-name>s.
URI producers have to percent-encode some characters as specified
below (<a href="#section-4">Section 4</a>); otherwise, they MUST treat a "Message-ID" without
angle brackets for 'news' URLs as is, i.e., case-sensitive.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Syntax of 'nntp' URIs</span>
An 'nntp' URI identifies an article by its number in a given
newsgroup on a specified server, or it identifies the newsgroup
without article number.
nntpURL = "nntp:" server "/" group [ "/" article-number ]
server = "//" authority ; see <a href="./rfc3986">RFC 3986</a>
group = 1*( group-char / pct-encoded )
article-number = 1*16DIGIT ; see <a href="./rfc3977">RFC 3977</a>
group-char = ALPHA / DIGIT / "-" / "+" / "_" / "."
In the form with an <article-number>, the URL corresponds roughly to
the content of an <xref> header field as specified in [<a href="./rfc5536" title=""Netnews Article Format"">RFC5536</a>],
replacing its more general <article-locator> by the <article-number>
used with the NNTP.
A <newsgroup-name> as specified in [<a href="./rfc5536" title=""Netnews Article Format"">RFC5536</a>] consists of dot-
separated components. Each component contains one or more letters,
digits, "-" (hyphen-minus), "+", or "_" (underscore). These
characters can be directly used in a segment of a path in an
[<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>] URI; no percent-encoding is necessary. Example:
nntp://news.server.example/example.group.this/12345
A <wildmat-exact> newsgroup name as specified in [<a href="./rfc3977" title=""Network News Transfer Protocol (NNTP)"">RFC3977</a>] allows (in
theory) any <UTF8-non-ascii> (see <a href="#section-6">Section 6</a>) and most printable
US-ASCII characters, excluding "!", "*", ",", "?", "[", "\", and "]".
However, [<a href="./rfc5536" title=""Netnews Article Format"">RFC5536</a>] does not (yet) permit characters outside of
<span class="grey">Ellermann Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
<group-char> and so, to keep the syntax simple, the additional
characters are here covered by <pct-encoded> as defined in [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>],
since most of them have to be percent-encoded anyway (with a few
exceptions, such as ":", ";", and "~"). Example:
nntp://wild.server.example/example.group.n%2Fa/12345
In the form without <article-number>, the URL identifies a single
group on the specified server. This is also possible with an
equivalent 'news' URL, and the latter is better supported by user
agents. Example:
nntp://news.server.example/example.group.this
news://news.server.example/example.group.this
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Syntax of 'news' URIs</span>
A 'news' URI identifies an article by its unique "Message-ID", or it
identifies a set of newsgroups. Additionally, it can specify a
server; when the server is not specified, a configured default server
for Netnews access is used.
newsURL = "news:" [ server "/" ] ( article / newsgroups )
article = msg-id-core ; see <a href="./rfc5536">RFC 5536</a>
The form identifying an <article> is the <msg-id-core> from
[<a href="./rfc5536" title=""Netnews Article Format"">RFC5536</a>]; it is a "Message-ID" without angle brackets. According to
[<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>], characters that are in <gen-delims> (a subset of
<reserved>), together with the character "%", MUST be percent-encoded
(though it is not wrong to encode others). Specifically, the
characters allowed in <msg-id-core> that must be encoded are
"/" "?" "#" "[" "]" and "%"
Note that an agent which seeks to interpret a 'news' URI needs to
decode all percent-encoded characters before passing it on to an NNTP
server to be acted upon.
Please note that "%3E" (">") is not allowed; <msg-id-core> is
otherwise identical to
id-left "@" id-right
as defined in [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>].
The form identifying <newsgroups> corresponds to the [<a href="./rfc3977" title=""Network News Transfer Protocol (NNTP)"">RFC3977</a>]
<wildmat-pattern>, a newsgroup name with wildcards "*" and "?". Any
"?" has to be percent-encoded as "%3F" in this part of a URI.
<span class="grey">Ellermann Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
Examples (the first two are equivalent):
news://news.server.example/*
news://news.server.example/
news://wild.server.example/example.group.th%3Fse
news:example.group.*
news:example.group.this
Without wildcards, this form of the URL identifies a single group if
it is not empty. User agents would typically try to present an
overview of the articles available in this group, likely somehow
limiting this overview to the newest unread articles up to a
configured maximum.
With wildcards, user agents could try to list matching group names on
the specified or default server. Some user agents support only a
specific <group> without wildcards, or an optional single "*".
As noted above (<a href="#section-2.2">Section 2.2</a>), the presence of an "@" in a 'news' URI
disambiguates <article> and <newsgroups> for URI consumers. The new
<message-id> construct specified in [<a href="./rfc3977" title=""Network News Transfer Protocol (NNTP)"">RFC3977</a>] does not require an
"@". Since [<a href="./rfc0822" title=""Standard for the format of ARPA Internet text messages"">RFC0822</a>], the "Message-ID" syntax has been closely
related to the syntax of mail addresses with an "@" separating left-
hand side (local part of addresses, unique part of message
identifiers) and right-hand side (domain part), and this memo sticks
to the known [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>] practice.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
Henry Spencer was the driving force to adopt MIME in Netnews; he
registered the MIME 'message/external-body' access type
'news-message-ID', discussed below (<a href="#section-8.2">Section 8.2</a>), in 1993 as recalled
in "Son-of-1036" [<a href="./rfc1849" title=""Son of 1036"">RFC1849</a>].
"The 'news' URL scheme" [<a href="#ref-GILMAN" title=""The 'news' URL scheme"">GILMAN</a>], by Alfred S. Gilman (March 1998),
introduced additions to the original [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>] 'news' URI scheme.
Some of these ideas are now widely supported and reflected by the
revised 'news' URI scheme specified here.
Thanks to Alfred Hoenes, Charles Lindsey, Clive Feather, Chris
Newman, Ken Murchinson, Kjetil T. Homme, Lars Magne Ingebrigtsen,
Martin Duerst, Matt Seitz, Nicolas Krebs, Paul Hoffman, Pasi Eronen,
Roy T. Fielding, Russ Allbery, Stephane Bortzmeyer, and Tom Petch for
their feedback, contributions, or encouragement.
Bill Fenner's _xml2rfc validator_ and _ABNF checker_ were a great
help in the creation of (not only) this memo. The same goes for
various great _IETF tools_ written by Henrik Levkowetz.
<span class="grey">Ellermann Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Internationalization Considerations</span>
The URI schemes were updated to support percent-encoded UTF-8
characters in NNTP newsgroup names as specified in [<a href="./rfc3977" title=""Network News Transfer Protocol (NNTP)"">RFC3977</a>] and
[<a href="./rfc3987" title=""Internationalized Resource Identifiers (IRIs)"">RFC3987</a>].
The Netnews Article Format in [<a href="./rfc5536" title=""Netnews Article Format"">RFC5536</a>] does not yet allow UTF-8 in
<newsgroup-name>s; therefore, well-known Unicode and UTF-8 security
considerations are not listed below. For an overview, see [<a href="#ref-UTR36" title=""Unicode Security Considerations"">UTR36</a>]
and [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>].
The work on Email Address Internationalization (EAI), started in
[<a href="./rfc4952" title=""Overview and Framework for Internationalized Email"">RFC4952</a>], is not expected to change the syntax of a "Message-ID".
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
There are many security considerations for URI schemes discussed in
[<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. The NNTP protocol may use passwords in the clear for
authentication or offer no privacy, both of which are considered
extremely unsafe in current practice. Alternatives and further
security considerations with respect to the NNTP are discussed in
[<a href="./rfc4642" title=""Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)"">RFC4642</a>] and [<a href="./rfc4643" title=""Network News Transfer Protocol (NNTP) Extension for Authentication"">RFC4643</a>].
The syntax for the 'news' and 'nntp' URI schemes contains the general
<authority> construct with an optional <userinfo> defined in
[<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. As noted in [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>], the "user:password" form of a
<userinfo> is deprecated.
Articles on NNTP servers typically expire after some time. After
that time, corresponding 'news' and 'nntp' URLs may not work anymore
depending on the server. While a "Message-ID" is supposed to be
worldwide unique forever, the NNTP protocol does not guarantee this.
Under various conditions depending on the servers, the same
"Message-ID" could be used for different articles, and attackers
could try to distribute malicious content for known 'news' or 'nntp'
URLs.
If a URI does not match the generic syntax in [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>], it is
invalid, and broken URIs can cause havoc. Compare [<a href="./rfc5064" title=""The Archived-At Message Header Field"">RFC5064</a>] for
similar security considerations.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
The IANA registry of URI schemes has been updated to point to this
memo instead of [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>] for the 'news' and 'nntp' URI schemes.
<span class="grey">Ellermann Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. 'snews' URIs</span>
This section contains the [<a href="./rfc4395" title=""Guidelines and Registration Procedures for New URI Schemes"">RFC4395</a>] template for the registration of
the historical 'snews' scheme specified in [<a href="#ref-GILMAN" title=""The 'news' URL scheme"">GILMAN</a>].
URI scheme name: snews
Status: historical
URI scheme syntax: Same as for 'news' (<a href="#section-4">Section 4</a>)
URI scheme semantics:
Syntactically equivalent to 'news', but using NNTP
over SSL/TLS (SSL/TLS with security layer is
negotiated immediately after establishing the TCP
connection) with a default port of 563, registered
as "nntps"
Encoding considerations:
Same as for 'news' (<a href="#section-6">Section 6</a>)
Applications/protocols that use this URI scheme name:
For some user agents, 'snews' URLs trigger the use
of "nntps" instead of NNTP for their access on
Netnews
Interoperability considerations:
This URI scheme was not widely deployed; its
further use is deprecated in favor of ordinary
'news' URLs in conjunction with NNTP servers
supporting [<a href="./rfc4642" title=""Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)"">RFC4642</a>]
Security considerations:
See [<a href="./rfc4642" title=""Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)"">RFC4642</a>]; the use of a dedicated port for
secure variants of a protocol was discouraged in
[<a href="./rfc2595" title=""Using TLS with IMAP, POP3 and ACAP"">RFC2595</a>]
Contact: <mailto:uri@w3.org> (URI mailing list)
Change controller: IETF
References: <a href="./rfc5538">RFC 5538</a>, [<a href="./rfc4642" title=""Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)"">RFC4642</a>], [<a href="#ref-GILMAN" title=""The 'news' URL scheme"">GILMAN</a>]
<span class="grey">Ellermann Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. 'news-message-ID' Access Type</span>
The MIME 'news-message-ID' access type was erroneously listed as a
subtype. IANA has removed 'news-message-ID' from the application
subtype registry, and has added it to the access types registry
defined in [<a href="./rfc4289" title=""Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures"">RFC4289</a>].
[<a id="ref-RFC4289">RFC4289</a>] requires an RFC (preferably on the Standards Track) for the
access types registry. To provide a definition meeting this
requirement, the following paragraph is reproduced verbatim from
[<a href="./rfc1849" title=""Son of 1036"">RFC1849</a>]:
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.
Please note that 'news' URLs offer a very similar and (today) more
common way to access articles by their Message-ID; compare [<a href="./rfc2017" title=""Definition of the URL MIME External-Body Access-Type"">RFC2017</a>].
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3977">RFC3977</a>] Feather, C., "Network News Transfer Protocol (NNTP)",
<a href="./rfc3977">RFC 3977</a>, October 2006.
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter,
"Uniform Resource Identifier (URI): Generic Syntax",
STD 66, <a href="./rfc3986">RFC 3986</a>, January 2005.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, January 2008.
[<a id="ref-RFC5536">RFC5536</a>] Murchison, K., Lindsey, C., and D. Kohn, "Netnews
Article Format", <a href="./rfc5536">RFC 5536</a>, November 2009.
<span class="grey">Ellermann Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-GILMAN">GILMAN</a>] Gilman, A., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22The+%27news%27+URL+scheme%22'>"The 'news' URL scheme"</a>, Work in Progress,
March 1998.
[<a id="ref-POSIX">POSIX</a>] Institute of Electrical and Electronics Engineers,
"The Open Group Base Specifications Issue 6",
IEEE Standard 1003.1, 2004 edition.
[<a id="ref-RFC0822">RFC0822</a>] Crocker, D., "Standard for the format of ARPA Internet
text messages", STD 11, <a href="./rfc822">RFC 822</a>, August 1982.
[<a id="ref-RFC1738">RFC1738</a>] Berners-Lee, T., Masinter, L., and M. McCahill,
"Uniform Resource Locators (URL)", <a href="./rfc1738">RFC 1738</a>,
December 1994.
[<a id="ref-RFC1849">RFC1849</a>] Spencer, H., ""Son of 1036": News Article Format and
Transmission", <a href="./rfc1849">RFC 1849</a>, March 2010.
[<a id="ref-RFC2017">RFC2017</a>] Freed, N. and K. Moore, "Definition of the URL MIME
External-Body Access-Type", <a href="./rfc2017">RFC 2017</a>, October 1996.
[<a id="ref-RFC2046">RFC2046</a>] Freed, N. and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) Part Two: Media Types",
<a href="./rfc2046">RFC 2046</a>, November 1996.
[<a id="ref-RFC2595">RFC2595</a>] Newman, C., "Using TLS with IMAP, POP3 and ACAP",
<a href="./rfc2595">RFC 2595</a>, June 1999.
[<a id="ref-RFC2980">RFC2980</a>] Barber, S., "Common NNTP Extensions", <a href="./rfc2980">RFC 2980</a>,
October 2000.
[<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003.
[<a id="ref-RFC3987">RFC3987</a>] Duerst, M. and M. Suignard, "Internationalized
Resource Identifiers (IRIs)", <a href="./rfc3987">RFC 3987</a>, January 2005.
[<a id="ref-RFC4156">RFC4156</a>] Hoffman, P., "The wais URI Scheme", <a href="./rfc4156">RFC 4156</a>,
August 2005.
[<a id="ref-RFC4157">RFC4157</a>] Hoffman, P., "The prospero URI Scheme", <a href="./rfc4157">RFC 4157</a>,
August 2005.
[<a id="ref-RFC4248">RFC4248</a>] Hoffman, P., "The telnet URI Scheme", <a href="./rfc4248">RFC 4248</a>,
October 2005.
<span class="grey">Ellermann Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
[<a id="ref-RFC4266">RFC4266</a>] Hoffman, P., "The gopher URI Scheme", <a href="./rfc4266">RFC 4266</a>,
November 2005.
[<a id="ref-RFC4289">RFC4289</a>] Freed, N. and J. Klensin, "Multipurpose Internet Mail
Extensions (MIME) Part Four: Registration Procedures",
<a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, <a href="./rfc4289">RFC 4289</a>, December 2005.
[<a id="ref-RFC4395">RFC4395</a>] Hansen, T., Hardie, T., and L. Masinter, "Guidelines
and Registration Procedures for New URI Schemes",
<a href="https://www.rfc-editor.org/bcp/bcp35">BCP 35</a>, <a href="./rfc4395">RFC 4395</a>, February 2006.
[<a id="ref-RFC4642">RFC4642</a>] Murchison, K., Vinocur, J., and C. Newman, "Using
Transport Layer Security (TLS) with Network News
Transfer Protocol (NNTP)", <a href="./rfc4642">RFC 4642</a>, October 2006.
[<a id="ref-RFC4643">RFC4643</a>] Vinocur, J. and K. Murchison, "Network News Transfer
Protocol (NNTP) Extension for Authentication",
<a href="./rfc4643">RFC 4643</a>, October 2006.
[<a id="ref-RFC4952">RFC4952</a>] Klensin, J. and Y. Ko, "Overview and Framework for
Internationalized Email", <a href="./rfc4952">RFC 4952</a>, July 2007.
[<a id="ref-RFC5064">RFC5064</a>] Duerst, M., "The Archived-At Message Header Field",
<a href="./rfc5064">RFC 5064</a>, December 2007.
[<a id="ref-RFC5322">RFC5322</a>] Resnick, P., Ed., "Internet Message Format", <a href="./rfc5322">RFC 5322</a>,
October 2008.
[<a id="ref-UTR36">UTR36</a>] Davis, M. and M. Suignard, "Unicode Security
Considerations", Unicode Technical Reports #36,
August 2006.
<span class="grey">Ellermann Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Collected ABNF</span>
In addition to the syntax given above, this appendix also lists the
sources of terms used in comments and the prose:
nntpURL = "nntp:" server "/" group [ "/" article-number ]
server = "//" authority ; see <a href="./rfc3986">RFC 3986</a>
group = 1*( group-char / pct-encoded )
article-number = 1*16DIGIT ; see <a href="./rfc3977">RFC 3977</a>
group-char = ALPHA / DIGIT / "-" / "+" / "_" / "."
newsURL = "news:" [ server "/" ] ( article / newsgroups )
article = msg-id-core ; see <a href="./rfc5536">RFC 5536</a>
newsgroups = *( group-char / pct-encoded / "*" )
authority = <see <a href="./rfc3986#section-3.2">RFC 3986 Section 3.2</a>>
host = <see <a href="./rfc3986#section-3.2.2">RFC 3986 Section 3.2.2</a>>
pct-encoded = <see <a href="./rfc3986#section-2.1">RFC 3986 Section 2.1</a>>
port = <see <a href="./rfc3986#section-3.2.3">RFC 3986 Section 3.2.3</a>>
gen-delims = <see <a href="./rfc3986#section-2.2">RFC 3986 Section 2.2</a>>
msg-id-core = <see <a href="./rfc5536#section-3.1.3">RFC 5536 Section 3.1.3</a>>
reserved = <see <a href="./rfc5536#section-2.2">RFC 5536 Section 2.2</a>>
userinfo = <see <a href="./rfc3986#section-3.2.1">RFC 3986 Section 3.2.1</a>>
message-id = <see <a href="./rfc3977#section-9.8">RFC 3977 Section 9.8</a>>
UTF8-non-ascii = <see <a href="./rfc3977#section-9.8">RFC 3977 Section 9.8</a>>
wildmat = <see <a href="./rfc3977#section-4.1">RFC 3977 Section 4.1</a>>
wildmat-exact = <see <a href="./rfc3977#section-4.1">RFC 3977 Section 4.1</a>>
wildmat-pattern = <see <a href="./rfc3977#section-4.1">RFC 3977 Section 4.1</a>>
ALPHA = <see <a href="./rfc5234#appendix-B.1">RFC 5234 Appendix B.1</a>>
DIGIT = <see <a href="./rfc5234#appendix-B.1">RFC 5234 Appendix B.1</a>>
article-locator = <see <a href="./rfc5536#section-3.2.14">RFC 5536 Section 3.2.14</a>>
newsgroup-name = <see <a href="./rfc5536#section-3.1.4">RFC 5536 Section 3.1.4</a>>
xref = <see <a href="./rfc5536#section-3.2.14">RFC 5536 Section 3.2.14</a>>
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Detailed Example</span>
Here is an example of a mail to the <mailto:tools.discuss@ietf.org>
list with "Message-ID" <p0624081dc30b8699bf9b@[10.20.30.108]>.
<<a href="http://dir.gmane.org/gmane.ietf.tools">http://dir.gmane.org/gmane.ietf.tools</a>> is one of the various list
archives; it converts mail into Netnews articles. The header of this
article contains the following fields (among others):
<span class="grey">Ellermann Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc5538">RFC 5538</a> 'news' and 'nntp' URIs April 2010</span>
Message-ID: <p0624081dc30b8699bf9b@[10.20.30.108]>
Xref: news.gmane.org gmane.ietf.tools:742
Archived-At: <<a href="http://permalink.gmane.org/gmane.ietf.tools/742">http://permalink.gmane.org/gmane.ietf.tools/742</a>>
The "Xref" roughly indicates the 742nd article in newsgroup
<news://news.gmane.org/gmane.ietf.tools> on this server. An 'nntp'
URL might be <nntp://news.gmane.org/gmane.ietf.tools/742>. For
details about the "Archived-At" URL, see [<a href="./rfc5064" title=""The Archived-At Message Header Field"">RFC5064</a>].
The list software and list subscribers reading the list elsewhere
can't predict a server-specific article number 742 in this archive.
If they know this server, they can however guess the corresponding
<news://news.gmane.org/p0624081dc30b8699bf9b@%5B10.20.30.108%5D> URL.
In theory, the list software could use the guessed 'news' URL in an
"Archived-At" header field, but if a list tries this, it would likely
use <<a href="http://mid.gmane.org/p0624081dc30b8699bf9b@%5B10.20.30.108%5D">http://mid.gmane.org/p0624081dc30b8699bf9b@%5B10.20.30.108%5D</a>>.
Using domain literals in a "Message-ID" could cause collisions. A
collision might force the mail2news gateway in this example to invent
a new "Message-ID", and an attempt to guess the future URL on this
server would then fail.
Author's Address
Frank Ellermann
xyzzy
Hamburg, Germany
EMail: hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com
URI: <a href="http://purl.net/xyzzy/">http://purl.net/xyzzy/</a>
Ellermann Standards Track [Page 14]
</pre>
|
