forked from jcgregorio/uri-templates
-
Notifications
You must be signed in to change notification settings - Fork 2
/
rfc2629-README.txt
1736 lines (822 loc) · 49.3 KB
/
rfc2629-README.txt
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
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
The README file M. Rose
Dover Beach Consulting, Inc.
B. Fenner
Arista Networks, Inc.
C. Levert
T. Hansen
AT&T Labs
J. Reschke
greenbytes
January 2011
xml2rfc v1.36pre1
Rose, et al. [Page 1]
README xml2rfc v1.36pre1 January 2011
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . 4
3. Testing . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Testing under a windowing system . . . . . . . . . . . . . 5
3.2. Testing without a windowing system . . . . . . . . . . . . 5
4. Next steps . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Processing Instructions . . . . . . . . . . . . . . . . . 6
4.1.1. Option Settings . . . . . . . . . . . . . . . . . . . . . 6
4.1.2. Include Files . . . . . . . . . . . . . . . . . . . . . . 11
5. The Page Model . . . . . . . . . . . . . . . . . . . . . . 13
6. Additions to RFC 2629 . . . . . . . . . . . . . . . . . . 14
6.1. Extra Attributes . . . . . . . . . . . . . . . . . . . . . 14
6.2. Typed-Artwork Interpretation . . . . . . . . . . . . . . . 15
7. Limitations of xml2rfc . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . 18
A. Producing the IETF 'Boilerplate' . . . . . . . . . . . . . 19
A.1. The /rfc/@ipr Attribute . . . . . . . . . . . . . . . . . 19
A.1.1. Current Values: '*trust200902' . . . . . . . . . . . . . . 20
A.1.2. Historic Values . . . . . . . . . . . . . . . . . . . . . 21
A.2. The /rfc/@category Attribute . . . . . . . . . . . . . . . 22
A.3. The /rfc/@submissionType Attribute . . . . . . . . . . . . 22
A.4. The /rfc/@consensus Attribute . . . . . . . . . . . . . . 23
A.5. The /rfc/@number Attribute . . . . . . . . . . . . . . . . 23
A.6. The /rfc/@docName Attribute . . . . . . . . . . . . . . . 23
A.7. The /rfc/@obsoletes Attribute . . . . . . . . . . . . . . 24
A.8. The /rfc/@updates Attribute . . . . . . . . . . . . . . . 24
B. MacOS 9 Installation (courtesy of Ned Freed) . . . . . . . 25
C. rfc2629.xslt (courtesy of Julian Reschke) . . . . . . . . 26
D. MS-Windows/Cygwin Installation (courtesy of Joe Touch) . . 27
E. A Special Thanks . . . . . . . . . . . . . . . . . . . . . 28
F. Copyrights . . . . . . . . . . . . . . . . . . . . . . . . 29
Index . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 31
Rose, et al. [Page 2]
README xml2rfc v1.36pre1 January 2011
1. Introduction
This is a package to convert memos written in XML to the RFC format.
If you don't want to install any software, you can use the web-based
service [5].
Rose, et al. [Page 3]
README xml2rfc v1.36pre1 January 2011
2. Requirements
You need to have Tcl/Tk version 8 running on your system. Tcl is a
scripting language, Tk is Tcl with support for your windowing system.
To get a source or binary distribution for your system, go to the Tcl
Developer Xchange website [6] and install it. If you get the binary
distribution, this is pretty simple.
Of course, you may already have Tcl version 8. To find out, try
typing this command from the shell (or the "MS-DOS Prompt"):
% tclsh
If the program launches, you're good to go with Tcl version 8.
If you are running under a windowing system (e.g., X or MS-Windows),
you can also try:
% wish
If a new window comes up along with a "Console" window, then you're
good to go with Tk version 8.
Finally, you may notice a file called "xml2sgml.tcl" in the
distribution. It contains some extra functionality for a few special
users -- so, if you don't know what it is, don't worry about it...
Rose, et al. [Page 4]
README xml2rfc v1.36pre1 January 2011
3. Testing
Now test your installation.
3.1. Testing under a windowing system
Type this command from the shell:
% xml2rfc.tcl
A new window should come up that looks like this:
+------------------------------------------------------------+
| Convert XML to RFC |
| |
| Select input file: ____________________________ [Browse] |
| |
| Select output file: ____________________________ [Browse] |
| |
| [Convert] [Quit] |
| |
+------------------------------------------------------------+
Fill-in the blanks and click on [Convert].
3.2. Testing without a windowing system
Type this command from the shell:
% tclsh
If the program launches, type this command to it:
% source xml2rfc.tcl
and you should see these five lines:
invoke as "xml2rfc input-file output-file"
or "xml2txt input-file"
or "xml2html input-file"
or "xml2nroff input-file"
or "xml2unpg input-file"
Rose, et al. [Page 5]
README xml2rfc v1.36pre1 January 2011
4. Next steps
Read the 2629bis [7] document. In particular, Section 3 has some
good information.
4.1. Processing Instructions
A _processing instruction_ contains directives to an XML application.
If you want to give directives to *xml2rfc*, the processing
instructions (PIs) look like this:
<?rfc keyword='value'?>
Of course, if you like the default behavior, you don't need any
behavior-modifying directives in your input file! Although *xml2rfc*
supports putting several attribute-like directives in one PI, be
warned that there are issues in doing this for a non-include-file
directive following an include-file directive (Section 4.1.2). It is
good practice to always surround the value with either single or
double quotes.
4.1.1. Option Settings
The list of valid keywords are:
+---------------------+--------------+------------------------------+
| keyword | default | meaning |
+---------------------+--------------+------------------------------+
| artworkdelimiter | "" | when producing txt or nroff |
| | | files, use this string to |
| | | delimit artwork |
| | | |
| artworklines | 0 | when producing txt or nroff |
| | | files, add this many blank |
| | | lines around artwork |
| | | |
| authorship | yes | render author information |
| | | |
| autobreaks | yes | automatically force page |
| | | breaks to avoid widows and |
| | | orphans (not perfect) |
| | | |
| background | "" | when producing a html file, |
| | | use this image |
| | | |
| colonspace | no | put two spaces instead of |
| | | one after each colon (":") |
| | | in txt or nroff files |
Rose, et al. [Page 6]
README xml2rfc v1.36pre1 January 2011
| comments | no | render <cref> information |
| | | |
| compact | (rfcedstyle) | when producing a txt/nroff |
| | | file, try to conserve |
| | | vertical whitespace (the |
| | | default value is the current |
| | | value of the rfcedstyle PI) |
| | | |
| docmapping | no | use hierarchical tags (e.g., |
| | | <h1>, <h2>, etc.) for |
| | | (sub)section titles |
| | | |
| editing | no | insert editing marks for |
| | | ease of discussing draft |
| | | versions |
| | | |
| emoticonic | no | automatically replaces input |
| | | sequences such as "|*text|" |
| | | by, e.g., |
| | | "<strong>text</strong>" in |
| | | html output |
| | | |
| footer | "" | override the center footer |
| | | string |
| | | |
| header | "" | override the leftmost header |
| | | string |
| | | |
| include | n/a | see Section 4.1.2 |
| | | |
| inline | no | if comments is "yes", then |
| | | render comments inline; |
| | | otherwise render them in an |
| | | "Editorial Comments" section |
| | | |
| iprnotified | no | include boilerplate from |
| | | Section 10.4(d) of [1] |
| | | |
| linkmailto | yes | generate mailto: URL, as |
| | | appropriate |
| | | |
Rose, et al. [Page 7]
README xml2rfc v1.36pre1 January 2011
| linefile | n/a | a string like "35:file.xml" |
| | | or just "35" (file name then |
| | | defaults to the containing |
| | | file's real name or to the |
| | | latest linefile |
| | | specification that changed |
| | | it) that will be used to |
| | | override *xml2rfc*'s |
| | | reckoning of the current |
| | | input position (right after |
| | | this PI) for warning and |
| | | error reporting purposes |
| | | (line numbers are 1-based) |
| | | |
| needLines | n/a | an integer hint indicating |
| | | how many contiguous lines |
| | | are needed at this point in |
| | | the output |
| | | |
| notedraftinprogress | yes | generates "(work in |
| | | progress)", as appropriate |
| | | |
| private | "" | produce a private memo |
| | | rather than an RFC or |
| | | Internet-Draft |
| | | |
| refparent | "References" | title of the top-level |
| | | section containing all |
| | | references |
| | | |
Rose, et al. [Page 8]
README xml2rfc v1.36pre1 January 2011
| rfcedstyle | no | attempt to closely follow |
| | | finer details from the |
| | | latest observable RFC-Editor |
| | | style so as to minimize the |
| | | probability of being sent |
| | | back corrections after |
| | | submission; this directive |
| | | is a kludge whose exact |
| | | behavior is likely to change |
| | | on a regular basis to match |
| | | the current flavor of the |
| | | month; presently, it will |
| | | capitalize the adjective |
| | | "This" in automatically |
| | | generated headings, use the |
| | | variant "acknowledgement" |
| | | spelling instead of Merriam |
| | | Webster's main |
| | | "acknowledgment" dictionary |
| | | entry, use the "eMail" |
| | | spelling instead of Knuth's |
| | | more modern "email" |
| | | spelling, only put one blank |
| | | line instead of two before |
| | | top sections, omit |
| | | "Intellectual Property and |
| | | Copyright Statements" and |
| | | "Author's Address" from the |
| | | table of content, and not |
| | | limit the indentation to a |
| | | maximum tag length in |
| | | <references> sections. |
| | | |
| rfcprocack | no | if there already is an |
| | | automatically generated |
| | | Acknowledg(e)ment section, |
| | | pluralize its title and add |
| | | a short sentence |
| | | acknowledging that *xml2rfc* |
| | | was used in the document's |
| | | production to process an |
| | | input XML source file in |
| | | RFC-2629 format |
| | | |
| slides | no | when producing a html file, |
| | | produce multiple files for a |
| | | slide show |
| | | |
Rose, et al. [Page 9]
README xml2rfc v1.36pre1 January 2011
| sortrefs | no | sort references |
| | | |
| strict | no | try to enforce the ID-nits |
| | | conventions and DTD validity |
| | | |
| subcompact | (compact) | if compact is "yes", then |
| | | you can make things a little |
| | | less compact by setting this |
| | | to "no" (the default value |
| | | is the current value of the |
| | | compact PI) |
| | | |
| symrefs | yes | use anchors rather than |
| | | numbers for references |
| | | |
| text-list-sybols | o*+- | modify the list of symbols |
| | | used (when generated text) |
| | | for list type="symbols". For |
| | | example, specifying "abcde" |
| | | will cause "a" to be used |
| | | for 1st level, "b" for the |
| | | 2nd level, etc, cycling back |
| | | to the first character "a" |
| | | at the 6th level. Specifying |
| | | "o*" will cause the |
| | | characters "o" and "*" to be |
| | | alternated for each |
| | | successive level. |
| | | |
| toc | no | generate a table-of-contents |
| | | |
| tocappendix | yes | control whether the word |
| | | "Appendix" appears in the |
| | | table-of-content |
| | | |
| tocdepth | 3 | if toc is "yes", then this |
| | | determines the depth of the |
| | | table-of-contents |
| | | |
| tocindent | yes | if toc is "yes", then |
| | | setting this to "yes" will |
| | | indent subsections in the |
| | | table-of-contents |
| | | |
| tocnarrow | yes | affects horizontal spacing |
| | | in the table-of-content |
| | | |
Rose, et al. [Page 10]
README xml2rfc v1.36pre1 January 2011
| tocompact | yes | if toc is "yes", then |
| | | setting this to "no" will |
| | | make it a little less |
| | | compact |
| | | |
| topblock | yes | put the famous header block |
| | | on the first page |
| | | |
| typeout | n/a | during processing pass 2, |
| | | print the value to standard |
| | | output at that point in |
| | | processing |
| | | |
| useobject | no | when producing a html file, |
| | | use the "<object>" html |
| | | element with inner |
| | | replacement content instead |
| | | of the "<img>" html element, |
| | | when a source xml element |
| | | includes an "src" attribute |
+---------------------+--------------+------------------------------+
Remember that, as with everything else in XML, keywords and values
are case-sensitive.
With the exception of the "needLines", "typeout", and "include"
directives, you normally put all of these processing instructions at
the beginning of the document (right after the XML declaration).
4.1.2. Include Files
*xml2rfc* has an include-file facility, e.g.,
<?rfc include='file'?>
*xml2rfc* will consult the "XML_LIBRARY" environment variable for a
search path of where to look for files. (If this environment
variable isn't set, the directory containing the file that contains
the include-file directive is used.) The file's contents are
inserted right after the PI. Putting non-include-file directives
(especially needLines ones) after an include-file one in the same PI
may not work as expected because of this. Remember that file names
are generally case-sensitive and that an input file that is
distributed to the outside world may be processed on a different
operating system than that used by its author.
Rose, et al. [Page 11]
README xml2rfc v1.36pre1 January 2011
You can also have *xml2rfc* set the "XML_LIBRARY" environment
variable directly, by creating a file called ".xml2rfc.rc" in the
directory where your main file is, e.g.,
global env tcl_platform
if {![string compare $tcl_platform(platform) windows]} {
set sep ";"
} else {
set sep ":"
}
if {[catch { set env(XML_LIBRARY) } library]} {
set library ""
foreach bibxmlD [lsort -dictionary \
[glob -nocomplain $HOME/rfcs/bibxml/*]] {
append library $sep$bibxmlD
}
}
set nativeD [file nativename $inputD]
if {[lsearch [split $library $sep] $nativeD] < 0} {
set library "$nativeD$sep$library"
}
set env(XML_LIBRARY) $library
There are links to various bibliographic databases (RFCs, I-Ds, and
so on) on the *xml2rfc* homepage [5].
Rose, et al. [Page 12]
README xml2rfc v1.36pre1 January 2011
5. The Page Model
The *html* rendering engine does not need to have a tightly defined
page model.
The *txt* and *nr* rendering engines assume the following page model.
Each line has at most 72 columns from the left edge, including any
left margin, but excluding the line terminator. Every output
character is from the ASCII repertoire and the only control character
used is the line-feed (LF); the character-tabulation (HT) character
is never used.
Each page has the following lines (in 1-based numbering, as reported
to the user, but contrary to *xml2rfc*'s internal 0-based numbering):
1: header line (blank line on first page)
2: blank line
3: blank line
4: 1st line of content
...
51: 48th line of content
52: blank line
53: blank line
54: blank line
55: footer line
56: form-feed character (followed by line terminator)
Once processed through *nroff* and the "fix.sh" script (from
2-nroff.template [8]), the *nr* output differs from this in two ways.
It has three extra blank lines (that could be numbered -2, -1, and 0,
for a total of six) at the very beginning of the document (so the
first page is that much longer). It also has no line terminator
following the very last form-feed character of the file. These
differences originate in the design of the "fix.sh" script.
Header and footer lines each have three parts: left, center, and
right.
Rose, et al. [Page 13]
README xml2rfc v1.36pre1 January 2011
6. Additions to RFC 2629
A few additions have been made to the format originally defined in
RFC 2629. In particular, Appendix C of the 2629bis document
enumerates the additions.
6.1. Extra Attributes
In addition, *xml2rfc* recognizes the undocumented "src", "alt",
"width", and "height" attributes in the "figure" and "artwork"
elements, but only if HTML is being generated. Here are two
examples, one for each case.
Here, the attributes are added to the "artwork" element.
<figure>
<preamble>This is the preamble.</preamble>
<artwork src='layers.png'
alt='[picture of layers only]'>
.-----------.
| ASCII art |
`-----------'
</artwork>
<postamble>This is the postamble.</postamble>
</figure>
In this case, the "preamble" and "postamble" elements are kept and an
"img" tag is placed in the HTML output to replace the whole "artwork"
element and its textual drawing, which are ignored.
Here, the attributes are added to the "figure" element.
<figure src='layers.png'
alt='[picture of layers and explanation]'>
<preamble>This is the preamble.</preamble>
<artwork>
.-----------.
| ASCII art |
`-----------'
</artwork>
<postamble>This is the postamble.</postamble>
</figure>
In this case, an "img" tag is placed in the HTML output to replace
the whole contents of the "figure" element (the "preamble",
"artwork", and "postamble" inner elements and the textual drawing
itself) which are ignored.
Rose, et al. [Page 14]
README xml2rfc v1.36pre1 January 2011
*xml2rfc* also recognizes an undocumented "align" attribute (with
possible values "left", "center", or "right") in the "figure" and
"artwork" elements. It affects the whole content of the targeted
element for all types of generated output. Its default is inherited
from the parent of its element.
6.2. Typed-Artwork Interpretation
The "artwork" element from RFC 2629 supports an optional "type"
attribute. While most possible values are just ignored, including
the special case where the attribute is unspecified or just empty,
some values are recognized. In particular, "type='abnf'" can be used
if the "artwork" contains an Augmented Backus-Naur Form (ABNF) syntax
specification [3]. As a special extension in its _behavior_,
*xml2rfc* will attempt to validate the syntax and colorize the HTML
output of ABNF, since it is so widely used in RFCs. It does this
colorizing by relying on the full parsing it does right before, not
on a quick and partial (e.g., line-by-line) pattern-based hack. ABNF
is the only artwork type to benefit from this kind of internal
support at this time. If the "strict" rfc-PI directive is activated,
invalid ABNF content will cause *xml2rfc* to abort with an error
message. Omitting the "type" attribute altogether is the obvious way
to avoid having this validation and colorizing performed.
Rose, et al. [Page 15]
README xml2rfc v1.36pre1 January 2011
For example (to be viewed in HTML):
char-val = DQUOTE *(%x20-21 / %x23-7E) DQUOTE
; quoted string of SP and VCHAR
without DQUOTE
num-val = "%" (bin-val / dec-val / hex-val)
bin-val = "b" 1*BIT
[ 1*("." 1*BIT) / ("-" 1*BIT) ]
; series of concatenated bit values
; or single ONEOF range
dec-val = "d" 1*DIGIT
[ 1*("." 1*DIGIT) / ("-" 1*DIGIT) ]
hex-val = "x" 1*HEXDIG
[ 1*("." 1*HEXDIG) / ("-" 1*HEXDIG) ]
prose-val = "<" *(%x20-3D / %x3F-7E) ">"
; bracketed string of SP and VCHAR
without angles
; prose description, to be used as
last resort
This is from the original RFC on ABNF [2], with its minor mistakes in
manually folded comment lines purposely left intact, for
illustration. Since the result is still valid ABNF (but incorrect
with respect to what was intended), this showcases how colorizing
might give a human author (or editor or reader) a better chance to
spot the three mistakes (and correct them, e.g., with extra
semicolons, as has been done in a more recent version [3] of the ABNF
specification). Note that it is the white space characters at the
beginning of the subsequent lines (including the commented ones) that
conspire to extend the reach of those rules across several lines.
Rose, et al. [Page 16]
README xml2rfc v1.36pre1 January 2011
7. Limitations of xml2rfc
o The "figure" element's "title" attribute is ignored, except when
generating HTML.
o The "xref" element's "pageno" attribute is ignored.
Rose, et al. [Page 17]
README xml2rfc v1.36pre1 January 2011
8. References
[1] Bradner, S., "The Internet Standards Process -- Revision 3",
BCP 9, RFC 2026, October 1996.
[2] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[3] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, October 2005.
[4] Daigle, L. and O. Kolkman, "RFC Streams, Headers, and
Boilerplates", RFC 5741, December 2009.
[5] <http://xml.resource.org/>
[6] <http://www.tcl.tk/software/tcltk/8.4.html>
[7] <draft-mrose-writing-rfcs.html>
[8] <ftp://ftp.rfc-editor.org/in-notes/rfc-editor/2-nroff.template>
[9] <http://greenbytes.de/tech/webdav/rfc2629.xslt>
[10] <http://greenbytes.de/tech/webdav/rfc2629xslt.zip>
[11] <http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html>
[12] <http://www.cygwin.com/>
[13] <http://wiki.tcl.tk/2?cygwin>