18 Jun 2004 01:04
RFC 3779 on X.509 Extensions for IP Addresses and AS Identifiers
<rfc-editor <at> rfc-editor.org>
2004-06-17 23:04:33 GMT
2004-06-17 23:04:33 GMT
A new Request for Comments is now available in online RFC libraries. RFC 3779 Title: X.509 Extensions for IP Addresses and AS Identifiers Author(s): C. Lynn, S. Kent, K. Seo Status: Standards Track Date: June 2004 Mailbox: CLynn <at> BBN.Com, Kent <at> BBN.Com, KSeo <at> BBN.Com Pages: 27 Characters: 60732 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pkix-x509-ipaddr-as-extn-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3779.txt This document defines two X.509 v3 certificate extensions. The first binds a list of IP address blocks, or prefixes, to the subject of a certificate. The second binds a list of autonomous system identifiers to the subject of a certificate. These extensions may be used to convey the authorization of the subject to use the IP addresses and autonomous system identifiers contained in the extensions. This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST <at> IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info <at> RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR <at> RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.