draft-ietf-ospf-manet-single-hop-mdr-01.txt   draft-ietf-ospf-manet-single-hop-mdr-02.txt 
Network Working Group R. Ogier Network Working Group R. Ogier
Updates: 5614 December 7, 2012 Internet-Draft SRI International
Internet-Draft Updates: 5614 May 5, 2013
Intended status: Experimental Intended status: Experimental
Expires: June 10, 2013 Expires: November 6, 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-01.txt draft-ietf-ospf-manet-single-hop-mdr-02.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 1, line 41 skipping to change at page 1, line 41
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 46 skipping to change at page 4, line 46
To provide rationale for the above procedure, let i and j be two To provide rationale for the above procedure, let i and j be two
non-MDR routers. Since the SPF calculation (Section 16.1 of non-MDR routers. Since the SPF calculation (Section 16.1 of
[RFC2328]) allows router i to use router j as a next hop only if [RFC2328]) allows router i to use router j as a next hop only if
router j advertises a link back to router i, routers i and j must router j advertises a link back to router i, routers i and j must
both advertise a link to each other in their router-LSAs before both advertise a link to each other in their router-LSAs before
either can use the other as a next hop. Therefore, the above either can use the other as a next hop. Therefore, the above
procedure for non-MDR routers (Step 2) implies there must exist a procedure for non-MDR routers (Step 2) implies there must exist a
path of fully adjacent links between i and j (via the MDR) in path of fully adjacent links between i and j (via the MDR) in
both directions before this can happen. The above procedure for both directions before this can happen. The above procedure for
non-MDR routers is similar to one described in Section 3.6 of non-MDR routers is similar to one described in Section 4.6 of
[HYBRID] for non-DR routers. [RFC6845] for non-DR routers.
4. MDR Selection Algorithm 4. MDR Selection Algorithm
The MDR selection algorithm of [RFC5614] simplifies as follows in The MDR selection algorithm of [RFC5614] simplifies as follows in
single-hop networks. The resulting algorithm is similar to the DR single-hop networks. The resulting algorithm is similar to the DR
election algorithm of OSPF, but is slightly different (e.g., two election algorithm of OSPF, but is slightly different (e.g., two
Backup MDRs are selected). The following simplified algorithm is Backup MDRs are selected). The following simplified algorithm is
interoperable with the full MDR selection algorithm. interoperable with the full MDR selection algorithm.
Note that lexicographic order is used when comparing tuples of the Note that lexicographic order is used when comparing tuples of the
skipping to change at page 6, line 39 skipping to change at page 6, line 39
[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
[HYBRID] Sheth, N., L. Wang, and J. Zhang, "OSPF Hybrid Broadcast [RFC6845] Sheth, N., L. Wang, and J. Zhang, "OSPF Hybrid Broadcast
and P2MP Interface Type", draft-ietf-ospf-hybrid-bcast-and- and Point-to-Multipoint Interface Type", RFC 6845,
p2mp-06.txt, October 2012, work in progress. January 2013.
Author's Address Author's Address
Richard G. Ogier Richard G. Ogier
Email: rich.ogier@earthlink.net Email: rich.ogier@earthlink.net
 End of changes. 6 change blocks. 
10 lines changed or deleted 10 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/