[ppml] RFC 4698 on IRIS: An Address Registry (areg) Type for the Internet Registry Information Service (fwd)
Ed.Lewis at neustar.biz
Fri Oct 13 17:32:06 EDT 2006
To clarify...CRISP is the name of a IETF WG, not the name of a
protocol. IRIS is the main product of the CRISP WG.
At 13:49 -0700 10/13/06, william(at)elan.net wrote:
>Yesterday at the meeting (I listed to part of it remotely) you discussed
>CRISP protocol. For those interested in its technical specification as
>it related to IPs & ASNs below is info on just published RFC for it.
>---------- Forwarded message ----------
>Date: Thu, 12 Oct 2006 18:17:34 -0700
>From: rfc-editor at rfc-editor.org
>To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
>Cc: crisp at ietf.org, rfc-editor at rfc-editor.org
>Subject: RFC 4698 on IRIS: An Address Registry (areg) Type for the Internet
> Registry Information Service
>A new Request for Comments is now available in online RFC libraries.
> RFC 4698
> Title: IRIS: An Address Registry (areg)
> Type for the Internet Registry Information
> Author: E. Gunduz, A. Newton,
> S. Kerr
> Status: Standards Track
> Date: October 2006
> Mailbox: e.gunduz at computer.org,
> andy at hxr.us,
> shane at time-travellers.org
> Pages: 48
> Characters: 89932
> Updates/Obsoletes/SeeAlso: None
> I-D Tag: draft-ietf-crisp-iris-areg-15.txt
> URL: http://www.rfc-editor.org/rfc/rfc4698.txt
>This document describes an IRIS registry schema for IP address and
>Autonomous System Number information. The schema extends the
>necessary query and result operations of IRIS to provide the
>functional information service needs for syntaxes and results used by
>Internet Protocol address registries. [STANDARDS TRACK]
>This document is a product of the Cross Registry Information Service
>Protocol Working Group of the IETF.
>This is now a Proposed Standard Protocol.
>STANDARDS TRACK: 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
>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
>IETF-Announce mailing list
>IETF-Announce at ietf.org
>PPML mailing list
>PPML at arin.net
Edward Lewis +1-571-434-5468
Secrets of Success #107: Why arrive at 7am for the good parking space?
Come in at 11am while the early birds drive out to lunch.
More information about the ARIN-PPML