Dynamic-Anycast (Dyncast) Requirements
draft-liu-dyncast-reqs-00

Document Type Active Internet-Draft (individual)
Authors Peng Liu  , Peter Willis  , Dirk Trossen 
Last updated 2021-02-15
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)
dyncast                                                           P. Liu
Internet-Draft                                              China Mobile
Intended status: Informational                                 P. Willis
Expires: August 15, 2021                                              BT
                                                              D. Trossen
                                                                  Huawei
                                                       February 15, 2021

                 Dynamic-Anycast (Dyncast) Requirements
                        draft-liu-dyncast-reqs-00 

Abstract

   This draft provides requirements for an architecture addressing the
   problems outlined in the use case and problem statement draft for
   Dyncast [DYNCAST-PS].

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 July 22, 2021.

Copyright Notice

   Copyright (c) 2019 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
 

Liu, et al.             Expires August 15, 2021                 [Page 1]
Internet-Draft            Dyncast Requirements         February 15, 2021

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Definition of Terms  . . . . . . . . . . . . . . . . . . . . .  2
   3.  Desirable System Characteristics and Requirements  . . . . . .  3
     3.1.  Anycast-based Service Addressing Methodology . . . . . . .  3
     3.2.  Instance Affinity  . . . . . . . . . . . . . . . . . . . .  3
     3.3.  Encoding Metrics . . . . . . . . . . . . . . . . . . . . .  4
     3.4.  Signaling Metrics  . . . . . . . . . . . . . . . . . . . .  5
     3.5.  Using Metrics in Routing Decisions . . . . . . . . . . . .  5
     3.6.  Supporting Service Dynamism  . . . . . . . . . . . . . . .  6
   4.  Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . .  6
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
   7.  Informative References . . . . . . . . . . . . . . . . . . . .  7
   Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

1.  Introduction

   Computing service instances instantiated at multiple geographical
   edge sites are used to better realize an edge computing service in
   edge computing use cases, as shown in [DYNCAST-PS]. To optimally
   deliver the service request to the most appropriate service instance
   is the fundamental requirement in such deployments. As shown in
   [DYNCAST-PS], choosing the most appropriate service instance should
   take both, the computing resources available and the network path
   quality, into consideration. "Optimal" here additionally means the
   architecture and overall mechanism should be efficient, support high
   dynamism, while maintaining instance affinity, as shown in [DYNCAST-
   PS].

   This draft provides the requirements to realize the potential dynamic
   anycast architecture by alleviating the problems of existing
   solutions outlined in [DYNCAST-PS].

2.  Definition of Terms

   Service: A service represents a defined endpoint of functionality
       encoded according to the specification for said service. 

   Service instance: One service can have several instances running on
       different nodes. Service instance is a running environment (e.g.,
 

Liu, et al.             Expires August 15, 2021                 [Page 2]
Internet-Draft            Dyncast Requirements         February 15, 2021

       a node) that makes the functionality of a service available.
Show full document text