INTERNET-DRAFT M. Yevstifeyev
Intended Status: Informational January 6, 2011
Obsoletes: 938 (if approved)
Expires: July 10, 2011
Moving Internet Reliable Transaction Protocol (IRTP) to Historic
Abstract
This document moves the Internet Reliable Transaction Protocol (IRTP)
to Historic status. It obsoletes RFC 938.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Yesvtifeyev Expires July 10, 2011 [Page 1]
INTERNET DRAFT IRTP to Historic January 6, 2011
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction and Overview . . . . . . . . . . . . . . . . . . . 2
2. RFC Editor Considerations . . . . . . . . . . . . . . . . . . . 2
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 2
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 2
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.1. Normative References . . . . . . . . . . . . . . . . . . . 3
5.2. Informative References . . . . . . . . . . . . . . . . . . 3
Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction and Overview
Internet Reliable Transaction Protocol (IRTP) is defined in RFC 938
[RFC938]. This protocol has a number of issues, that make it
impossible to be used in the current Internet. Among other, the IRTP
specification defines the protocol operations less than clear; the
port range of 256 available ports is obviously very little; the
protocol provides neither security features nor congestion control,
etc. Moreover, for almost 25 years nobody has seen either
implementations of this protocol or services claimed to use it.
Taking everything into account, development of a new IRTP
specification to match the needs of current Internet would not be
justified. This document moves IRTP to Historic status. [RFC2026]
2. RFC Editor Considerations
RFC Editor is asked to mark RFC 938 [RFC938] as Historic (see
[RFC2026]) and obsoleted by this document.
3. IANA Considerations
The document has no actions for IANA.
4. Security Considerations
The document does not introduce any new security issues to IRTP.
Yesvtifeyev Expires July 10, 2011 [Page 2]
INTERNET DRAFT IRTP to Historic January 6, 2011
5. References
5.1. Normative References
[RFC938] Miller, T., "Internet Reliable Transaction Protocol
functional and interface specification", RFC 938,
February 1985.
5.2. Informative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996.
Author's Addresses
Mykyta Yevstifeyev
Kotovsk, Ukraine
EMail: evnikita2@gmail.com
Yesvtifeyev Expires July 10, 2011 [Page 3]