datatracker.ietf.org
Sign in
Version 5.6.3, 2014-09-19
Report a bug

Use of the OSPF-MANET Interface in Single-Hop Broadcast Networks
RFC 7137

Document type: RFC - Experimental (February 2014; No errata)
Updates RFC 5820
Document stream: IETF
Last updated: 2014-02-27
Other versions: plain text, pdf, html

IETF State: Submitted to IESG for Publication
Consensus: Unknown
Document shepherd: Yi Yang
Shepherd Write-Up: Last changed 2013-11-04

IESG State: RFC 7137 (Experimental)
IANA Review State: IANA OK - No Actions Needed
IANA Action State: No IC
Responsible AD: Stewart Bryant
Send notices to: ospf-chairs@tools.ietf.org, draft-ietf-ospf-manet-single-hop-or@tools.ietf.org, yiya@cisco.com

Internet Engineering Task Force (IETF)                         A. Retana
Request for Comments: 7137                                    S. Ratliff
Updates: 5820                                        Cisco Systems, Inc.
Category: Experimental                                     February 2014
ISSN: 2070-1721

    Use of the OSPF-MANET Interface in Single-Hop Broadcast Networks

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

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This document is a product of the Internet Engineering
   Task Force (IETF).  It represents the consensus of the IETF
   community.  It has received public review and has been approved for
   publication by the Internet Engineering Steering Group (IESG).  Not
   all documents approved by the IESG are a candidate for any level of
   Internet Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7137.

Retana & Ratliff              Experimental                      [Page 1]
RFC 7137           MANET Single-Hop Broadcast Networks     February 2014

Copyright Notice

   Copyright (c) 2014 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
   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 . . . . . . . . . . . . . .   3
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Single-Hop Network Operation  . . . . . . . . . . . . . . . .   4
     3.1.  Use of Router Priority  . . . . . . . . . . . . . . . . .   4
     3.2.  Unsynchronized Adjacencies  . . . . . . . . . . . . . . .   5
   4.  Single-Hop Network Detection  . . . . . . . . . . . . . . . .   6
     4.1.  Transition from Multi-Hop to Single-Hop Mode  . . . . . .   6
     4.2.  Transition from Single-Hop to Multi-Hop Mode  . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   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  The 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.

Retana & Ratliff              Experimental                      [Page 2]
RFC 7137           MANET Single-Hop Broadcast Networks     February 2014

   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 that 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; this consists of its
   simplified operation by not requiring the use of overlapping relays
   as well as introducing a new heuristic for smart peering using the
   Router Priority.

1.1.  Single-Hop Broadcast Networks

   The OSPF extensions for MANETs assume the ad hoc formation of a
   network over bandwidth-constrained wireless links, where packets may
   traverse several intermediate nodes before reaching their destination

[include full document text]