Synchronisation of Network Parameters
draft-bryant-rtgwg-param-sync-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-10-13
Replaced by draft-ietf-rtgwg-routing-timer-param-sync
Stream (None)
Intended RFC status (None)
Formats 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                                          S. Bryant
Internet-Draft                                       Huawei Technologies
Intended status: Standards Track                                A. Atlas
Expires: April 15, 2017                                        C. Bowers
                                                        Juniper Networks
                                                        October 12, 2016

                 Synchronisation of Network Parameters
                    draft-bryant-rtgwg-param-sync-00

Abstract

   This document describes a mechanism for a link state routing protocol
   to coordinate the value of a network-wide parameter.  The document
   also defines the solution to one specific case: the agreement of a
   common convergence timer value for use in network convergence.

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 April 15, 2017.

Copyright Notice

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

Bryant, et al.           Expires April 15, 2017                 [Page 1]
Internet-Draft               Parameter Sync                 October 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Protocol Details  . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  ISIS  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.2.  OSPF  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Convergence Time  . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Required Properties . . . . . . . . . . . . . . . . . . .   5
     5.2.  Definition of the Convergence Timer . . . . . . . . . . .   5
   6.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  ISIS  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.2.  OSPF  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.3.  Network Wide Parameter  . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  Contributing Authors  . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   There exist use cases where it desirable for a network to use a
   common value for a parameter across all nodes.  In the past, these
   use cases have been addressed by setting the parameter to a constant
   value in the protocol definition itself, or by requiring that the
   same value of the parameter be configured at every node.

   Setting the parameter to a constant value in the protocol definition
   makes it very difficult to change the parameter, since a change would
   require formal modification to the protocol.  In practice, such a
   change is impractical, so the constant value needs to be chosen
   conservatively.  This may impose a fundamental restriction on the
   eventual use of the protocol.

   Manual or "static" configuration of the parameter is fraught for two
   reasons.  First, it is always difficult to ensure that the correct
   value is installed in all of the routers.  Second, if any change is
   introduced into the network that results in a need to change the
   value (for example due to a change in hardware or software version)
   then all of the routers need to be reconfigured to use the new
   parameter value.

Show full document text