RFC 4992: XML Pipelining with Chunks for the Internet Registry Information Service
In plain English — editorial summary, not part of the RFC
This document describes a simple TCP transfer protocol for the Internet Registry Information Service (IRIS). Data is transferred between clients and servers using chunks to achieve pipelining. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4992
- Published
- August 2007
- Authors
- A. Newton
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 29
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4173Bootstrapping Clients using the Internet Small Computer System Interface (iSCSI) ProtocolUpdated
September 2005
- RFC 4172iFCP - A Protocol for Internet Fibre Channel Storage NetworkingUpdated
September 2005
- RFC 4991A Common Schema for Internet Registry Information Service Transfer ProtocolsCurrent
August 2007
- RFC 4993A Lightweight UDP Transfer Protocol for the Internet Registry Information ServiceCurrent
August 2007
- RFC 3081Mapping the BEEP Core onto TCPCurrent
March 2001
- RFC 4953Defending TCP Against Spoofing AttacksCurrent
July 2007
- RFC 4850Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node ArchitectureObsoleted
April 2007
- RFC 5273Certificate Management over CMS (CMC): Transport ProtocolsObsoleted
June 2008
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?