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