1 | |
---|
2 | |
---|
3 | |
---|
4 | Network Working Group J. Doe |
---|
5 | Request for Comments: 3223 January 2002 |
---|
6 | Category: Informational |
---|
7 | |
---|
8 | |
---|
9 | Default RFC IPR (w. iprnotified PI set to yes) as of January 2002 |
---|
10 | |
---|
11 | Status of this Memo |
---|
12 | |
---|
13 | This memo provides information for the Internet community. It does |
---|
14 | not specify an Internet standard of any kind. Distribution of this |
---|
15 | memo is unlimited. |
---|
16 | |
---|
17 | Copyright Notice |
---|
18 | |
---|
19 | Copyright (C) The Internet Society (2002). All Rights Reserved. |
---|
20 | |
---|
21 | Abstract |
---|
22 | |
---|
23 | This is a test case document, it is not RFC 3223 (which was never |
---|
24 | issued by the RFC-Editor). |
---|
25 | |
---|
26 | |
---|
27 | 1. Dummy Section |
---|
28 | |
---|
29 | Dummy Section. |
---|
30 | |
---|
31 | |
---|
32 | Author's Address |
---|
33 | |
---|
34 | John Doe |
---|
35 | |
---|
36 | |
---|
37 | |
---|
38 | |
---|
39 | |
---|
40 | |
---|
41 | |
---|
42 | |
---|
43 | |
---|
44 | |
---|
45 | |
---|
46 | |
---|
47 | |
---|
48 | |
---|
49 | |
---|
50 | |
---|
51 | |
---|
52 | |
---|
53 | |
---|
54 | |
---|
55 | Doe Informational [Page 1] |
---|
56 | |
---|
57 | RFC 3223 default RFC IPR example January 2002 |
---|
58 | |
---|
59 | |
---|
60 | Full Copyright Statement |
---|
61 | |
---|
62 | Copyright (C) The Internet Society (2002). All Rights Reserved. |
---|
63 | |
---|
64 | This document and translations of it may be copied and furnished to |
---|
65 | others, and derivative works that comment on or otherwise explain it |
---|
66 | or assist in its implementation may be prepared, copied, published |
---|
67 | and distributed, in whole or in part, without restriction of any |
---|
68 | kind, provided that the above copyright notice and this paragraph are |
---|
69 | included on all such copies and derivative works. However, this |
---|
70 | document itself may not be modified in any way, such as by removing |
---|
71 | the copyright notice or references to the Internet Society or other |
---|
72 | Internet organizations, except as needed for the purpose of |
---|
73 | developing Internet standards in which case the procedures for |
---|
74 | copyrights defined in the Internet Standards process must be |
---|
75 | followed, or as required to translate it into languages other than |
---|
76 | English. |
---|
77 | |
---|
78 | The limited permissions granted above are perpetual and will not be |
---|
79 | revoked by the Internet Society or its successors or assigns. |
---|
80 | |
---|
81 | This document and the information contained herein is provided on an |
---|
82 | "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
---|
83 | TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
---|
84 | BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
---|
85 | HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
---|
86 | MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
---|
87 | |
---|
88 | |
---|
89 | Intellectual Property |
---|
90 | |
---|
91 | The IETF takes no position regarding the validity or scope of any |
---|
92 | intellectual property or other rights that might be claimed to |
---|
93 | pertain to the implementation or use of the technology described in |
---|
94 | this document or the extent to which any license under such rights |
---|
95 | might or might not be available; neither does it represent that it |
---|
96 | has made any effort to identify any such rights. Information on the |
---|
97 | IETF's procedures with respect to rights in standards-track and |
---|
98 | standards-related documentation can be found in BCP 11. Copies of |
---|
99 | claims of rights made available for publication and any assurances of |
---|
100 | licenses to be made available, or the result of an attempt made to |
---|
101 | obtain a general license or permission for the use of such |
---|
102 | proprietary rights by implementors or users of this specification can |
---|
103 | be obtained from the IETF Secretariat. |
---|
104 | |
---|
105 | The IETF invites any interested party to bring to its attention any |
---|
106 | copyrights, patents or patent applications, or other proprietary |
---|
107 | rights which may cover technology that may be required to practice |
---|
108 | |
---|
109 | |
---|
110 | |
---|
111 | Doe Informational [Page 2] |
---|
112 | |
---|
113 | RFC 3223 default RFC IPR example January 2002 |
---|
114 | |
---|
115 | |
---|
116 | this standard. Please address the information to the IETF Executive |
---|
117 | Director. |
---|
118 | |
---|
119 | The IETF has been notified of intellectual property rights claimed in |
---|
120 | regard to some or all of the specification contained in this |
---|
121 | document. For more information consult the online list of claimed |
---|
122 | rights. |
---|
123 | |
---|
124 | |
---|
125 | Acknowledgment |
---|
126 | |
---|
127 | Funding for the RFC Editor function is currently provided by the |
---|
128 | Internet Society. |
---|
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 | Doe Informational [Page 3] |
---|
168 | |
---|