source: rfc2629xslt/samples/sample.ipr.rfc.200609.ind.txt @ 2082

Last change on this file since 2082 was 1276, checked in by julian.reschke@…, 9 years ago

bump up document dates, latest version of rfc2629.xslt

  • Property svn:eol-style set to native
  • Property svn:executable set to *
File size: 3.0 KB
Line 
1
2
3
4Network Working Group                                             J. Doe
5Request for Comments: 4637                                September 2006
6Category: Informational
7
8
9   Default RFC IPR/@submissionType="independent" as of September 2006
10
11Status 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
17Copyright Notice
18
19   Copyright (C) The Internet Society (2006).
20
21Abstract
22
23   This is a test case document, it is not RFC 4637 (which was never
24   issued by the RFC-Editor).
25
26
271.  Dummy Section
28
29   Dummy Section.
30
31
32Author'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
55Doe                           Informational                     [Page 1]
56
57RFC 4637                 default RFC IPR example          September 2006
58
59
60Full Copyright Statement
61
62   Copyright (C) The Internet Society (2006).
63
64   This document is subject to the rights, licenses and restrictions
65   contained in BCP 78 and at http://www.rfc-editor.org/copyright.html,
66   and except as set forth therein, the authors retain all their rights.
67
68   This document and the information contained herein are provided on an
69   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
70   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
71   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
72   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
73   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
74   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
75
76
77Intellectual Property
78
79   The IETF takes no position regarding the validity or scope of any
80   Intellectual Property Rights or other rights that might be claimed to
81   pertain to the implementation or use of the technology described in
82   this document or the extent to which any license under such rights
83   might or might not be available; nor does it represent that it has
84   made any independent effort to identify any such rights.  Information
85   on the procedures with respect to rights in RFC documents can be
86   found in BCP 78 and BCP 79.
87
88   Copies of IPR disclosures made to the IETF Secretariat and any
89   assurances of licenses to be made available, or the result of an
90   attempt made to obtain a general license or permission for the use of
91   such proprietary rights by implementers or users of this
92   specification can be obtained from the IETF on-line IPR repository at
93   http://www.ietf.org/ipr.
94
95   The IETF invites any interested party to bring to its attention any
96   copyrights, patents or patent applications, or other proprietary
97   rights that may cover technology that may be required to implement
98   this standard.  Please address the information to the IETF at
99   ietf-ipr@ietf.org.
100
101
102Acknowledgment
103
104   Funding for the RFC Editor function is provided by the IETF
105   Administrative Support Activity (IASA).
106
107
108
109
110
111Doe                           Informational                     [Page 2]
112
Note: See TracBrowser for help on using the repository browser.