Internet-Draft RSerPool Bakeoff Scoring March 2022
Dreibholz & Tuexen Expires 22 September 2022 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-dreibholz-rserpool-score-30
Published:
Intended Status:
Informational
Expires:
Authors:
T. Dreibholz
SimulaMet
M. Tuexen
Münster Univ. of App. Sciences

Reliable Server Pooling (RSerPool) Bakeoff Scoring

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 22 September 2022.

Table of Contents

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:

2.1. Pool Element Communication

These points will be scored for EACH peer implementation that you successfully communicate with.

2.2. Pool User Communication

These points will be scored for EACH peer implementation that you successfully communicate with.

2.3. ENRP Server Communication

These points will be scored for EACH peer implementation that you successfully communicate with.

3. Endpoint Handlespace Redundancy Protocol

The ENRP protocol and useful extensions are described in the follwing documents:

3.1. Peer Management

These points will be scored for EACH peer implementation that you successfully communicate with.

3.2. Update

These points will be scored for EACH peer implementation that you successfully communicate with.

3.3. Synchronization

These points will be scored for EACH peer implementation that you successfully communicate with.

3.4. Takeover

These points will be scored for EACH peer implementation that you successfully communicate with. The setup contains your ENRP server plus a set of peers running another implementation.

4. Bonus Points

You can also earn Bonus Points:

Please note that the whole period of the bakeoff is relevant.

5. Reference Implementation

The RSerPool reference implementation RSPLIB can be found at [14]. It supports the functionalities defined by [2], [3], [4], [5] and [7] as well as the options [9], [11] and [10]. The MIB module is defined in [8]. An introduction to this implementation is provided in [12].

6. Testbed Platform

A large-scale and realistic Internet testbed platform with support for the multi-homing feature of the underlying SCTP protocol is NorNet. A description of NorNet is provided in [13], some further information can be found on the project website [15].

7. Security Considerations

This document does only describe test scenarios and therefore does not introduce any new security issues.

For security considerations of the RSerPool protocols see [1], [2], [3], [4], [5]. [7] and in particular [6].

8. IANA Considerations

This document introduces no additional considerations for IANA.

9. References

9.1. Normative References

[1]
Tuexen, M., Xie, Q., Stewart, R., Shore, M., Ong, L., Loughney, J., and M. Stillman, "Requirements for Reliable Server Pooling", RFC 3237, DOI 10.17487/RFC3237, , <https://www.rfc-editor.org/info/rfc3237>.
[2]
Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An Overview of Reliable Server Pooling Protocols", RFC 5351, DOI 10.17487/RFC5351, , <https://www.rfc-editor.org/info/rfc5351>.
[3]
Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, "Aggregate Server Access Protocol (ASAP)", RFC 5352, DOI 10.17487/RFC5352, , <https://www.rfc-editor.org/info/rfc5352>.
[4]
Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A. Silverton, "Endpoint Handlespace Redundancy Protocol (ENRP)", RFC 5353, DOI 10.17487/RFC5353, , <https://www.rfc-editor.org/info/rfc5353>.
[5]
Stewart, R., Xie, Q., Stillman, M., and M. Tuexen, "Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters", RFC 5354, DOI 10.17487/RFC5354, , <https://www.rfc-editor.org/info/rfc5354>.
[6]
Stillman, M., Ed., Gopal, R., Guttman, E., Sengodan, S., and M. Holdrege, "Threats Introduced by Reliable Server Pooling (RSerPool) and Requirements for Security in Response to Threats", RFC 5355, DOI 10.17487/RFC5355, , <https://www.rfc-editor.org/info/rfc5355>.
[7]
Dreibholz, T. and M. Tuexen, "Reliable Server Pooling Policies", RFC 5356, DOI 10.17487/RFC5356, , <https://www.rfc-editor.org/info/rfc5356>.
[8]
Dreibholz, T. and J. Mulik, "Reliable Server Pooling MIB Module Definition", RFC 5525, DOI 10.17487/RFC5525, , <https://www.rfc-editor.org/info/rfc5525>.
[9]
Dreibholz, T., "Handle Resolution Option for ASAP", Work in Progress, Internet-Draft, draft-dreibholz-rserpool-asap-hropt-29, , <https://www.ietf.org/archive/id/draft-dreibholz-rserpool-asap-hropt-29.txt>.
[10]
Dreibholz, T. and X. Zhou, "Definition of a Delay Measurement Infrastructure and Delay-Sensitive Least-Used Policy for Reliable Server Pooling", Work in Progress, Internet-Draft, draft-dreibholz-rserpool-delay-28, , <https://www.ietf.org/archive/id/draft-dreibholz-rserpool-delay-28.txt>.
[11]
Dreibholz, T. and X. Zhou, "Takeover Suggestion Flag for the ENRP Handle Update Message", Work in Progress, Internet-Draft, draft-dreibholz-rserpool-enrp-takeover-26, , <https://www.ietf.org/archive/id/draft-dreibholz-rserpool-enrp-takeover-26.txt>.

9.2. Informative References

[12]
Dreibholz, T., "Reliable Server Pooling – Evaluation, Optimization and Extension of a Novel IETF Architecture", , <https://duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/Derivate-16326/Dre2006_final.pdf>.
[13]
Dreibholz, T. and E. G. Gran, "Design and Implementation of the NorNet Core Research Testbed for Multi-Homed Systems", Proceedings of the 3nd International Workshop on Protocols and Applications with Multi-Homing Support (PAMS) Pages 1094-1100, ISBN 978-0-7695-4952-1, DOI 10.1109/WAINA.2013.71, , <https://www.simula.no/file/threfereedinproceedingsreference2012-12-207643198512pdf/download>.
[14]
Dreibholz, T., "Thomas Dreibholz's RSerPool Page", , <https://www.uni-due.de/~be0001/rserpool/>.
[15]
Dreibholz, T., "NorNet – A Real-World, Large-Scale Multi-Homing Testbed", , <https://www.nntb.no/>.

Authors' Addresses

Thomas Dreibholz
Simula Metropolitan Centre for Digital Engineering
Pilestredet 52
0167 Oslo
Norway
Michael Tuexen
Münster University of Applied Sciences
Stegerwaldstraße 39
48565 Steinfurt
Germany

mirror server hosted at Truenetwork, Russian Federation.