X.25
X.25 (ITU-T X.25 packet switching) and IP over public data networks
Within this page
X.25 RFCs (19)
RFC 1613: cisco Systems X.25 over TCP (XOT)
Informational- J. Forster
- G. Satz
- G. Glick
- R. Day
- May 1994
- Legacy publication
Abstract
This memo documents a method of sending X.25 packets over IP internets by encapsulating the X.25 Packet Level in TCP packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Abstract
This memo documents a method of sending X.25 packets over IP internets by encapsulating the X.25 Packet Level in TCP packets. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC 1598: PPP in X.25
Proposed Standard- W. Simpson
- March 1994
- IETF publication
- Internet Area
Abstract
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of X.25 for framing PPP encapsulated packets. [STANDARDS-TRACK]
Abstract
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. This document describes the use of X.25 for framing PPP encapsulated packets. [STANDARDS-TRACK]
RFC 1490: Multiprotocol Interconnect over Frame Relay
Draft Standard- T. Bradley
- C. Brown
- A. Malis
- July 1993
- IETF publication
- Routing Area
Abstract
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Additionally, it describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU. [STANDARDS-TRACK]
- Obsoleted by RFC 2427
Abstract
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Additionally, it describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU. [STANDARDS-TRACK]
RFC 1461: SNMP MIB extension for Multiprotocol Interconnect over X.25
Historic- D. Throop
- May 1993
- IETF publication
- Network Management Area
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Multiprotocol Interconnect (including IP) traffic carried over X.25. [STANDARDS-TRACK]
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Multiprotocol Interconnect (including IP) traffic carried over X.25. [STANDARDS-TRACK]
RFC 1433: Directed ARP
Experimental- J. Garrett
- J. Hagan
- J. Wong
- March 1993
- IETF publication
- Routing Area
Abstract
Directed ARP is a dynamic address resolution procedure that enables hosts and routers to resolve advertised potential next-hop IP addresses on foreign IP networks to their associated link level addresses. This memo defines an Experimental Protocol for the Internet community.
Abstract
Directed ARP is a dynamic address resolution procedure that enables hosts and routers to resolve advertised potential next-hop IP addresses on foreign IP networks to their associated link level addresses. This memo defines an Experimental Protocol for the Internet community.
RFC 1381: SNMP MIB Extension for X.25 LAPB
Proposed Standard- D. Throop
- F. Baker
- November 1992
- IETF publication
- Network Management Area
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Link Layer of X.25, LAPB. [STANDARDS-TRACK]
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Link Layer of X.25, LAPB. [STANDARDS-TRACK]
RFC 1382: SNMP MIB Extension for the X.25 Packet Layer
Proposed Standard- D. Throop
- November 1992
- IETF publication
- Network Management Area
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK]
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. [STANDARDS-TRACK]
RFC 1362: Novell IPX over Various WAN Media (IPXWAN)
Informational- M. Allen
- September 1992
- Legacy publication
Abstract
This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. It does not specify an Internet standard.
- Obsoleted by RFC 1634
Abstract
This document describes how Novell IPX operates over various WAN media. Specifically, it describes the common "IPX WAN" protocol Novell uses to exchange necessary router to router information prior to exchanging standard IPX routing information and traffic over WAN datalinks. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1356: Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode
Draft Standard- A. Malis
- D. Robinson
- R. Ullmann
- August 1992
- IETF publication
- Routing Area
Abstract
This document specifies the encapsulation of IP and other network layer protocols over X.25 networks, in accordance and alignment with ISO/IEC and CCITT standards. It is a replacement for RFC 877, "A Standard for the Transmission of IP Datagrams Over Public Data Networks" [1]. [STANDARDS-TRACK]
Abstract
This document specifies the encapsulation of IP and other network layer protocols over X.25 networks, in accordance and alignment with ISO/IEC and CCITT standards. It is a replacement for RFC 877, "A Standard for the Transmission of IP Datagrams Over Public Data Networks" [1]. [STANDARDS-TRACK]
RFC 1315: Management Information Base for Frame Relay DTEs
Proposed Standard- C. Brown
- F. Baker
- C. Carvalho
- April 1992
- IETF publication
- Routing Area
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Frame Relay. [STANDARDS-TRACK]
- Obsoleted by RFC 2115
Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing Frame Relay. [STANDARDS-TRACK]
RFC 1293: Inverse Address Resolution Protocol
Proposed Standard- T. Bradley
- C. Brown
- January 1992
- IETF publication
- Routing Area
Abstract
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
- Obsoleted by RFC 2390
Abstract
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
RFC 1294: Multiprotocol Interconnect over Frame Relay
Proposed Standard- T. Bradley
- C. Brown
- A. Malis
- January 1992
- IETF publication
- Routing Area
Abstract
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK]
- Obsoleted by RFC 1490, RFC 2427
Abstract
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK]
RFC 1236: IP to X.121 address mapping for DDN
Informational- L. Morales
- P. Hasse
- June 1991
- Legacy publication
Abstract
This memo defines a standard way of converting IP addresses to CCITT X.121 addresses and is the recommended standard for use on the Internet, specifically for the Defense Data Network (DDN). This memo provides information for the Internet community. It does not specify an Internet standard.
Abstract
This memo defines a standard way of converting IP addresses to CCITT X.121 addresses and is the recommended standard for use on the Internet, specifically for the Defense Data Network (DDN). This memo provides information for the Internet community. It does not specify an Internet standard.
RFC 1133: Routing between the NSFNET and the DDN
Informational- J.Y. Yu
- H.W. Braun
- November 1989
- Legacy publication
Abstract
This document is a case study of the implementation of routing between the NSFNET and the DDN components (the MILNET and the ARPANET). We hope that it can be used to expand towards interconnection of other Administrative Domains. We would welcome discussion and suggestions about the methods employed for the interconnections. No standards are specified in this memo.
Abstract
This document is a case study of the implementation of routing between the NSFNET and the DDN components (the MILNET and the ARPANET). We hope that it can be used to expand towards interconnection of other Administrative Domains. We would welcome discussion and suggestions about the methods employed for the interconnections. No standards are specified in this memo.
RFC 1090: SMTP on X.25
Unknown- R. Ullmann
- February 1989
- Legacy publication
Abstract
This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT.
Abstract
This memo proposes a standard for SMTP on the virtual circuit facility provided by the X.25 standard of the CCITT.
RFC 1086: ISO-TP0 bridge between TCP and X.25
Unknown- J.P. Onions
- M.T. Rose
- December 1988
- Legacy publication
Abstract
This memo proposes a standard for the Internet community. Hosts on the Internet that choose to implement ISO TP0 transport connectivity between TCP and X.25 based hosts are expected to experiment with this proposal. TCP port 146 is reserved for this proposal.
Abstract
This memo proposes a standard for the Internet community. Hosts on the Internet that choose to implement ISO TP0 transport connectivity between TCP and X.25 based hosts are expected to experiment with this proposal. TCP port 146 is reserved for this proposal.
RFC 1044: STD 45: Internet Protocol on Network System's HYPERchannel: Protocol Specification
Internet Standard- K. Hardwick
- J. Lekashman
- February 1988
- Legacy publication
Abstract
This memo intends to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment. This document is directed toward network planners and implementors who are already familiar with the TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on common networks such as the DDN or the Ethernet. No great familiarity with NSC products is assumed; an appendix is devoted to a review of NSC technologies and protocols.
Abstract
This memo intends to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel equipment. This document is directed toward network planners and implementors who are already familiar with the TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on common networks such as the DDN or the Ethernet. No great familiarity with NSC products is assumed; an appendix is devoted to a review of NSC technologies and protocols.
RFC 1031: MILNET name domain transition
Unknown- W.D. Lazear
- November 1987
- Legacy publication
Abstract
This RFC consolidates information necessary for the implementation of domain style names throughout the DDN/MILNET Internet community. The introduction of domain style names will impact all hosts in the DDN/MILNET Internet. This RFC is designed as an aid to implementors and administrators by providing: 1) an overview of the transition process from host tables to domains, 2) a timetable for the transition, and 3) references to documentation and software relating to the domain system.
Abstract
This RFC consolidates information necessary for the implementation of domain style names throughout the DDN/MILNET Internet community. The introduction of domain style names will impact all hosts in the DDN/MILNET Internet. This RFC is designed as an aid to implementors and administrators by providing: 1) an overview of the transition process from host tables to domains, 2) a timetable for the transition, and 3) references to documentation and software relating to the domain system.
RFC 874: Critique of X.25
Unknown- M.A. Padlipsky
- September 1982
- Legacy publication
Abstract
This RFC is an analysis of X.25 pointing out some problems in the conceptual model, particularly the conflict between the interface aspects and the end-to-end aspects. The memo also touches on security, and implementation issues. Originally published as M82-50 by the MITRE Corporation, Bedford, Massachusetts.
Abstract
This RFC is an analysis of X.25 pointing out some problems in the conceptual model, particularly the conflict between the interface aspects and the end-to-end aspects. The memo also touches on security, and implementation issues. Originally published as M82-50 by the MITRE Corporation, Bedford, Massachusetts.
Subscribe to X.25
Get notified when:
- RFC changes to status, obsoleted by, updates, updated by, or subseries.
- New RFC added to this subject or below
- The subject was merged into another.