Re: [Crisp] WG: RFC 4698 on IRIS: An Address Registry (areg) Type for 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