RFC 6529 on Host/Host Protocol for the ARPA Network

rfc-editor@rfc-editor.org Fri, 06 April 2012 21:11 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED05911E809F for <ietf-announce@ietfa.amsl.com>; Fri, 6 Apr 2012 14:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.305
X-Spam-Level:
X-Spam-Status: No, score=-102.305 tagged_above=-999 required=5 tests=[AWL=0.295, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gz7YP7w9GWVO for <ietf-announce@ietfa.amsl.com>; Fri, 6 Apr 2012 14:11:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 822F911E8098 for <ietf-announce@ietf.org>; Fri, 6 Apr 2012 14:11:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id ED4C662199; Fri, 6 Apr 2012 14:11:38 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6529 on Host/Host Protocol for the ARPA Network
From: rfc-editor@rfc-editor.org
Message-Id: <20120406211138.ED4C662199@rfc-editor.org>
Date: Fri, 06 Apr 2012 14:11:38 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Apr 2012 21:11:58 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6529

        Title:      Host/Host Protocol for the ARPA 
                    Network 
        Author:     A. McKenzie, S. Crocker
        Status:     Historic
        Stream:     Independent
        Date:       April 2012
        Mailbox:    amckenzie3@yahoo.com, 
                    steve@stevecrocker.com
        Pages:      34
        Characters: 69527
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-mckenzie-arpanet-host-host-protocol-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6529.txt

This document reproduces the Host/Host Protocol developed by the ARPA
Network Working Group during 1969, 1970, and 1971.  It describes a
protocol used to manage communication between processes residing on
independent Hosts.  It addresses issues of multiplexing multiple
streams of communication (including addressing, flow control, connection
establishment/disestablishment, and other signaling) over a single hardware
interface.  It was the official protocol of the ARPA Network from January
1972 until the switch to TCP/IP in January 1983.  It is offered as an RFC 
at this late date to help complete the historical record available through 
the RFC series.  This document is not an Internet Standards Track 
specification; it is published for the historical record.


HISTORIC: This memo defines a Historic Document for the Internet
community.  It does not specify an Internet standard of any kind.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC