Handle Resolution Option for ASAP
draft-dreibholz-rserpool-asap-hropt-29
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Thomas Dreibholz
|
|
Last updated |
|
2021-09-06
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
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: Experimental September 06, 2021
Expires: March 10, 2022
Handle Resolution Option for ASAP
draft-dreibholz-rserpool-asap-hropt-29
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 March 10, 2022.
Copyright Notice
Copyright (c) 2021 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 Expires March 10, 2022 [Page 1]
Internet-Draft Handle Resolution Option September 2021
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Conventions . . . . . . . . . . . . . . . . . . . . . . . 3
2. Handle Resolution Option . . . . . . . . . . . . . . . . . . 3
2.1. Definition . . . . . . . . . . . . . . . . . . . . . . . 3
3. Reference Implementation . . . . . . . . . . . . . . . . . . 3
4. Testbed Platform . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
8.1. Normative References . . . . . . . . . . . . . . . . . . 4
8.2. Informative References . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
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 [Dre2006], [IJAIT2009], [IJHIT2008], 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 [LCN2005] 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.
Dreibholz Expires March 10, 2022 [Page 2]
Internet-Draft Handle Resolution Option September 2021
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 [RFC5354].
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 [RFC2119].
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
[RSerPool-Website]. It supports the functionalities defined by
[RFC5351], [RFC5352], [RFC5353], [RFC5354] and [RFC5356] as well as
the options [I-D.dreibholz-rserpool-delay],
[I-D.dreibholz-rserpool-enrp-takeover] and of course the option
Dreibholz Expires March 10, 2022 [Page 3]
Internet-Draft Handle Resolution Option September 2021
defined by this document. An introduction to this implementation is
provided in [Dre2006].
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 [PAMS2013-NorNet],
some further information can be found on the project website
[NorNet-Website].
5. Security Considerations
Security considerations for RSerPool systems are described by
[RFC5355].
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
[I-D.dreibholz-rserpool-delay]
Dreibholz, T. and X. Zhou, "Definition of a Delay
Measurement Infrastructure and Delay-Sensitive Least-Used
Policy for Reliable Server Pooling", draft-dreibholz-
rserpool-delay-27 (work in progress), March 2021.
[I-D.dreibholz-rserpool-enrp-takeover]
Dreibholz, T. and X. Zhou, "Takeover Suggestion Flag for
the ENRP Handle Update Message", draft-dreibholz-rserpool-
enrp-takeover-25 (work in progress), March 2021.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
Dreibholz Expires March 10, 2022 [Page 4]
Internet-Draft Handle Resolution Option September 2021
[RFC5351] Lei, P., Ong, L., Tuexen, M., and T. Dreibholz, "An
Overview of Reliable Server Pooling Protocols", RFC 5351,
DOI 10.17487/RFC5351, September 2008,
<https://www.rfc-editor.org/info/rfc5351>.
[RFC5352] Stewart, R., Xie, Q., Stillman, M., and M. Tuexen,
"Aggregate Server Access Protocol (ASAP)", RFC 5352,
DOI 10.17487/RFC5352, September 2008,
<https://www.rfc-editor.org/info/rfc5352>.
[RFC5353] Xie, Q., Stewart, R., Stillman, M., Tuexen, M., and A.
Silverton, "Endpoint Handlespace Redundancy Protocol
(ENRP)", RFC 5353, DOI 10.17487/RFC5353, September 2008,
<https://www.rfc-editor.org/info/rfc5353>.
[RFC5354] 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, September 2008,
<https://www.rfc-editor.org/info/rfc5354>.
[RFC5355] 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,
September 2008, <https://www.rfc-editor.org/info/rfc5355>.
[RFC5356] Dreibholz, T. and M. Tuexen, "Reliable Server Pooling
Policies", RFC 5356, DOI 10.17487/RFC5356, September 2008,
<https://www.rfc-editor.org/info/rfc5356>.
8.2. Informative References
[Dre2006] Dreibholz, T., "Reliable Server Pooling - Evaluation,
Optimization and Extension of a Novel IETF Architecture",
March 2007, <https://duepublico.uni-duisburg-
essen.de/servlets/DerivateServlet/Derivate-16326/
Dre2006_final.pdf>.
[IJAIT2009]
Dreibholz, T. and E. 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, June 2009,
<https://www.wiwi.uni-due.de/fileadmin/fileupload/I-
TDR/ReliableServer/Publications/IJAIT2009.pdf>.
Dreibholz Expires March 10, 2022 [Page 5]
Internet-Draft Handle Resolution Option September 2021
[IJHIT2008]
Dreibholz, T. and E. 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, April 2008, <https://www.wiwi.uni-
due.de/fileadmin/fileupload/I-
TDR/ReliableServer/Publications/IJHIT2008.pdf>.
[LCN2005] Dreibholz, T. and E. 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, November 2005,
<https://www.wiwi.uni-due.de/fileadmin/fileupload/I-
TDR/ReliableServer/Publications/LCN2005.pdf>.
[NorNet-Website]
Dreibholz, T., "NorNet - A Real-World, Large-Scale Multi-
Homing Testbed", Online: https://www.nntb.no/, 2019,
<https://www.nntb.no/>.
[PAMS2013-NorNet]
Dreibholz, T. and E. 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, March 2013,
<https://www.simula.no/file/
threfereedinproceedingsreference2012-12-207643198512pdf/
download>.
[RSerPool-Website]
Dreibholz, T., "Thomas Dreibholz's RSerPool Page",
Online: https://www.uni-due.de/~be0001/rserpool/, 2019,
<https://www.uni-due.de/~be0001/rserpool/>.
Author's Address
Dreibholz Expires March 10, 2022 [Page 6]
Internet-Draft Handle Resolution Option September 2021
Thomas Dreibholz
Simula Metropolitan Centre for Digital Engineering
Pilestredet 52
0167 Oslo, Oslo
Norway
Phone: +47-6782-8200
Fax: +47-6782-8201
Email: dreibh@simula.no
URI: https://www.simula.no/people/dreibh
Dreibholz Expires March 10, 2022 [Page 7]