Providing Instance Affinity in Dyncast
draft-bormann-dyncast-affinity-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Carsten Bormann
|
|
Last updated |
|
2021-02-22
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
html
xml
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)
|
dyncast C. Bormann
Internet-Draft Universität Bremen TZI
Intended status: Informational 22 February 2021
Expires: 26 August 2021
Providing Instance Affinity in Dyncast
draft-bormann-dyncast-affinity-00
Abstract
Dyncast support in the network provides a client with a fresh optimal
path to a service provider instance, where optimality includes both
path and service provider characteristics. As a service invocation
usually takes more than one packet, dyncast needs to provide instance
affinity for each service invocation. Naive implementations of
instance affinity require per-application, per service-invocation
state in the network.
The present short document defines a way to provide instance affinity
that does not require, but also does not rule out per-application
state.
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 26 August 2021.
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.
Bormann Expires 26 August 2021 [Page 1]
Internet-Draft Dyncast Instance Affinity February 2021
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Approach . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Details . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. Legacy IP Considerations . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
11.1. Normative References . . . . . . . . . . . . . . . . . . 6
11.2. Informative References . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
Dyncast support in the network provides a client with a fresh optimal
path to a service provider instance, where optimality includes both
path and service provider characteristics. As a service invocation
usually takes more than one packet, dyncast needs to provide instance
affinity for each service invocation. Naive implementations of
instance affinity require per-application, per service-invocation
state in the network.
The present short document defines a way to provide instance affinity
that does not require, but also does not rule out per-application
state.
[I-D.liu-dyncast-ps-usecases] lists use cases of dyncast. The
present document does not discuss the specifics of how the network
provides dyncast, such as the way service instance metrics enter path
computations.
Bormann Expires 26 August 2021 [Page 2]
Internet-Draft Dyncast Instance Affinity February 2021
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
This document uses the terminology of [I-D.liu-dyncast-ps-usecases],
in particular _Service_ and _Service Instance_ (the latter often
Show full document text