Service Oriented Internet Protocol
draft-jiang-service-oriented-ip-02

Document Type Active Internet-Draft (individual)
Last updated 2019-10-28
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                       B. Carpenter
Internet-Draft                                         Univ. of Auckland
Intended status: Informational                                  S. Jiang
Expires: May 1, 2020                        Huawei Technologies Co., Ltd
                                                                   G. Li
                                                     Huawei Technologies
                                                        October 29, 2019

                   Service Oriented Internet Protocol
                   draft-jiang-service-oriented-ip-02

Abstract

   This document proposes a new, backwards-compatible, approach to
   packet forwarding, where the service required rather than the IP
   address required acts as the vector for routing packets at the edge
   of the network.  Deeper in the network, the mechanism can interface
   to conventional and future methods of service or application aware
   networking.

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 May 1, 2020.

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

Carpenter, et al.          Expires May 1, 2020                  [Page 1]
Internet-Draft             Service Oriented IP              October 2019

   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.  Proposed Solution . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Coexistence Issues  . . . . . . . . . . . . . . . . . . . . .   7
   4.  Some Usage Examples . . . . . . . . . . . . . . . . . . . . .   8
   5.  Continuity with the Existing Internet . . . . . . . . . . . .   8
   6.  Interface with Service and Application Domains  . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Appendix A.  Possible TLV and CBOR Encodings  . . . . . . . . . .  11
     A.1.  TLV Mapping . . . . . . . . . . . . . . . . . . . . . . .  11
     A.2.  CBOR Mapping  . . . . . . . . . . . . . . . . . . . . . .  12
   Appendix B.  Change log [RFC Editor: Please remove] . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   An important aspect of the Internet today is that it is no longer a
   uniform space with uniform requirements.  For both technical and
   economic reasons, we see an emerging trend of usage scenarios that
   are confined to some form of limited domain, and which inevitably
   lead to applications and protocols that are only suitable within a
   given scope [I-D.carpenter-limited-domains].  In particular, various
   techniques have emerged for packet treatments that are specific to a
   type of application or service.  This trend collides immediately with
   two factors: the original design concept of an Internet with end to
   end IP transparency (such that any locally defined protocol running
   over IP is almost certain to escape the local network), and with the
   increasing presence of middleboxes.  In this emerging context, where
   end to end IP service is no longer a safe assumption, and where there
   is increasing demand for specific services, this document proposes a
   new, backwards-compatible, approach to packet forwarding, where the
   service required rather than the IP address required acts as the
   vector for routing packets at the edge of the network, close to the
   host requiring a particular service or application.  This form of
   service based packet forwarding is referred to as Service Oriented IP
   (SOIP).

   We propose an addition to the existing core function of the network,
Show full document text