RFC 1608: Representing IP Information in the X.500 Directory
In plain English — editorial summary, not part of the RFC
This document describes the objects necessary to include information about IP networks and IP numbers in the X.500 Directory. It extends the work "Charting networks in the X.500 Directory" [1] where a general framework is presented for representing networks in the Directory by applying it to IP networks. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC1608
- Published
- March 1994
- Authors
- T. Johannsen; G. Mansfield; M. Kosters; S. Sataluri
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- app
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1609Charting Networks in the X.500 DirectoryCurrent
March 1994
- RFC 3470Guidelines for the Use of Extensible Markup Language (XML) within IETF ProtocolsUpdated
January 2003
- RFC 1767MIME Encapsulation of EDI ObjectsCurrent
March 1995
- RFC 2046Multipurpose Internet Mail Extensions (MIME) Part Two: Media TypesUpdated
November 1996
- RFC 2259Simple Nomenclator Query Protocol (SNQP)Current
January 1998
- RFC 2305A Simple Mode of Facsimile Using Internet MailObsoleted
March 1998
- RFC 2506Media Feature Tag Registration ProcedureCurrent
March 1999
- RFC 2534Media Features for Display, Print, and FaxCurrent
March 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?