ForCES Intra-NE High Availability
draft-ietf-forces-ceha-09

The information below is for an old version of the document
Document Type Active Internet-Draft (forces WG)
Last updated 2013-12-10 (latest revision 2013-11-20)
Replaces draft-ogawa-forces-ceha
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Bhumip Khasnabish
Shepherd write-up Show (last changed 2013-11-26)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Needs a YES. Needs 9 more YES or NO OBJECTION positions to pass.
Responsible AD Adrian Farrel
Send notices to forces-chairs@tools.ietf.org, draft-ietf-forces-ceha@tools.ietf.org
IANA IANA review state IANA OK - Actions Needed
Network Working Group                                           K. Ogawa
Internet-Draft                                           NTT Corporation
Updates: 5810 (if approved)                                   W. M. Wang
Intended status: Standards Track           Zhejiang Gongshang University
Expires: May 24, 2014                                      E. Haleplidis
                                                    University of Patras
                                                           J. Hadi Salim
                                                       Mojatatu Networks
                                                       November 20, 2013

                   ForCES Intra-NE High Availability
                       draft-ietf-forces-ceha-09

Abstract

   This document discusses Control Element High Availability within a
   ForCES Network Element.  Additionally this document updates [RFC5810]
   by providing new normative text for the Cold-Standby High
   availability mechanism.

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."

   This Internet-Draft will expire on May 24, 2014.

Copyright Notice

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

Ogawa, et al.             Expires May 24, 2014                  [Page 1]
Internet-Draft      ForCES Intra-NE High Availability      November 2013

   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.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Document Scope  . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Quantifying Problem Scope . . . . . . . . . . . . . . . .   5
   3.  RFC5810 CE HA Framework . . . . . . . . . . . . . . . . . . .   6
     3.1.  RFC 5810 CE HA Support  . . . . . . . . . . . . . . . . .   6
       3.1.1.  Cold Standby Interaction with ForCES Protocol . . . .   7
       3.1.2.  Responsibilities for HA . . . . . . . . . . . . . . .  10
   4.  CE HA Hot Standby . . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  Changes to the FEPO model . . . . . . . . . . . . . . . .  11
     4.2.  FEPO processing . . . . . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  18
   Appendix A.  New FEPO version . . . . . . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  28

1.  Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   The following definitions are taken from [RFC3654], [RFC3746] and
   [RFC5810].  They are repeated here for convenience as needed, but the
   normative definitions are found in the referenced RFCs:

   o  Logical Functional Block (LFB) -- A template that represents a
      fine-grained, logically separate aspects of FE processing.

   o  Forwarding Element (FE) - A logical entity that implements the
      ForCES Protocol.  FEs use the underlying hardware to provide per-
      packet processing and handling as directed by a CE via the ForCES
      Protocol.

   o  Control Element (CE) - A logical entity that implements the ForCES
      Protocol and uses it to instruct one or more FEs on how to process
      packets.  CEs handle functionality such as the execution of
      control and signaling protocols.

Ogawa, et al.             Expires May 24, 2014                  [Page 2]
Show full document text