draft-ietf-ospf-manet-single-hop-mdr-02.txt   draft-ietf-ospf-manet-single-hop-mdr-03.txt 
Network Working Group R. Ogier Network Working Group R. Ogier
Internet-Draft SRI International Internet-Draft SRI International
Updates: 5614 May 5, 2013 Updates: 5614 June 3, 2013
Intended status: Experimental Intended status: Experimental
Expires: November 6, 2013 Expires: December 5, 2013
Use of OSPF-MDR in Single-Hop Broadcast Networks Use of OSPF-MDR in Single-Hop Broadcast Networks
draft-ietf-ospf-manet-single-hop-mdr-02.txt draft-ietf-ospf-manet-single-hop-mdr-03.txt
Abstract Abstract
RFC 5614 (OSPF-MDR) extends OSPF to support mobile ad hoc networks RFC 5614 (OSPF-MDR) extends OSPF to support mobile ad hoc networks
(MANETs) by specifying its operation on the new OSPF interface of type (MANETs) by specifying its operation on the new OSPF interface of type
MANET. This document describes the use of OSPF-MDR in a single-hop MANET. This document describes the use of OSPF-MDR in a single-hop
broadcast network, which is a special case of a MANET in which each broadcast network, which is a special case of a MANET in which each
router is a (one-hop) neighbor of each other router. Unlike an OSPF router is a (one-hop) neighbor of each other router. Unlike an OSPF
broadcast interface, such an interface can have a different cost broadcast interface, such an interface can have a different cost
associated with each neighbor. The document includes configuration associated with each neighbor. The document includes configuration
skipping to change at page 3, line 5 skipping to change at page 3, line 5
overhead by reporting only changes in neighbor states. overhead by reporting only changes in neighbor states.
This document describes the use of OSPF-MDR in a single-hop broadcast This document describes the use of OSPF-MDR in a single-hop broadcast
network, which is a special case of a MANET in which each router is a network, which is a special case of a MANET in which each router is a
(one-hop) neighbor of each other router. Unlike an OSPF broadcast (one-hop) neighbor of each other router. Unlike an OSPF broadcast
interface, such an interface can have a different cost associated interface, such an interface can have a different cost associated
with each neighbor. An example use case is when the underlying radio with each neighbor. An example use case is when the underlying radio
system performs layer-2 routing, but has a different number of system performs layer-2 routing, but has a different number of
(layer-2) hops to (layer-3) neighbors. (layer-2) hops to (layer-3) neighbors.
The rationale for using this interface type for single-hop broadcast
networks, instead of a broadcast interface type, is to represent the
underlying network in a point-to-multipoint manner, allowing each
router to advertise different costs to different neighbors in its
router-LSA. In this sense, this document shows how the OSPF-MDR
interface type can be configured (and simplified if desired) to
achieve the same goals as the OSPF Hybrid Broadcast and Point-to-
Multipoint interface type [RFC6845].
Section 2 describes the operation of OSPF-MDR in a single-hop Section 2 describes the operation of OSPF-MDR in a single-hop
broadcast network with recommended parameter settings. Section 3 broadcast network with recommended parameter settings. Section 3
describes an alternative procedure which may be used to decide which describes an alternative procedure which may be used to decide which
neighbors on a single-hop broadcast network to advertise in the neighbors on a single-hop broadcast network to advertise in the
router-LSA. Section 4 describes a simplified version of the MDR router-LSA. Section 4 describes a simplified version of the MDR
selection algorithm for single-hop networks. selection algorithm for single-hop networks.
The alternative procedure of Section 3 and the simplified algorithm The alternative procedure of Section 3 and the simplified algorithm
of Section 4 are optional and MUST NOT be used if it is possible for of Section 4 are optional and MUST NOT be used if it is possible for
two routers in the network to be more than one hop from each other. two routers in the network to be more than one hop from each other.
skipping to change at page 6, line 40 skipping to change at page 7, line 8
[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
for IPv6", RFC 5340, July 2008. for IPv6", RFC 5340, July 2008.
[RFC5614] Ogier, R. and P. Spagnolo, "Mobile Ad Hoc Network (MANET) [RFC5614] Ogier, R. and P. Spagnolo, "Mobile Ad Hoc Network (MANET)
Extension of OSPF Using Connected Dominating Set (CDS) Extension of OSPF Using Connected Dominating Set (CDS)
Flooding", RFC 5614, August 2009. Flooding", RFC 5614, August 2009.
8. Informative References 8. Informative References
[RFC6845] Sheth, N., L. Wang, and J. Zhang, "OSPF Hybrid Broadcast [RFC6845] Sheth, N., L. Wang, and J. Zhang, "OSPF Hybrid Broadcast
and Point-to-Multipoint Interface Type", RFC 6845, and Point-to-Multipoint Interface Type", RFC 6845, January
January 2013. 2013.
Author's Address Author's Address
Richard G. Ogier Richard G. Ogier
Email: rich.ogier@earthlink.net Email: ogier@earthlink.net
 End of changes. 6 change blocks. 
5 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/