RPS ICANN Issues
draft-ietf-rps-icann-00
Document | Type |
Expired Internet-Draft
(rps WG)
Expired & archived
|
|
---|---|---|---|
Authors | Curtis Villamizar , Dr. Ramesh Govindan | ||
Last updated | 1999-07-01 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 ICANN. This paper presents these seed objects and lists operations required from ICANN.
Authors
Curtis Villamizar
Dr. Ramesh Govindan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)