Internet-Draft Handle Resolution Option March 2022
Dreibholz Expires 22 September 2022 [Page]
Workgroup:
Network Working Group
Internet-Draft:
draft-dreibholz-rserpool-asap-hropt-30
Published:
Intended Status:
Experimental
Expires:
Author:
T. Dreibholz
SimulaMet

Handle Resolution Option for ASAP

Abstract

This document describes the Handle Resolution option for the ASAP protocol.

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

Reliable Server Pooling defines protocols for providing highly available services. The Aggregate Server Access Protocol (ASAP) provides session management and server selection for applications. Upon request for a server selection -- denoted as handle resolution -- an ENRP server returns a list of selected PE identities. The number of PE identities to be returned is not specified by RSerPool. Furthermore the ASAP protocol does not contain a way for letting the requesting instance specify it.

As shown in [10], [11], [12], selecting too many entries does not make sense for the application, but on the other hand also result in significant processing and network overhead. Furthermore, it has been shown in [13] that the number of requested elements is usually 1, but there are application cases where more PE identities have to be returned. That is, there should be a possibility to specify the number of requested PE items upon a handle resolution.

1.1. Scope

The Handle Resolution option defined in this draft simply defines an option to let the PU-side specify the desired number of PE identities from the ENRP server.

1.2. Terminology

The terms are commonly identified in related work and can be found in the Aggregate Server Access Protocol and Endpoint Handlespace Redundancy Protocol Common Parameters document RFC 5354 [5].

1.3. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [1].

2. Handle Resolution Option

2.1. Definition

The Handle Resolution MAY be used once in an ASAP Handle Resolution message sent from a PU to an ENRP server. It is defined as follows.

   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Type = 0x803f         |            Length=8            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                             Items                             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Items: 32 bits (unsigned integer)

Contains the number of PE identities to be selected by the ENRP server. Setting it to 0xffffffff denotes to obtain as many PE identities as possible. A setting of 0 denotes to use the ENRP server's default value; this default MUST be used if there is no Handle Resolution option given. The ENRP server SHOULD try to fulfil the request for the given number of items.

Note, that the high-order bits of the type field are set to 10, which means "skip this parameter and continue processing" if this parameter type is not supported by the ENRP server. This allows for interoperability with old implementations.

3. Reference Implementation

The RSerPool reference implementation RSPLIB can be found at [15]. It supports the functionalities defined by [2], [3], [4], [5] and [7] as well as the options [8], [9] and of course the option defined by this document. An introduction to this implementation is provided in [10].

4. 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 [14], some further information can be found on the project website [16].

5. Security Considerations

Security considerations for RSerPool systems are described by [6].

6. IANA Considerations

This document does not require additional IANA actions beyond those already identified in the ENRP and ASAP protocol specifications.

7. Acknowledgments

The author would like to thank Nihad Cosic, Dirk Hoffstadt, Michael Kohnen, Jobin Pulinthanath and Xing Zhou for their support.

8. References

8.1. Normative References

[1]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[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 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>.
[9]
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>.

8.2. Informative References

[10]
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>.
[11]
Dreibholz, T. and E. P. Rathgeb, "Overview and Evaluation of the Server Redundancy and Session Failover Mechanisms in the Reliable Server Pooling Framework", International Journal on Advances in Internet Technology (IJAIT) Number 1, Volume 2, Pages 1-14, ISSN 1942-2652, , <https://www.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/IJAIT2009.pdf>.
[12]
Dreibholz, T. and E. P. Rathgeb, "An Evaluation of the Pool Maintenance Overhead in Reliable Server Pooling Systems", SERSC International Journal on Hybrid Information Technology (IJHIT) Number 2, Volume 1, Pages 17-32, ISSN 1738-9968, , <https://www.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/IJHIT2008.pdf>.
[13]
Dreibholz, T. and E. P. Rathgeb, "On the Performance of Reliable Server Pooling Systems", Proceedings of the IEEE Conference on Local Computer Networks (LCN) 30th Anniversary Pages 200-208, ISBN 0-7695-2421-4, DOI 10.1109/LCN.2005.98, , <https://www.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/LCN2005.pdf>.
[14]
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>.
[15]
Dreibholz, T., "Thomas Dreibholz's RSerPool Page", , <https://www.uni-due.de/~be0001/rserpool/>.
[16]
Dreibholz, T., "NorNet – A Real-World, Large-Scale Multi-Homing Testbed", , <https://www.nntb.no/>.

Author's Address

Thomas Dreibholz
Simula Metropolitan Centre for Digital Engineering
Pilestredet 52
0167 Oslo
Norway

mirror server hosted at Truenetwork, Russian Federation.