Skip to main content

Delay-based Metric Extension for the Babel Routing Protocol
draft-ietf-babel-rtt-extension-05

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Donald Eastlake <d3e3e3@gmail.com>, The IESG <iesg@ietf.org>, andrew-ietf@liquid.tech, babel-chairs@ietf.org, babel@ietf.org, d3e3e3@gmail.com, draft-ietf-babel-rtt-extension@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Delay-based Metric Extension for the Babel Routing Protocol' to Proposed Standard (draft-ietf-babel-rtt-extension-04.txt)

The IESG has approved the following document:
- 'Delay-based Metric Extension for the Babel Routing Protocol'
  (draft-ietf-babel-rtt-extension-04.txt) as Proposed Standard

This document is the product of the Babel routing protocol Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-babel-rtt-extension/


Ballot Text

Technical Summary

   This document defines an extension to the Babel routing protocol that
   measures the round-trip time (RTT) between routers and makes it
   possible to prefer lower latency links over higher latency ones.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

There seemed to be solid consensus on this document 

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

There are reported implementations of this draft.

Personnel

   The Document Shepherd for this document is Donald E. Eastlake 3rd. The
   Responsible Area Director is Andrew Alston.

RFC Editor Note