IPv6 DOTS Signal Option
draft-francois-dots-ipv6-signal-option-02

Document Type Active Internet-Draft (individual)
Last updated 2017-05-03
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
DOTS                                                         J. Francois
Internet-Draft                                                     Inria
Intended status: Standards Track                              A. Lahmadi
Expires: November 4, 2017                 University of Lorraine - LORIA
                                                               M. Davids
                                                                G. Moura
                                                               SIDN Labs
                                                             May 3, 2017

                        IPv6 DOTS Signal Option
               draft-francois-dots-ipv6-signal-option-02

Abstract

   DOTS client signal using original signal communication channel can
   expect service degradation and even service disruption as any other
   service over Internet but in more severe conditions because the
   signal may have to be transmitted over congested paths due to the
   denial-of-service attack.

   This document specifies a fall-back asynchronous mechanism using an
   intermediate agent to store DOTS signal information during a limited
   period of time.  This mechanism allows a DOTS server to request a
   signal information stored by a DOTS client when no heartbeat is
   received from the DOTS client.  This intermediate agent called DOTS
   Signal Repository have to be connected to the DOTS client and server
   independently.  The repository must be located and/or reached through
   one or multiple network paths, preferably as most as possible
   disjoint from regular signal channel, in order to increase its
   reachability.  The document introduces a set of support protocols to
   build the asynchronous communication between the DOTS cient, server
   and the repository.

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 http://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."

Francois, et al.        Expires November 4, 2017                [Page 1]
Internet-Draft           IPv6 DOTS Signal Option                May 2017

   This Internet-Draft will expire on November 4, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Asynchronous DOTS signaling . . . . . . . . . . . . . . . . .   4
     2.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Architecture  . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Asynchronous process  . . . . . . . . . . . . . . . . . .   5
     2.4.  Protocol requirements . . . . . . . . . . . . . . . . . .   6
   3.  DOTS Signal Repository  . . . . . . . . . . . . . . . . . . .   7
   4.  Protocol  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Between DSR and DOTS server . . . . . . . . . . . . . . .   7
     4.2.  Between DSR and DOTS client . . . . . . . . . . . . . . .   7
       4.2.1.  Opportunistic DOTS signaling  . . . . . . . . . . . .   8
         4.2.1.1.  Hop-by-Hop option encoding  . . . . . . . . . . .   9
         4.2.1.2.  DOTS signal Option attributes . . . . . . . . . .  10
         4.2.1.3.  Example . . . . . . . . . . . . . . . . . . . . .  11
         4.2.1.4.  Option Processing . . . . . . . . . . . . . . . .  12
         4.2.1.5.  Deployment considerations . . . . . . . . . . . .  14
         4.2.1.6.  Impact on existing IP layer implementations . . .  15
       4.2.2.  IPv6 SRH  . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text