Changes

Jump to navigation Jump to search
15 bytes removed ,  12 years ago
no edit summary
Line 1: Line 1: −
FIRS( Federated Internet Registry Service) is a distributed service for storing, locating and transferring information about Internet resources using [[LDAPv3]].<ref>[https://wiki.tools.ietf.org/wg/crisp/draft-ietf-crisp-firs-arch/draft-ietf-crisp-firs-arch-02-from-01.diff.txt wiki.tools.ietf.org]</ref>
+
'''FIRS''' ('''Federated Internet Registry Service''') is a distributed service for storing, locating and transferring information about Internet resources using [[LDAPv3]].<ref>[https://wiki.tools.ietf.org/wg/crisp/draft-ietf-crisp-firs-arch/draft-ietf-crisp-firs-arch-02-from-01.diff.txt wiki.tools.ietf.org]</ref>
   −
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 is intended to provide a distributed [[Whois]]-like information service, using the [[LDAPv3]] specifications 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.
 
FIRS has a collection of specifications which define the following service elements: Namespace Rules, Schema Definitions, Query-Processing Rules.
    
==Background==
 
==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.  
+
The original WHOIS service was intended to be a centralized repository of [[ARPANET]] resources and users. Eventually, many [[Whois]] resources sprung-up 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.
+
There was not 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.
+
Thus, FIRS was bourn out of a need for specifications that cumulatively define a structured 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.
+
The Cross Registry Internet Service Protocol ([[CRISP]]) working group of the [[IETF]] is responsible for development of FIRS.
 
  −
== References ==
  −
{{reflist}}
      
== External links ==
 
== External links ==
Line 22: Line 19:  
* [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-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 Defining and Locating Contact Information in the Federated Internet Registry Service]
 
* [http://tools.ietf.org/html/draft-ietf-crisp-firs-contact-01 Defining and Locating Contact Information in the Federated Internet Registry Service]
 +
== References ==
 +
{{reflist}}
 +
 +
[[Category: Glossary]]
14,326

edits

Navigation menu