One document matched: draft-ietf-rps-iana-00.txt
Internet Draft Cengiz Alaettinoglu
Expires February 17, 2000 USC/ISI
draft-ietf-rps-iana-00.txt Curtis Villamizar
Avici Systems
Ramesh Govindan
USC/ISI
August 17, 1999
RPS IANA Issues
Status of this Memo:
This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026.
Copyright (C) The Internet Society (1998). All Rights Reserved.
Internet-Drafts are working documents of the Internet Engineering Task Force
(IETF), its areas, and its working groups. Note that other groups may also
distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and
may be updated, replaced, or obsoleted by other documents at any time. It
is inappropriate to use Internet-Drafts as reference material or to cite
them other than as 'work in progress.'
The list of current Internet-Drafts can be accessed at
<http://www.ietf.org/ietf/1id-abstracts.txt>
The list of Internet-Draft Shadow Directories can be accessed at
<http://www.ietf.org/shadow.html>.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.
Abstract
RPS Security [2] requires certain RPSL [1] objects in the IRR to be
hierarchically delegated. The set of objects that are at the root of this
hierarchy needs to be created and digitally signed by IANA. This paper
Internet Draft RPS IANA Issues August 17, 1999
presents these seed objects and lists operations required from IANA.
1 Initial Seed
A public key of IANA needs to be distributed with the software
implementations of Distributed Routing Policy System [3]. An initial set of
seed objects are needed to be signed with this key. They are:
mntner: mnt-iana
descr: iana's maintainer
admin-c: . . .
tech-c: . . .
upd-to: . . .
mnt-nfy: . . .
auth: pgpkey-12345
mnt-by: mnt-iana
referral-by: mnt-iana
source: IANA
key-cert: pgpkey-12345
method: pgp
owner: . . .
fingerpr: . . .
certif: # this key is for illustration only
+ -----BEGIN PGP PUBLIC KEY BLOCK-----
+ Version: PGP for Personal Privacy 5.0
+
+ mQFCBDZDU98RAwDUmo45DdsS5W8zjTT0wrOMGIxhpdgGEajiwcjUF2EJm/7w7rEt
+ 2WOqXqPupF2lrbb8D3keBnIPW8oyvn0tl471yerBeuBsR50U+D039/yFbpcG0O4F
+ IhYB5TBOrPuUUl8AoP+bUmGP6DudkE+wDgNlcY5UnEBnAwDIB9umMEKK0kDcFy/Q
+ 34gLNplxARbNjyIFLDOg/W2qfBb9/RfQLNGfgPWqYz47tIN1rYhErDWDJjjhWkNd
+ Fb7sARhqCotnkJrJ/0EsnSugU+HZZrp/49XMyvdITyq3Q3QC/RDh2dIWD0VyXvz8
+ uDo6jvN9cx9rmejOsle/TXWYeLlNZrv5zQ8zLr/ZHWzOQAV45GdSgRREHKfHM9lj
+ iOqMagiTdk0df+/g78v8tQaefScj5JNbXqDive5HStdeogFMR7QkQ2VuZ2l6IEFs
+ YWV0dGlub2dsdSA8Y2VuZ2l6QGlzaS5lZHU+iQBLBBARAgALBQI2Q1PfBAsDAQIA
+ CgkQjZRGkY5cjCfDMgCgx8SYpbmMwCC3QoFaJdhBeHPtjCoAn3MZ75AODmWlTjgI
+ akrLUaw3v5CGuQDNBDZDU+UQAwDUtvp8wrXXKqvhGMGBDLYYPWlgGhBAr2eoyS2r
+ n+JZPbDJpOKVygVfdkrWjqQpParzRRUHerhgGNnaiGZBB+XtDa7OTy8mKWGLyY3f
+ svtySSmVSDIjOCTIoMwhR+c3oBcAAgIC/2FVAllFaZWeuEpyjT5p4rOzgzpLSNTf
+ LV9Mav5hyuZJZYHlpibqt1uF5YiYGaE/Zaf0P5pHvF89mOUZ0y8Cj9rKc2AkoRWm
+ 8XhDVL68MXjBUcMimNHkweOnn16iSNttm4kAPwMFGDZDU+WNlEaRjlyMJxECThwA
+ oOpfVLhHM1tqnq09SFptSoiEfxGQAKDF0b1pN8iuZslgttr7AcfAnImCYA==
+ =X+wc
+ -----END PGP PUBLIC KEY BLOCK-----
mnt-by: mnt-iana
source: IANA
Alaettinoglu et. al. Expires February 17, 2000 [Page 2]
Internet Draft RPS IANA Issues August 17, 1999
as-block: AS0 - AS65535
descr: as number space
country: us
admin-c: . . .
tech-c: . . .
status: UNALLOCATED
source: IANA
mnt-by: mnt-iana
mnt-lower: mnt-iana
inetnum: 0.0.0.0 - 255.255.255.255
netname: Internet
descr: ip number space
country: us
admin-c: . . .
tech-c: . . .
status: UNALLOCATED
source: IANA
mnt-by: mnt-iana
mnt-lower: mnt-iana
Here, we assume that IANA runs its own repository. However this is not a
requirement. Instead, it may publish its objects with one of the existing
routing registries.
This set of seed objects needs to be signed with the hard coded IANA key.
Later, IANA objects can be signed with the key in the IANA key-cert object.
2 IANA Assignments
Each time IANA makes an assignment, it needs to create inetnum and as-block
objects as appropriate and digitally sign them using the key in its key-cert
object. For example:
as-block: AS0 - AS500
descr: arin's space
country: us
status: ALLOCATED
source: iana
delegated: arin
mnt-by: mnt-iana
inetnum: 128.0.0.0 - 128.255.255.255
netname: Internet portion
descr: ip number space
country: us
Alaettinoglu et. al. Expires February 17, 2000 [Page 3]
Internet Draft RPS IANA Issues August 17, 1999
status: ALLOCATED
source: iana
delegated: arin
mnt-by: mnt-iana
3 Creating Routing Repositories
To enable a new routing repository, a repository object, a maintainer object
and a key-cert object (if the maintainer object uses it) needs to be created
and digitally signed by IANA. For example:
mntner: mnt-ripe
descr: RIPE's maintainer
auth: <ripe's choice>
mnt-by: mnt-ripe
referral-by: mnt-iana
admin-c: . . .
tech-c: . . .
upd-to: . . .
mnt-nfy: . . .
source: RIPE
key-cert: pgpkey-979979
method: pgp
owner: . . .
fingerpr: . . .
certif: # this key is for illustration only
+ -----BEGIN PGP PUBLIC KEY BLOCK-----
+ Version: PGP for Personal Privacy 5.0
+
+ . . .
+ -----END PGP PUBLIC KEY BLOCK-----
mnt-by: mnt-ripe
source: RIPE
repository: RIPE
query-address: whois.ripe.net 43
response-auth-type: rsa-pubkey some-incredibly-long-public-key
response-auth-type: none
remarks: you can request rsa signature on queries
remarks: PGP required on submissions
submit-address: mailto://auto-dbm@ripe.net
submit-address: rps-query://whois.ripe.net:43
submit-auth-type: pgp-key crypt-pw mail-from
remarks: these are the authentication types supported
mnt-by: maint-ripe
expire: 0000 04:00:00
Alaettinoglu et. al. Expires February 17, 2000 [Page 4]
Internet Draft RPS IANA Issues August 17, 1999
heartbeat-rate: 0000 01:00:00
...
remarks: admin and technical contact, etc
source: RIPE
This very first transaction of a new repository is placed in the new
repository, not in the IANA repository.
4 Security Consideration
This document describes IANA procedures and initial RPSL seed objects. It
does not define protocols or standards that need to be secured.
References
[1] C. Alaettinoglu, T. Bates, E. Gerich, D. Karrenberg, D. Meyer, M.
Terpstra, and C. Villamizar: Routing Policy Specification Language
(RPSL), RFC 2280.
[2] C. Villamizar, C. Alaettinouglu, D. Meyer, S. Murphy, and C. Orange.
Routing policy system security. Internet Draft draft-ietf-rps-auth-03,
Network Information Center, April 1999.
[3] C. Villamizar, C. Alaettinouglu, R. Govindan, D. Meyer. Distributed
Routing Policy System. Internet Draft draft-ietf-rps-dist-01, Network
Information Center, February 1999.
5 Authors' Addresses
Cengiz Alaettinoglu
USC Information Sciences Institute
email: cengiz@isi.edu
Curtis Villamizar
Avici Systems
email: curtis@avici.com
Ramesh Govindan
USC Information Sciences Institute
email: govindan@isi.edu
Alaettinoglu et. al. Expires February 17, 2000 [Page 5]
| PAFTECH AB 2003-2026 | 2026-04-23 09:57:25 |