Interconnection Intents
draft-contreras-nmrg-interconnection-intents-02

Document Type Active Internet-Draft (individual)
Authors Luis Contreras  , Paolo Lucente 
Last updated 2022-01-20
Stream (None)
Intended RFC status (None)
Formats plain text htmlized pdfized 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)
NMRG                                                       LM. Contreras
Internet-Draft                                                Telefonica
Intended status: Informational                                P. Lucente
Expires: July 24, 2022                                               NTT
                                                        January 20, 2022

                        Interconnection Intents
            draft-contreras-nmrg-interconnection-intents-02

Abstract

   This memo introduces the use case of the usage of intents for
   expressing advance interconnection features, further than traditional
   IP peering.

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 24, 2022.

Copyright Notice

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

Contreras & Lucente       Expires July 24, 2022                 [Page 1]
Internet-Draft           Interconnection Intents            January 2022

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Evolution of Network interconnection  . . . . . . . . . . . .   3
     2.1.  Potential interconnection intent types  . . . . . . . . .   3
     2.2.  Interconnection intent lifecycle  . . . . . . . . . . . .   4
     2.3.  Protocol aspects  . . . . . . . . . . . . . . . . . . . .   4
   3.  Interconnection intent structure  . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The success of Internet-based services has been built on top of the
   global reachability of content accessed by the end-users, which is
   facilitated by the interconnection of individual networks owned by
   distinct service providers constituting independent administrative
   domains.

   Such interconnection services have been initially based simply on
   delivery of IP traffic between the interconnected parties leveraging
   on BGP.  This peer model enables full connectivity.  However, the
   traditional interconnection model shows some limitations when
   additional information to that related to routing is needed.

   New network capabilities based on programmability and virtualization
   are producing service situations where a connectivity-only approach
   is not sufficient.  The increasing availability of computing
   capabilities internal to the networks, or attached to them, enable
   new scenarios where those capabilities can be consumed through the
   advertisement or exposure of these execution environments (i.e., in
   terms of compute, storage and associated networking resources).  Such
   information from an interconnected provider can be obtained from e.g.
   [I-D.llc-teas-dc-aware-topo-model].

   In addition or complementary to that, even services or network
   functions could be advertised in order to make them available for
   interconnection.  For example, as service we could consider the
   advertisement of CDN capabilities as in CDNi approach [RFC7336],
   while as network function we could consider functions like firewall,
   CGNAT, etc, present in the network
   [I-D.ietf-teas-sf-aware-topo-model].

   All these scenarios present clear evolutions of the interconnection
   model which can not be simply expressed through existing mechanisms,

Contreras & Lucente       Expires July 24, 2022                 [Page 2]
Internet-Draft           Interconnection Intents            January 2022

   or at least, cannot be expressed in a simple (and comprehensive) way
   with such existing mechanisms.  Here is where an advanced
   interconnection intent can assist on declaring the goal of the
   interconnection transcending pure IP traffic exchange and including
   more advance capabilities as the ones mentioned before.

2.  Evolution of Network interconnection

   It becomes clear the trend to increasingly rely on multi-domain
   scenarios for the provision of services.  For instance, the access
   today to an on-demand OTT video on Internet implies the interaction
   of more than one single administrative domain.  Thus, end-to-end
   service delivery over multiple providers or domains is becoming the
   norm.

   Complex network services leveraging on virtualization solutions and
   different infrastructure environments pertaining to distinct
   administrative domains (i.e., operated and managed by distinct
   providers) can be easily foreseen.

   It is then necessary to explore mechanisms for interconnecting that
   multiple domain environments in a common, portable way independently
   of the owner of such infrastructure.

2.1.  Potential interconnection intent types

   The interconnection intent should provide enough abstractions to
   express a variety of interconnection options.

   The purpose of the interconnection intent can be multiple:

   o  to enable multi-domain network service programming, by soliciting
      interconnection of service / network functions in different
      domains

   o  to enable multi-domain deployment of virtualized network
      functions, by advertising the availability of compute and storage
      resources in different domains

   o  to facilitate multi-domain network function or service charging,
      by advertising (cumulative) costs in the different domains

   o  to enable traffic interchange, ie.  IP as in traditional peering
      or optical

   o  to put in place the right collection of policies to implement and
      operate the interconnection

