Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP) (RFC3983)

IP.com Disclosure Number: IPCOM000033948D
Original Publication Date: 2005-Jan-01
Included in the Prior Art Database: 2005-Jan-06
Document File: 13 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Newton: AUTHOR [+2]

Abstract

This document specifies how to use the Blocks Extensible Exchange Protocol (BEEP) as the application transport substrate for the Internet Registry Information Service (IRIS).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group                                          A. Newton

Request for Comments: 3983                                VeriSign, Inc.

Category: Standards Track                                        M. Sanz

                                                                DENIC eG

                                                            January 2005

      Using the Internet Registry Information Service (IRIS) over

             the Blocks Extensible Exchange Protocol (BEEP)

Status of This Memo

   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.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document specifies how to use the Blocks Extensible Exchange

   Protocol (BEEP) as the application transport substrate for the

   Internet Registry Information Service (IRIS).

Table of Contents

   1.  Introduction and Motivations . . . . . . . . . . . . . . . . .  2

   2.  Document Terminology . . . . . . . . . . . . . . . . . . . . .  3

   3.  BEEP Profile Identification  . . . . . . . . . . . . . . . . .  3

   4.  IRIS Message Packages  . . . . . . . . . . . . . . . . . . . .  4

   5.  IRIS Message Patterns  . . . . . . . . . . . . . . . . . . . .  4

       5.1.  Registry Dependent Patterns. . . . . . . . . . . . . . .  4

       5.2.  Default Pattern. . . . . . . . . . . . . . . . . . . . .  4

   6.  Server Authentication Methods  . . . . . . . . . . . . . . . .  5

       6.1.  Registry Dependent Methods. . . . . . . .  . . . . . . .  5

       6.2.  Basic Server Authentication Method. . . .  . . . . . . .  5

   7.  IRIS Transport Mapping Definitions . . . . . . . . . . . . . .  6

       7.1.  URI Scheme . . . . . . . . . . . . . . . . . . . . . . .  6

       7.2.  Application Protocol Label . . . . . . . . . . . . . . .  6

       7.3.  Allowable Character Sets . . . . . . . . . . . . . . . .  6

       7.4.  BEEP Mapping . . . . . . . . . . . . . . . . . . . . . .  6

   8.  Registrations  . . . . . . . . . . . . . . . . . . . . . . . .  6

       8.1.  BEEP Profile Registration. . . . . . . . . . . . . . . .  6

       8.2.  URI Scheme Registration. . . . . . . . . . . . . . . . .  7

Newton & Sanz               Standards Track                     [Page 1]

RFC 3983                    ...