RFC 4991: A Common Schema for Internet Registry Information Service Transfer Protocols
In plain English — editorial summary, not part of the RFC
This document describes an XML Schema for use by Internet Registry Information Service (IRIS) application transfer protocols that share common characteristics. It describes common information about the transfer protocol, such as version, supported extensions, and supported security mechanisms. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4991
- Published
- August 2007
- Authors
- A. Newton
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4992XML Pipelining with Chunks for the Internet Registry Information ServiceUpdated
August 2007
- RFC 4993A Lightweight UDP Transfer Protocol for the Internet Registry Information ServiceCurrent
August 2007
- RFC 3923End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP)Current
October 2004
- RFC 3922Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)Current
October 2004
- RFC 3921Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceObsoleted
October 2004
- RFC 3920Extensible Messaging and Presence Protocol (XMPP): CoreObsoleted
October 2004
- RFC 6283Extensible Markup Language Evidence Record Syntax (XMLERS)Current
July 2011
- RFC 3505Electronic Commerce Modeling Language (ECML): Version 2 RequirementsCurrent
March 2003
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?