--- 1/draft-ietf-manet-olsrv2-dat-metric-07.txt 2015-11-04 07:15:51.377351638 -0800 +++ 2/draft-ietf-manet-olsrv2-dat-metric-08.txt 2015-11-04 07:15:51.413352522 -0800 @@ -1,19 +1,19 @@ MANET H. Rogge Internet-Draft Fraunhofer FKIE Intended status: Experimental E. Baccelli -Expires: May 5, 2016 INRIA - November 2, 2015 +Expires: May 7, 2016 INRIA + November 4, 2015 Packet Sequence Number based directional airtime metric for OLSRv2 - draft-ietf-manet-olsrv2-dat-metric-07 + draft-ietf-manet-olsrv2-dat-metric-08 Abstract This document specifies an directional airtime link metric for usage in OLSRv2. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -21,21 +21,21 @@ 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 May 5, 2016. + This Internet-Draft will expire on May 7, 2016. Copyright Notice Copyright (c) 2015 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 @@ -462,21 +462,21 @@ o an INTERVAL_TIME message TLV in each HELLO message, as defined in [RFC6130] section 4.3.2. o an interface specific packet sequence number as defined in [RFC5444] section 5.1 which is incremented by 1 for each outgoing [RFC5444] packet on the interface. An implementation of OLSRv2 using the metric specified by this document that inserts packet sequence numbers in some, but not all - outgoing [RFC5444] packets will make this metric ignoring all packets + outgoing [RFC5444] packets will make this metric ignore all packets without the sequence number. Putting the INTERVAL_TIME TLV into some, but not all Hello messages will make the timeout based loss detection slower. This will only matter in the absence of packet sequence numbers. 9.3. Link Loss Data Gathering For each incoming [RFC5444] packet, additional processing SHOULD be carried out after the packet messages have been processed as specified in [RFC6130] and [RFC7181] as specified in this section. @@ -769,27 +769,26 @@ fluctuations regarding frame loss. However, the current "quere of counters" algorithm suggested for DAT outperforms the binary queue algorithm and the exponential aging algorithms used for the ETX metric in the OLSR [RFC3626] codebase of Olsr.org. Appendix B. OLSR.org metric history The Funkfeuer [FUNKFEUER] and Freifunk networks [FREIFUNK] are OLSR- based [RFC3626] or B.A.T.M.A.N. [BATMAN] based wireless community networks with hundreds of routers in permanent operation. The Vienna - Funkfeuer network in Austria, for instance, consists of 400 - routerscovering the whole city of Vienna and beyond, spanning roughly - 40km in diameter. It has been in operation since 2003 and supplies - its users with Internet access. A particularity of the Vienna - Funkfeuer network is that it manages to provide Internet access - through a city wide, large scale Wi-Fi MANET, with just a single - Internet uplink. + Funkfeuer network in Austria, for instance, consists of 400 routers + covering the whole city of Vienna and beyond, spanning roughly 40km + in diameter. It has been in operation since 2003 and supplies its + users with Internet access. A particularity of the Vienna Funkfeuer + network is that it manages to provide Internet access through a city + wide, large scale Wi-Fi MANET, with just a single Internet uplink. Operational experience of the OLSR project [OLSR.org] with these networks have revealed that the use of hop-count as routing metric leads to unsatisfactory network performance. Experiments with the ETX metric [MOBICOM03] were therefore undertaken in parallel in the Berlin Freifunk network as well as in the Vienna Funkfeuer network in 2004, and found satisfactory, i.e., sufficiently easy to implement and providing sufficiently good performance. This metric has now been in operational use in these networks for several years.