[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 3632 on VeriSign Registry Registrar Protocol (RRP) Version 2.0.0
A new Request for Comments is now available in online RFC libraries.
Title: VeriSign Registry Registrar Protocol (RRP)
Author(s): S. Hollenbeck, S. Veeramachaneni, S. Yalamanchilli
Date: November 2003
Mailbox: email@example.com, firstname.lastname@example.org,
I-D Tag: draft-hollenbeck-rfc2832bis-03.txt
This document updates version 1.1.0 of the Network Solutions
Inc. (NSI) Registry Registrar Protocol (RRP) specified in RFC 2832.
The changes described in this document combined with the base
specification documented in RFC 2832 specify version 2.0.0 of the
VeriSign Registry Registrar Protocol.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR@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.