Contreras & Lucente       Expires July 24, 2022                 [Page 3]
Internet-Draft           Interconnection Intents            January 2022

   o  to facilitate whatever combination of all of them

2.2.  Interconnection intent lifecycle

   [I-D.irtf-nmrg-ibn-concepts-definitions] defines an intent lifecycle
   composed of two phases, namely fulfillment and assurance.  Figure 1
   captures the intent procedure for the fulfillment phase (assurance
   phase will be detailed in future versions of this draft).

          User Space   :       Translation / IBS       :  Network Ops
                       :            Space              :     Space
                       :                               :
         +----------+  :  +----------+   +-----------+ : +-----------+
 Fulfill |recognize/|---> |translate/|-->|  learn/   |-->| configure/|
         |generate  |     |          |   |  plan/    |   | provision |
         |intent    |<--- |  refine  |   |  render   | : |           |
         +----------+  :  +----------+   +-----------+ : +-----------+
                       :                               :
 .........................................................................

       Provider A      :                   Provider B
       ----------      :                   ----------
                       :
  - Select interconn.  : - Mapping of intent types to  : - Establishment of
    intent type        :   protocols / APIs for        :   protocol sessions
  - Specify targeted   :   coveying targeted resources :   or API requests
    resources (i.e.,   : - Parametrization of that     :   for configure or
    routes, compute    :   protocols / APIs, e.g.      :   provisioning
    quotes, service    :   leveraging on data models   :   targeted resources
    functions, etc.)   :                               :
                       :                               :

         Figure 1: Fulfillment phase of the Interconnection Intent

2.3.  Protocol aspects

   Ultimately the ideas and notions elaborated in this document will
   need to find room in a framework made of one or multiple protocols
   (ie.  BGP, LISP, etc.) and/or API definitions.  While the exact
   definition of such framework is left as future work, in this document
   we intend to perform some seminal work in this sense (ie. identify
   existing protocols that could fit, determine gaps of such protocols,
   etc.).

Contreras & Lucente       Expires July 24, 2022                 [Page 4]
Internet-Draft           Interconnection Intents            January 2022

3.  Interconnection intent structure

   To be done.

4.  Security Considerations

   To be done.

5.  IANA Considerations

   This draft does not include any IANA considerations

6.  References

   [I-D.ietf-teas-sf-aware-topo-model]
              Bryskin, I., Liu, X., Lee, Y., Guichard, J., Contreras, L.
              M., Ceccarelli, D., Tantsura, J., and D. Shytyi, "SF Aware
              TE Topology YANG Model", draft-ietf-teas-sf-aware-topo-
              model-08 (work in progress), July 2021.

   [I-D.irtf-nmrg-ibn-concepts-definitions]
              Clemm, A., Ciavaglia, L., Granville, L. Z., and J.
              Tantsura, "Intent-Based Networking - Concepts and
              Definitions", draft-irtf-nmrg-ibn-concepts-definitions-06
              (work in progress), December 2021.

   [I-D.llc-teas-dc-aware-topo-model]
              Lee, Y., Liu, X., and L. M. Contreras, "DC aware TE
              topology model", draft-llc-teas-dc-aware-topo-model-01
              (work in progress), July 2021.

   [RFC7336]  Peterson, L., Davie, B., and R. van Brandenburg, Ed.,
              "Framework for Content Distribution Network
              Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336,
              August 2014, <https://www.rfc-editor.org/info/rfc7336>.

Acknowledgments

   This work has been partly funded by the European Commission through
   the H2020 project 5GROWTH (Grant Agreement no. 856709).

Authors' Addresses

Contreras & Lucente       Expires July 24, 2022                 [Page 5]
Internet-Draft           Interconnection Intents            January 2022

   Luis M. Contreras
   Telefonica
   Ronda de la Comunicacion, s/n
   Sur-3 building, 3rd floor
   Madrid  28050
   Spain

   Email: luismiguel.contrerasmurillo@telefonica.com
   URI:   http://lmcontreras.com/

   Paolo Lucente
   NTT
   Siriusdreef 70-72
   Hoofddorp, WT  2132
   Netherlands

   Email: paolo@ntt.net

Contreras & Lucente       Expires July 24, 2022                 [Page 6]