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

The information below is for an old version of the document
Document Type Active Internet-Draft (forces WG)
Last updated 2013-07-24 (latest revision 2013-05-08)
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-07-23)
IESG IESG state AD Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Responsible AD Adrian Farrel
Send notices to forces-chairs@tools.ietf.org, draft-ietf-forces-ceha@tools.ietf.org
Network Working Group                                           K. Ogawa
Internet-Draft                                           NTT Corporation
Intended status: Standards Track                              W. M. Wang
Expires: November 09, 2013                 Zhejiang Gongshang University
                                                           E. Haleplidis
                                                    University of Patras
                                                           J. Hadi Salim
                                                       Mojatatu Networks
                                                            May 08, 2013

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

Abstract

   This document discusses Control Element High Availability within a
   ForCES Network Element.

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 November 09, 2013.

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
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

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

   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 . . . . . . . . . . . . . . .   9
   4.  CE HA Hot Standby . . . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Changes to the FEPO model . . . . . . . . . . . . . . . .  10
     4.2.  FEPO processing . . . . . . . . . . . . . . . . . . . . .  12
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Appendix A.  New FEPO version . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  25

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 RFC 2119.

   The following definitions are taken from [RFC3654]and [RFC3746]:

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

   o  ForCES Protocol -- The protocol used at the Fp reference point in
      the ForCES Framework in [RFC3746].

   o  ForCES Protocol Layer (ForCES PL) -- A layer in the ForCES
      architecture that embodies the ForCES protocol and the state
      transfer mechanisms as defined in [RFC5810].

   o  ForCES Protocol Transport Mapping Layer (ForCES TML) -- A layer in
      ForCES protocol architecture that specifically addresses the
      protocol message transportation issues, such as how the protocol
      messages are mapped to different transport media (like SCTP, IP,
      TCP, UDP, ATM, Ethernet, etc), and how to achieve and implement
      reliability, security, etc.

Ogawa, et al.          Expires November 09, 2013                [Page 2]
Internet-Draft     ForCES Intra-NE High Availability            May 2013
Show full document text