[Rserpool] RFC 5353 on Endpoint Handlespace Redundancy Protocol (ENRP)
rfc-editor@rfc-editor.org Tue, 30 September 2008 17:26 UTC
Return-Path: <rserpool-bounces@ietf.org>
X-Original-To: rserpool-archive@megatron.ietf.org
Delivered-To: ietfarch-rserpool-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 95D3528C1B1;
Tue, 30 Sep 2008 10:26:48 -0700 (PDT)
X-Original-To: rserpool@core3.amsl.com
Delivered-To: rserpool@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 8A96F3A6B32;
Tue, 30 Sep 2008 10:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.085
X-Spam-Level:
X-Spam-Status: No, score=-17.085 tagged_above=-999 required=5
tests=[AWL=-0.285, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799,
USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id ZIFCf72SNeyo; Tue, 30 Sep 2008 10:26:44 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
by core3.amsl.com (Postfix) with ESMTP id B76B13A6951;
Tue, 30 Sep 2008 10:26:42 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
id E81A315ECF6; Tue, 30 Sep 2008 10:27:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080930172702.E81A315ECF6@bosco.isi.edu>
Date: Tue, 30 Sep 2008 10:27:02 -0700 (PDT)
Cc: rserpool@ietf.org, rfc-editor@rfc-editor.org
Subject: [Rserpool] RFC 5353 on Endpoint Handlespace Redundancy Protocol (ENRP)
X-BeenThere: rserpool@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Reliable Server Pooling <rserpool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rserpool>,
<mailto:rserpool-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rserpool>
List-Post: <mailto:rserpool@ietf.org>
List-Help: <mailto:rserpool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rserpool>,
<mailto:rserpool-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rserpool-bounces@ietf.org
Errors-To: rserpool-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
RFC 5353
Title: Endpoint Handlespace Redundancy Protocol (ENRP)
Author: Q. Xie, R. Stewart,
M. Stillman, M. Tuexen,
A. Silverton
Status: Experimental
Date: September 2008
Mailbox: Qiaobing.Xie@gmail.org,
randall@lakerest.net,
maureen.stillman@nokia.com,
tuexen@fh-muenster.de,
ajs.ietf@gmail.com
Pages: 39
Characters: 83657
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rserpool-enrp-21.txt
URL: http://www.rfc-editor.org/rfc/rfc5353.txt
The Endpoint Handlespace Redundancy Protocol (ENRP) is designed to
work in conjunction with the Aggregate Server Access Protocol (ASAP)
to accomplish the functionality of the Reliable Server Pooling
(RSerPool) requirements and architecture. Within the operational
scope of RSerPool, ENRP defines the procedures and message formats of
a distributed, fault-tolerant registry service for storing,
bookkeeping, retrieving, and distributing pool operation and
membership information. This memo defines an Experimental Protocol
for the Internet community.
This document is a product of the Reliable Server Pooling Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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
USC/Information Sciences Institute
_______________________________________________
rserpool mailing list
rserpool@ietf.org
https://www.ietf.org/mailman/listinfo/rserpool