datatracker.ietf.org
Sign In
Version 4.45, 2013-05-14
Report a bug

Use of the OSPF-MANET Interface in Single-Hop Broadcast Networks
draft-ietf-ospf-manet-single-hop-or-02

Active Internet-Draft (ospf WG)
Document Stream: IETF
Last updated: 2013-05-13
Intended RFC status: (None)
Other versions: plain text, pdf, html

IETF State: WG Document (ospf)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                          A. Retana
Internet-Draft                                                S. Ratliff
Updates: 5820 (if approved)                          Cisco Systems, Inc.
Intended status: Experimental                               May 13, 2013
Expires: November 14, 2013

    Use of the OSPF-MANET Interface in Single-Hop Broadcast Networks
                 draft-ietf-ospf-manet-single-hop-or-02

Abstract

   This document describes the use of the OSPF-MANET interface in
   single-hop broadcast networks.  It includes a mechanism to
   dynamically determine the presence of such a network and specific
   operational considerations due to its nature.

   This document updates [RFC5820].

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 14, 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

Retana & Ratliff       Expires November 14, 2013                [Page 1]
Internet-Draft    MANET Single-Hop Broadcast Networks           May 2013

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Single-Hop Broadcast Networks . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Single-Hop Network Operation  . . . . . . . . . . . . . . . .   3
     3.1.  Use of Router Priority  . . . . . . . . . . . . . . . . .   4
     3.2.  Unsynchronized Adjacencies  . . . . . . . . . . . . . . .   5
   4.  Single-Hop Network Detection  . . . . . . . . . . . . . . . .   5
     4.1.  Transition from multi-hop to single-hop mode  . . . . . .   6
     4.2.  Transition from single-hop to multi-hop mode  . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   8
     A.1.  Changes between the -00 and -01 versions. . . . . . . . .   8
     A.2.  Changes between the -01 and -02 versions. . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The OSPF-MANET interface [RFC5820] uses the point-to-multipoint
   adjacency model over a broadcast media to allow the following:

   o  all router-to-router connections are treated as if they were
      point-to-point links.

   o  Link metric can be set on a per-neighbor basis.

   o  Broadcast and multicast can be accomplished through the Layer 2
      broadcast capabilities of the media.

   It is clear that the characteristics of the MANET interface can also
   be beneficial in other types of network deployments; specifically in
   single-hop broadcast capable networks which may have a different cost
   associated with any pair of nodes.

   This document updates [RFC5820] by describing the use of the MANET
   interface in single-hop broadcast networks.

1.1.  Single-Hop Broadcast Networks

Retana & Ratliff       Expires November 14, 2013                [Page 2]
Internet-Draft    MANET Single-Hop Broadcast Networks           May 2013

   The OSPF extensions for MANET networks assume the ad-hoc formation of