Reliable Server Pooling (RSerPool) Bakeoff Scoring
draft-dreibholz-rserpool-score-26
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2020-03-13
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group T. Dreibholz
Internet-Draft SimulaMet
Intended status: Informational M. Tuexen
Expires: September 14, 2020 Muenster Univ. of App. Sciences
March 13, 2020
Reliable Server Pooling (RSerPool) Bakeoff Scoring
draft-dreibholz-rserpool-score-26
Abstract
This memo describes some of the scoring to be used in the testing of
Reliable Server Pooling protocols ASAP and ENRP at upcoming bakeoffs.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 14, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Dreibholz & Tuexen Expires September 14, 2020 [Page 1]
Internet-Draft RSerPool Bakeoff Scoring March 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Aggregate Server Access Protocol . . . . . . . . . . . . . . 2
2.1. Pool Element Communication . . . . . . . . . . . . . . . 3
2.2. Pool User Communication . . . . . . . . . . . . . . . . . 3
2.3. ENRP Server Communication . . . . . . . . . . . . . . . . 4
3. Endpoint Handlespace Redundancy Protocol . . . . . . . . . . 4
3.1. Peer Management . . . . . . . . . . . . . . . . . . . . . 5
3.2. Update . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3. Synchronization . . . . . . . . . . . . . . . . . . . . . 6
3.4. Takeover . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Bonus Points . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Reference Implementation . . . . . . . . . . . . . . . . . . 7
6. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
This document will be used as a basis for point scoring at upcoming
RSerPool bakeoffs. Its purpose is similar to that described in
RFC1025. It is hoped that a clear definition of where and how to
score points will further the development of RSerPool.
Note that while attending a bakeoff no one else will score your
points for you. We trust that all implementations will faithfully
record their points that are received honestly. Note also that these
scores are NOT to be used for marketing purposes. They are for the
use of the implementations to know how well they are doing. The only
reporting that will be done is a basic summary to the Reliable Server
Pooling Working Group but please note that NO company or
implementation names will be attached.
2. Aggregate Server Access Protocol
The ASAP protocol and useful extensions are described in the follwing
documents:
o [RFC5352]
o [RFC5354]
o [I-D.dreibholz-rserpool-asap-hropt]
Dreibholz & Tuexen Expires September 14, 2020 [Page 2]
Internet-Draft RSerPool Bakeoff Scoring March 2020
o [I-D.dreibholz-rserpool-delay]
2.1. Pool Element Communication
These points will be scored for EACH peer implementation that you
successfully communicate with.
o 2 Successful ASAP Registration Request of a PE in a pool using
Show full document text