Document Action: 'Link Metrics for the Mobile Ad Hoc Network (MANET) Routing Protocol OLSRv2 - Rationale' to Informational RFC (draft-ietf-manet-olsrv2-metrics-rationale-04.txt)
The IESG <iesg-secretary@ietf.org> Wed, 01 May 2013 18:53 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B54D21F99BF; Wed, 1 May 2013 11:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level:
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H8bQ6Eb4luk9; Wed, 1 May 2013 11:53:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA6521F991D; Wed, 1 May 2013 11:53:08 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Link Metrics for the Mobile Ad Hoc Network (MANET) Routing Protocol OLSRv2 - Rationale' to Informational RFC (draft-ietf-manet-olsrv2-metrics-rationale-04.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p4
Message-ID: <20130501185303.16952.32868.idtracker@ietfa.amsl.com>
Date: Wed, 01 May 2013 11:53:03 -0700
Cc: manet chair <manet-chairs@tools.ietf.org>, manet mailing list <manet@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 18:53:22 -0000
The IESG has approved the following document: - 'Link Metrics for the Mobile Ad Hoc Network (MANET) Routing Protocol OLSRv2 - Rationale' (draft-ietf-manet-olsrv2-metrics-rationale-04.txt) as Informational RFC This document is the product of the Mobile Ad-hoc Networks Working Group. The IESG contact persons are Adrian Farrel and Stewart Bryant. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2-metrics-rationale/ Technical Summary OLSRv2 includes the ablity to assign metrics to links and to use those metrics to allow routing by other than minimum hop count routes. This document provides a historic record of the rationale for and design considerations behind how link metrics were included in OLSRv2. Working Group Summary o OLSRv2 was first submitted as an individual draft in July 2005 (draft-clausen-manet-olsrv2-00), and accepted as a Working Group document in August 2005. o OLSRv2 is in the process of approval as a Proposed Standard. o A key difference between RFC3626 and OLSRv2 is the introduction of support for link metrics. An individual draft (draft-dearlove-olsrv2- metrics-00) was submitted in 2007, discussing the design options, culminating in 2010 with draft-dearlove-olsrv2-metrics-05 documenting Working Group consensus on this matter. Metrics support was, then, folded into OLSRv2. o This document retains and documents the design rationale, and important decisions for how metrics were integrated into OLSRv2. Thus, this document reflects WG consensus built up during the evolution of OLSRv2, and records the consensus view that lies behind OLSRv2. Document Quality There is a number of independent implementations of OLSRv2, as was indicated in the write-up for that I-D. This document does not propose a protocol, or mandate protocol behavior, but rather presents part of the design rationale for OLSRv2. Personnel Stan Ratliff (sratliff@cisco.com) is the Document Shepherd. Adrian Farrel (adrian@olddog.co.uk) is the Responsible Area Director RFC Editor Note Section 1 paras 4 and 5 Please move the explanation of TC from para 5 to para4