Federated Internet Registry Service: Difference between revisions
Created page with "FIRS( Federated Internet Registry Service) is a distributed service for storing, locating and transferring information about Internet resources using LDAPv3.<ref>[https://wik..." |
No edit summary |
||
Line 20: | Line 20: | ||
* [http://tools.ietf.org/html/draft-ietf-crisp-firs-arch-01 The Federated Internet Registry Service: Architecture and Implementation Guide] | * [http://tools.ietf.org/html/draft-ietf-crisp-firs-arch-01 The Federated Internet Registry Service: Architecture and Implementation Guide] | ||
* [http://tools.ietf.org/html/draft-ietf-crisp-firs-core-01 The Federated Internet Registry Service: Core Elements] | * [http://tools.ietf.org/html/draft-ietf-crisp-firs-core-01 The Federated Internet Registry Service: Core Elements] | ||
* http://tools.ietf.org/html/draft-ietf-crisp-firs-asn-01 | * [http://tools.ietf.org/html/draft-ietf-crisp-firs-asn-01 Defining and Locating Autonomous System Numbers in the Federated Internet Registry Service] | ||
* [http://tools.ietf.org/html/draft-ietf-crisp-firs-contact-01 | * [http://tools.ietf.org/html/draft-ietf-crisp-firs-contact-01 Defining and Locating Contact Information in the Federated Internet Registry Service] |
Revision as of 14:17, 14 July 2011
FIRS( Federated Internet Registry Service) is a distributed service for storing, locating and transferring information about Internet resources using LDAPv3.[1]
FIRS is intended to provide a distributed WHOIS-like information service, using the LDAPv3 specifications [RFC3377] for the data-formatting and query-transport functions.
FIRS has a collection of specifications which define the following service elements: Namespace Rules, Schema Definitions, Query-Processing Rules.
Background
The original WHOIS service [RFC812] was intended to be a centralized repository of ARPANET resources and users. Over time a lot of WHOIS resouces sprung all over the world, only providing information about particular network resources under the control of a specific organization.
RFC812 and its successors didn't have a strict set of data-typing or formatting requirements. This resulted in different implementations providing different kinds of information. There were also problems with privacy and security.
Thus, FIRS was bourn out of a need for specifications which cumulatively define astructured and distributed information service, including an extensible framework and resource-specific definitions.
The IETF Cross Registry Internet Service Protocol (CRISP) working group of the IETF is responsible for development of FIRS.
References
External links
- The Federated Internet Registry Service: Architecture and Implementation Guide
- The Federated Internet Registry Service: Core Elements
- Defining and Locating Autonomous System Numbers in the Federated Internet Registry Service
- Defining and Locating Contact Information in the Federated Internet Registry Service