RFC 2550: Y10K and Beyond
In plain English — editorial summary, not part of the RFC
This specification provides a solution to the "Y10K" problem which has also been called the "YAK" problem (hex) and the "YXK" problem (Roman numerals). This memo provides information for the Internet community.
Document record
- Document ID
- RFC2550
- Published
- April 1999
- Authors
- S. Glassman; M. Manasse; J. Mogul
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2551The Roman Standards Process -- Revision IIICurrent
April 1999
- RFC 2549IP over Avian Carriers with Quality of ServiceCurrent
April 1999
- RFC 1149Standard for the transmission of IP datagrams on avian carriersUpdated
April 1990
- RFC 2100The Naming of HostsCurrent
April 1997
- RFC 2506Media Feature Tag Registration ProcedureCurrent
March 1999
- RFC 2653CIP Transport ProtocolsCurrent
August 1999
- RFC 2049Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and ExamplesCurrent
November 1996
- RFC 3116Methodology for ATM BenchmarkingCurrent
June 2001
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?