RE: [Crisp] WG: RFC 4698 on IRIS: An Address Registry (areg) Typefor the Internet Registry Information Service

"Tim Christensen" <timc@arin.net> Wed, 18 October 2006 14:54 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaCoV-00025D-PY; Wed, 18 Oct 2006 10:54:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaCoT-00024q-SV for crisp@ietf.org; Wed, 18 Oct 2006 10:54:33 -0400
Received: from smtp2.arin.net ([192.149.252.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaCoQ-00052q-Gl for crisp@ietf.org; Wed, 18 Oct 2006 10:54:33 -0400
Received: by smtp2.arin.net (Postfix, from userid 5003) id 3C5DF146ECA; Wed, 18 Oct 2006 10:54:28 -0400 (EDT)
Received: from mercury.arin.net (mercury.arin.net [192.136.136.131]) by smtp2.arin.net (Postfix) with ESMTP id 354BE146DD8; Wed, 18 Oct 2006 10:54:27 -0400 (EDT)
Received: from cadmium (cadmium.arin.net [192.136.136.77]) by mercury.arin.net (Postfix) with ESMTP id 4F4B51FFCB; Wed, 18 Oct 2006 10:54:27 -0400 (EDT)
From: "Tim Christensen" <timc@arin.net>
To: "'April Marine'" <April.Marine@nominum.com>, "'Marcos Sanz/Denic'" <sanz@denic.de>
Subject: RE: [Crisp] WG: RFC 4698 on IRIS: An Address Registry (areg) Typefor the Internet Registry Information Service
Date: Wed, 18 Oct 2006 10:54:27 -0400
Message-ID: <009c01c6f2c5$4efc6240$4d8888c0@arin.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Thread-Index: AcbyxOg1O0hWjjCXQqWRSPhfQ4c49gAAEoBQ
In-Reply-To: <20061018075011.P66522@shell-ng.nominum.com>
X-Spam-Checker-Version: SpamAssassin 2.63-arin1 (2004-01-11) on smtp2.arin.net
X-Spam-Level:
X-Spam-Status: No, hits=-68.3 required=5.0 tests=AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=2.63-arin1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: crisp@ietf.org
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=subscribe>
Errors-To: crisp-bounces@ietf.org

/joins chorus 

> -----Original Message-----
> From: April Marine [mailto:April.Marine@nominum.com] 
> Sent: Wednesday, October 18, 2006 10:51 AM
> To: Marcos Sanz/Denic
> Cc: crisp@ietf.org
> Subject: Re: [Crisp] WG: RFC 4698 on IRIS: An Address 
> Registry (areg) Typefor the Internet Registry Information Service
> 
> Hey! I thought it was just me! I didn't see it on 
> ietf-announce either, although I know it went there. I'll ask 
> about it.
> 
> thx Marcos,
> A.
> 
> On Wed, 18 Oct 2006, Marcos Sanz/Denic wrote:
> 
> > Hello all,
> >
> > I haven't seen this annoucement in this list despite of the 
> wg being 
> > cc'ed, neither can I find the mail in the archives:
> > http://www1.ietf.org/mail-archive/web/crisp/current/index.html
> >
> > Is something going wrong with our list?
> >
> > Best
> > Marcos
> >
> >
> > ----- Weitergeleitet von Marcos Sanz/Denic am 18.10.2006 14:07 -----
> >
> > rfc-editor@rfc-editor.org schrieb am 13.10.2006 03:17:34:
> >
> >>
> >> 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
> >>                     Service
> >>         Author:     E. Gunduz, A. Newton,
> >>                     S. Kerr
> >>         Status:     Standards Track
> >>         Date:       October 2006
> >>         Mailbox:    e.gunduz@computer.org,
> >>                     andy@hxr.us,
> >>                     shane@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@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:
> >>
> >>         To: rfc-info@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@RFC-EDITOR.ORG.  
> >> Unless specifically noted otherwise on the RFC itself, all 
> RFCs are 
> >> for unlimited distribution.
> >>
> >> 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
> >>
> >> ...
> >>
> >>
> >>
> >> _______________________________________________
> >> IETF-Announce mailing list
> >> IETF-Announce@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/ietf-announce
> >
> >
> > _______________________________________________
> > Crisp mailing list
> > Crisp@ietf.org
> > https://www1.ietf.org/mailman/listinfo/crisp
> >
> 
> _______________________________________________
> Crisp mailing list
> Crisp@ietf.org
> https://www1.ietf.org/mailman/listinfo/crisp


_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www1.ietf.org/mailman/listinfo/crisp