draft-ietf-ospf-manet-single-hop-or-03.txt   draft-ietf-ospf-manet-single-hop-or-04.txt 
Network Working Group A. Retana Network Working Group A. Retana
Internet-Draft S. Ratliff Internet-Draft S. Ratliff
Updates: 5820 (if approved) Cisco Systems, Inc. Updates: 5820 (if approved) Cisco Systems, Inc.
Intended status: Experimental November 6, 2013 Intended status: Experimental December 18, 2013
Expires: May 10, 2014 Expires: June 21, 2014
Use of the OSPF-MANET Interface in Single-Hop Broadcast Networks Use of the OSPF-MANET Interface in Single-Hop Broadcast Networks
draft-ietf-ospf-manet-single-hop-or-03 draft-ietf-ospf-manet-single-hop-or-04
Abstract Abstract
This document describes the use of the OSPF-MANET interface in This document describes the use of the OSPF-MANET interface in
single-hop broadcast networks. It includes a mechanism to single-hop broadcast networks. It includes a mechanism to
dynamically determine the presence of such a network and specific dynamically determine the presence of such a network and specific
operational considerations due to its nature. operational considerations due to its nature.
This document updates RFC5820. This document updates RFC5820.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
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."
This Internet-Draft will expire on May 10, 2014. This Internet-Draft will expire on June 21, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Single-Hop Broadcast Networks . . . . . . . . . . . . . . . 3 1.1. Single-Hop Broadcast Networks . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Single-Hop Network Operation . . . . . . . . . . . . . . . . . 4 3. Single-Hop Network Operation . . . . . . . . . . . . . . . . 3
3.1. Use of Router Priority . . . . . . . . . . . . . . . . . . 4 3.1. Use of Router Priority . . . . . . . . . . . . . . . . . 4
3.2. Unsynchronized Adjacencies . . . . . . . . . . . . . . . . 5 3.2. Unsynchronized Adjacencies . . . . . . . . . . . . . . . 5
4. Single-Hop Network Detection . . . . . . . . . . . . . . . . . 6 4. Single-Hop Network Detection . . . . . . . . . . . . . . . . 5
4.1. Transition from multi-hop to single-hop mode . . . . . . . 6 4.1. Transition from multi-hop to single-hop mode . . . . . . 6
4.2. Transition from single-hop to multi-hop mode . . . . . . . 7 4.2. Transition from single-hop to multi-hop mode . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . . 8 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8
A.1. Changes between the -00 and -01 versions. . . . . . . . . . 8 A.1. Changes between the -00 and -01 versions. . . . . . . . . 8
A.2. Changes between the -01 and -02 versions. . . . . . . . . . 8 A.2. Changes between the -01 and -02 versions. . . . . . . . . 8
A.3. Changes between the -02 and -03 versions. . . . . . . . . . 8 A.3. Changes between the -02 and -03 versions. . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 A.4. Changes betwen the -03 and -04 versions . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The OSPF-MANET interface [RFC5820] uses the point-to-multipoint The OSPF-MANET interface [RFC5820] uses the point-to-multipoint
adjacency model over a broadcast media to allow the following: adjacency model over a broadcast media to allow the following:
o all router-to-router connections are treated as if they were o all router-to-router connections are treated as if they were
point-to-point links. point-to-point links.
o Link metric can be set on a per-neighbor basis. o Link metric can be set on a per-neighbor basis.
o Broadcast and multicast can be accomplished through the Layer 2 o Broadcast and multicast can be accomplished through the Layer 2
broadcast capabilities of the media. broadcast capabilities of the media.
It is clear that the characteristics of the MANET interface can also It is clear that the characteristics of the MANET interface can also
be beneficial in other types of network deployments; specifically in be beneficial in other types of network deployments; specifically in
single-hop broadcast capable networks which may have a different cost single-hop broadcast capable networks which may have a different cost
associated with any pair of nodes. associated with any pair of nodes.
This document updates [RFC5820] by describing the use of the MANET This document updates [RFC5820] by describing the use of the MANET
interface in single-hop broadcast networks. interface in single-hop broadcast networks, which 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 1.1. Single-Hop Broadcast Networks
The OSPF extensions for MANET networks assume the ad-hoc formation of The OSPF extensions for MANET networks assume the ad-hoc formation of
a network over bandwidth-constrained wireless links, where packets a network over bandwidth-constrained wireless links, where packets
may traverse several intermediate nodes before reaching their may traverse several intermediate nodes before reaching their
destination (multi-hop paths on the interface). By contrast, a destination (multi-hop paths on the interface). By contrast, a
single-hop broadcast network (as considered in this document) is one single-hop broadcast network (as considered in this document) is one
that is structured in such a way that all the nodes in it are that is structured in such a way that all the nodes in it are
directly connected to each other. An Ethernet interface is a good directly connected to each other. An Ethernet interface is a good
skipping to change at page 7, line 43 skipping to change at page 7, line 36
This document includes no request to IANA. This document includes no request to IANA.
6. Security Considerations 6. Security Considerations
No new security concerns beyond the ones expressed in [RFC5820] are No new security concerns beyond the ones expressed in [RFC5820] are
introduced in this document. introduced in this document.
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Anton Smirnov, Jeffrey Zhang, Alia The authors would like to thank Anton Smirnov, Jeffrey Zhang, Alia
Atlas, Juan Antonio Cordero and Richard Ogier for their comments. Atlas, Juan Antonio Cordero, Richard Ogier and Christer Holmberg for
their comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC5820] Roy, A. and M. Chandra, "Extensions to OSPF to Support [RFC5820] Roy, A. and M. Chandra, "Extensions to OSPF to Support
Mobile Ad Hoc Networking", RFC 5820, March 2010. Mobile Ad Hoc Networking", RFC 5820, March 2010.
skipping to change at page 8, line 21 skipping to change at page 8, line 10
[RFC5820] Roy, A. and M. Chandra, "Extensions to OSPF to Support [RFC5820] Roy, A. and M. Chandra, "Extensions to OSPF to Support
Mobile Ad Hoc Networking", RFC 5820, March 2010. Mobile Ad Hoc Networking", RFC 5820, March 2010.
8.2. Informative References 8.2. Informative References
[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.
Appendix A. Change Log Appendix A. Change Log
To be removed prior to publication.
A.1. Changes between the -00 and -01 versions. A.1. Changes between the -00 and -01 versions.
o Updated contact information. o Updated contact information.
A.2. Changes between the -01 and -02 versions. A.2. Changes between the -01 and -02 versions.
o Indicated the nature of the RFC5820 update. o Indicated the nature of the RFC5820 update.
o Clarified the Single-Hop Condition and the SingleHop flag. o Clarified the Single-Hop Condition and the SingleHop flag.
o Reshuffled the references. o Reshuffled the references.
A.3. Changes between the -02 and -03 versions. A.3. Changes between the -02 and -03 versions.
No changes..just a refresh. No changes..just a refresh.
A.4. Changes betwen the -03 and -04 versions
o Clarified how this document updates RFC5820.
o Updated ACKs.
Authors' Addresses Authors' Addresses
Alvaro Retana Alvaro Retana
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd. 7025 Kit Creek Rd.
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
Email: aretana@cisco.com Email: aretana@cisco.com
Stan Ratliff Stan Ratliff
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd. 7025 Kit Creek Rd.
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
Email: sratliff@cisco.com Email: sratliff@cisco.com
 End of changes. 11 change blocks. 
27 lines changed or deleted 42 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/