As per Relevance of the word copyright, we have this rfc below:
Network Working Group C.
Request for Comments: 2754 USC/
Category: Informational C.
Avici
R.
USC/
January 2000
RPS IANA
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
RPS Security [2] requires certain RPSL [1] objects in the IRR to
hierarchically delegated. The set of objects that are at the root
this hierarchy needs to be created and digitally signed by IANA.
paper presents these seed objects and lists operations required
IANA
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
document are to be interpreted as described in RFC 2119.
1 Initial
A public key of IANA needs to be distributed with the
implementations of Distributed Routing Policy System [3]. An
set of seed objects are needed to be signed with this key.
following transaction (the transaction format is defined in [3])
contains these objects and is signed by this key
Alaettinoglu, et al. Informational [Page 1]
RFC 2754 RPS IANA Issues January 2000
mntner: mnt-
descr: iana's
admin-c: JKR
tech-c: JKR
upd-to: JKRey@ISI.
mnt-nfy: JKRey@ISI.
auth: pgpkey-7F6AA1B
mnt-by: mnt-
referral-by: mnt-
source:
key-cert: pgpkey-7F6AA1B
method:
owner: iana-root (est. Nov 98)
fingerpr: 71 09 2E 37 71 B8 0A 9C 3B 28 98 B4 F1 21 13
certif: # this is the real IANA
+ -----BEGIN PGP PUBLIC KEY BLOCK-----
+ Version: 2.6.2
+
+ mQCNAzZJ52sAAAEEAJ//C01YnlaGuXyrC16V7FphkRvBmcNU22TPOzrKnKjnWjH
+ sJ5UQnGOpyhDc796gqBjY+lTLvPB9sFGJPWgxfNk2JQaxxLTD+tfqSsiURc/
+ XohFAVR/fez8MOecISwvNpFh5VADuFuoNi7ZLuOwVTC4tM5RU0NJa8l/aqG5
+ tCdpYW5hLXJvb3QgKGVzdC4gTm92IDk4KSA8aWFuYUBpYW5hLm9yZz4=
+ =sF4
+ -----END PGP PUBLIC KEY BLOCK-----
mnt-by: mnt-
source:
repository:
repository-cert: PGPKEY-88BAC849
query-address: http://www.iana.
response-auth-type:
submit-address: http://www.iana.
submit-auth-type:
expire: 0000 04:00:00
heartbeat-interval: 0000 01:00:00
admin-c: JKR
tech-c: JKR
mnt-by: mnt-
source:
Alaettinoglu, et al. Informational [Page 2]
RFC 2754 RPS IANA Issues January 2000
as-block: AS0 - AS65535
descr: as number
country:
admin-c: JKR
tech-c: JKR
status:
source:
mnt-by: mnt-
mnt-lower: mnt-
inetnum: 0.0.0.0 - 255.255.255.255
netname:
descr: ip number
country:
admin-c: JKR
tech-c: JKR
status:
source:
mnt-by: mnt-
mnt-lower: mnt-
timestamp: 19991001 01:00:00 +00:00
signature
+ -----BEGIN PGP SIGNATURE-----
+ Version: 2.6.2
+
+ iQCVAwUBOAd3YENJa8l/aqG5AQFVdAP9Ho2TSLGXiDi6v1McsKY4obO32EtP44
+ tpNWiRRz47WIpMBmzUrQajBDNNXzwq9r9mGC75Pg0MMwTDfvA47o6mnIGdT9
+ s9HlDGOqhklIjHOxXFDrBiz3u7eWEf3vmDCXt6UYg9lUtRKefkWtR5wD1Q1
+ 7Ya7PE6X8SU
+ =
+ -----END PGP SIGNATURE-----
The above text has no extra white space characters at the end of
line, and contains no tab characters. All blank line
contain only a single blank line. The page break in the text is
a single blank line
In this case, we assumed that IANA runs its own repository.
this is not a requirement. Instead, it may publish this
with an existing routing registry
2 IANA
Each time IANA makes an assignment, it needs to create inetnum
as-block objects as appropriate and digitally sign them using the
in its key-cert object. For example
Alaettinoglu, et al. Informational [Page 3]
RFC 2754 RPS IANA Issues January 2000
as-block: AS0 - AS500
descr: arin's
country:
status:
source:
delegated:
mnt-by: mnt-
inetnum: 128.0.0.0 - 128.255.255.255
netname: Internet
descr: ip number
country:
status:
source:
delegated:
mnt-by: mnt-
3 Creating Routing
To enable a new routing repository, a repository object, a
object and a key-cert object need to be created and digitally
by IANA. For example
mntner: mnt-
descr: RIPE's
auth:
mnt-by: mnt-
referral-by: mnt-
admin-c: . . .
tech-c: . . .
upd-to: . . .
mnt-nfy: . . .
source:
key-cert: pgpkey-979979
method:
owner: . . .
fingerpr: . . .
certif: # this key is for illustration
+ -----BEGIN PGP PUBLIC KEY BLOCK-----
+ Version: PGP for Personal Privacy 5.0
+
+ . . .
+ -----END PGP PUBLIC KEY BLOCK-----
mnt-by: mnt-
source:
Alaettinoglu, et al. Informational [Page 4]
RFC 2754 RPS IANA Issues January 2000
repository:
query-address: whois://whois.ripe.
response-auth-type: PGPKEY-23F5CE35 # pointer to key-cert
response-auth-type:
remarks: you can request rsa signature on
remarks: PGP required on
submit-address: mailto://auto-dbm@ripe.
submit-address: rps-query://whois.ripe.net:43
submit-auth-type: pgp-key, crypt-pw, mail-
remarks: these are the authentication types
mnt-by: maint-ripe-
expire: 0000 04:00:00
heartbeat-interval: 0000 01:00:00
...
remarks: admin and technical contact,
source:
This very first transaction of a new repository is placed in the
repository, not in the IANA repository
4 Security
Routing policy system security document [2] defines an
authorization model for objects stored in the routing registries
This document specifies the seed objects and the actions need to
taken by IANA to maintain the root of that authorization hierarchy
5 IANA
This whole document is for detailed consideration by IANA
[1] Alaettinoglu, C., Bates, T., Gerich, E., Karrenberg, D., Meyer
D., Terpstra, M. and C. Villamizar, "Routing Policy
Language (RPSL)", RFC 2622, June 1999.
[2] Villamizar, C., Alaettinouglu, C., Meyer, D., Murphy, S. and C
Orange, "Routing Policy System Security", RFC 2725,
1999.
[3] Villamizar, C., Alaettinouglu, C., Govindan, R. and D. Meyer
"Distributed Routing Policy System", Work in Progress
Alaettinoglu, et al. Informational [Page 5]
RFC 2754 RPS IANA Issues January 2000
6 Authors'
Cengiz
USC Information Sciences
EMail: cengiz@isi.
Curtis
Avici
EMail: curtis@avici.
Ramesh
USC Information Sciences
EMail: govindan@isi.
7
The IETF takes no position regarding the validity or scope of
intellectual property or other rights that might be claimed
pertain to the implementation or use of the technology described
this document or the extent to which any license under such
might or might not be available; neither does it represent that
has made any effort to identify any such rights. Information on
IETF's procedures with respect to rights in standards-track
standards-related documentation can be found in BCP-11. Copies
claims of rights made available for publication and any assurances
licenses to be made available, or the result of an attempt made
obtain a general license or permission for the use of
proprietary rights by implementors or users of this specification
be obtained from the IETF Secretariat
The IETF invites any interested party to bring to its attention
copyrights, patents or patent applications, or other
rights which may cover technology that may be required to
this standard. Please address the information to the IETF
Director
Alaettinoglu, et al. Informational [Page 6]
RFC 2754 RPS IANA Issues January 2000
8 Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Alaettinoglu, et al. Informational [Page 7]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
