summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc1226.txt
diff options
context:
space:
mode:
authorThomas Voss <mail@thomasvoss.com> 2024-11-27 20:54:24 +0100
committerThomas Voss <mail@thomasvoss.com> 2024-11-27 20:54:24 +0100
commit4bfd864f10b68b71482b35c818559068ef8d5797 (patch)
treee3989f47a7994642eb325063d46e8f08ffa681dc /doc/rfc/rfc1226.txt
parentea76e11061bda059ae9f9ad130a9895cc85607db (diff)
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc1226.txt')
-rw-r--r--doc/rfc/rfc1226.txt115
1 files changed, 115 insertions, 0 deletions
diff --git a/doc/rfc/rfc1226.txt b/doc/rfc/rfc1226.txt
new file mode 100644
index 0000000..426f7fe
--- /dev/null
+++ b/doc/rfc/rfc1226.txt
@@ -0,0 +1,115 @@
+
+
+
+
+
+
+Network Working Group B. Kantor
+Request for Comments: 1226 Univ. of Calif San Diego
+ May 1991
+
+
+ Internet Protocol Encapsulation of AX.25 Frames
+
+Status of this Memo
+
+ This memo describes a method for the encapsulation of AX.25 (the
+ Amateur Packet-Radio Link-Layer Protocol) frames within IP packets.
+ This technique is an Experimental Protocol for the Internet
+ community. Discussion and suggestions for improvement are requested.
+ Please refer to the current edition of the "IAB Official Protocol
+ Standards" for the standardization state and status of this protocol.
+ Distribution of this memo is unlimited.
+
+The AX.25 Amateur Packet-Radio Link-Layer Protocol
+
+ The AX.25 Amateur Packet-Radio Link-Layer Protocol is described in
+ the publication by that name [1], incorporated here by reference.
+
+ Each AX.25 packet ("frame") is encapsulated in one IP datagram.
+ Normally no AX.25 frame will exceed 330 octets, so fragmentation at
+ the IP layer should not be necessary. However, experiments with
+ larger AX.25 frame sizes may require the use of standard IP
+ fragmentation and reassembly procedures.
+
+ When an AX.25 frame is encapsulated within an IP packet, HDLC framing
+ elements (flags and zero-stuffing) are omitted, as the IP datagram
+ adequately delimits the beginning and end of each AX.25 frame. The
+ 16-bit CRC-CCITT frame check sequence (normally generated by the HDLC
+ transmission hardware) is included. In all other respects, AX.25
+ frames are encapsulated unaltered.
+
+ Each such IP datagram shall have a protocol number of 93.
+
+Reference
+
+ [1] AX.25 Amateur Packet-Radio Link-Layer Protocol Version 2.0
+ October 1984. Available from the American Radio Relay League,
+ Newington CT USA 06111, and other sources.
+
+Security Considerations
+
+ Security issues are not discussed in this memo.
+
+
+
+
+
+Kantor [Page 1]
+
+RFC 1226 IP Encapsulation of AX.25 Frames May 1991
+
+
+Author's Address
+
+ Brian Kantor
+ University of California at San Diego
+ Network Operations C-024
+ La Jolla, CA 92093-0214
+
+ Phone: (619) 534-6865
+
+ EMail: brian@UCSD.EDU
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Kantor [Page 2]
+ \ No newline at end of file