RFC 417 UNKNOWN PROTOCOL · COMPATIBILITY · TENEX

Link usage violation

A warning about TENEX link numbers outside the protocol range

RFC EDITOR

Postel, J. and C. Kline, "Link usage violation", RFC 417, DOI 10.17487/RFC0417, December 1972, <https://www.rfc-editor.org/info/rfc417>.

BIBTEX

@misc{rfc417,
  series = {Request for Comments},
  number = 417,
  howpublished = {RFC 417},
  publisher = {RFC Editor},
  doi = {10.17487/RFC0417},
  url = {https://www.rfc-editor.org/info/rfc417},
  author = {J. Postel and C. Kline},
  title = {{Link usage violation}},
  pagetotal = 1,
  year = 1972,
  month = dec,
}

PUBLISHED: December 1972
AUTHORS: J. Postel, C. Kline
STREAM: Legacy
DOI: 10.17487/RFC0417

RFC text

Original text · RFC Editor View on rfc-editor.org ↗

Network Working Group                                 Jonathan B. Postel
Request for Comments: 417                                 Chuck S. Kline
NIC: 12574                                               6 November 1972


                          LINK USAGE VIOLATION


   We have noticed that TENEX systems use link numbers outside the
   allowed range.  This is a violation of the official HOST-HOST
   protocol.  This causes problems with some sites when attempting to
   establish connections with TENEX systems.  We urge that this problem
   be corrected by bringing all TENEX systems into conformance with the
   established official protocol


          [This RFC was put into machine readable form for entry]
      [into the online RFC archives by Helene Morin, Via Genie 12/99]

ISO Plain Language

On this page

PROBLEMTENEX systems were using link numbers outside the range allowed by the official Host-Host protocol.

MECHANISMThe notice says this usage caused problems when some sites tried to establish connections with TENEX systems.

REQUESTED CORRECTIONThe authors urge TENEX systems to conform to the established protocol.

§1Link Numbers Outside the Allowed Range

The authors say TENEX systems were using link numbers beyond the range permitted by the official Host-Host protocol. The RFC does not list the valid range or the specific numbers that caused the problem.

TENEX systems were using connection numbers that the Host-Host protocol did not allow. This notice does not give the valid range.

§2Connection Problems for Other Sites

The out-of-range link usage caused problems for some sites when they attempted to establish connections with TENEX systems. The RFC describes the effect but gives no further technical details about the failures.

Some sites could not establish connections with TENEX systems because the link numbers did not follow the protocol.

§3Request to Follow the Protocol

Jonathan Postel and Chuck Kline urge that all TENEX systems be brought into conformance with the established Host-Host protocol. This short notice does not specify a correction procedure or report whether systems were changed.

The authors ask the people responsible for TENEX systems to make them follow the Host-Host protocol. The notice does not say what changes were made afterward.