idnits 2.17.1 draft-mealling-rfc3001bis-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3061 5 Title: A URN Namespace of Object Identifiers 6 Author(s): M. Mealling 7 Status: Informational 8 Date: February 2001 9 Mailbox: michaelm@netsol.com 10 Pages: 6 11 Characters: 8387 12 Obsoletes: 3001 14 I-D Tag: draft-mealling-rfc3001bis-01.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3061.txt 18 This document describes a Uniform Resource Name (URN) namespace that 19 contains Object Identifiers (OIDs). It obsoletes RFC 3001. 21 This memo provides information for the Internet community. It does 22 not specify an Internet standard of any kind. Distribution of this 23 memo is unlimited. 25 This announcement is sent to the IETF list and the RFC-DIST list. 26 Requests to be added to or deleted from the IETF distribution list 27 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 28 added to or deleted from the RFC-DIST distribution list should 29 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 31 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 32 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 33 help: ways_to_get_rfcs. For example: 35 To: rfc-info@RFC-EDITOR.ORG 36 Subject: getting rfcs 38 help: ways_to_get_rfcs 40 Requests for special distribution should be addressed to either the 41 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 42 specifically noted otherwise on the RFC itself, all RFCs are for 43 unlimited distribution.echo 44 Submissions for Requests for Comments should be sent to 45 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 46 Authors, for further information.