IPoE Client Health Checking
draft-patterson-intarea-ipoe-health-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-06-05
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
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)
intarea                                                     R. Patterson
Internet-Draft                                                    Sky UK
Intended status: Standards Track                          M. Abrahamsson
Expires: December 7, 2018                                      T-Systems
                                                           June 05, 2018

                      IPoE Client Health Checking
                 draft-patterson-intarea-ipoe-health-00

Abstract

   PPPoE clients have the functionality to detect path unavailability by
   using PPP Keepalives.  IPoE does not have this functionality, and
   it's not specified when an IPoE client should consider its WAN
   connectivity down, unless there is a physical layer link down event.

   This document describes a way for IPoE clients to achieve
   connectivity validation, similar to that of PPPoE, by using existing
   ARP and Neighbor Discovery functions.

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 December 7, 2018.

Copyright Notice

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

Patterson & Abrahamsson Expires December 7, 2018                [Page 1]
Internet-Draft                 IPoE-Health                     June 2018

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Alternative Mitigations . . . . . . . . . . . . . . . . . . .   3
   3.  IPoE Health Checks  . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Parameters  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  DHCPv6  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  DHCPv4  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.4.  Alternative Target  . . . . . . . . . . . . . . . . . . .   4
     3.5.  Passive Checks  . . . . . . . . . . . . . . . . . . . . .   5
   4.  Action Behaviours . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Behaviour 0: Renew (Default)  . . . . . . . . . . . . . .   5
     4.2.  Behaviour 1: Rebind . . . . . . . . . . . . . . . . . . .   6
     4.3.  Behaviour 2: Expire Lease . . . . . . . . . . . . . . . .   6
     4.4.  Behaviour 3: Release  . . . . . . . . . . . . . . . . . .   6
     4.5.  LAN Considerations  . . . . . . . . . . . . . . . . . . .   6
   5.  DHCP Option . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  DHCPv6  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.2.  DHCPv4  . . . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  Multihomed Clients  . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  DHCPv6  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.2.  DHCPv4  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   PPP [RFC1661] makes use of regular LCP echos and replies to
   continually test the data link layer, if the peer fails to respond to
   a predetermined number of LCP echos, the PPP session is terminated
   and will return to the Link Dead phase, ready for reestablishing.
   IPoE currently lacks this functionality.

   Physical link state change on an IPoE client can trigger the renewing
   of a DHCP lease, however any indirect upstream network changes are
Show full document text