Re: [babel] Babel-RTT information model and example parameters

"STARK, BARBARA H" <bs7652@att.com> Mon, 29 July 2019 21:12 UTC

Return-Path: <bs7652@att.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C53D120045 for <babel@ietfa.amsl.com>; Mon, 29 Jul 2019 14:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IHULHpTu8bzb for <babel@ietfa.amsl.com>; Mon, 29 Jul 2019 14:12:22 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ABA3120043 for <babel@ietf.org>; Mon, 29 Jul 2019 14:12:22 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.27/8.16.0.27) with SMTP id x6TL6UBJ028952; Mon, 29 Jul 2019 17:12:17 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049462.ppops.net-00191d01. with ESMTP id 2u27g4hhhx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 29 Jul 2019 17:12:16 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x6TLBjbc007035; Mon, 29 Jul 2019 17:11:45 -0400
Received: from zlp30486.vci.att.com (zlp30486.vci.att.com [135.47.91.177]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x6TLBdNJ006946 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 29 Jul 2019 17:11:39 -0400
Received: from zlp30486.vci.att.com (zlp30486.vci.att.com [127.0.0.1]) by zlp30486.vci.att.com (Service) with ESMTP id 533A24009E77; Mon, 29 Jul 2019 21:11:39 +0000 (GMT)
Received: from GAALPA1MSGHUBAE.ITServices.sbc.com (unknown [130.8.218.154]) by zlp30486.vci.att.com (Service) with ESMTPS id 4062A4005C24; Mon, 29 Jul 2019 21:11:39 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.84]) by GAALPA1MSGHUBAE.ITServices.sbc.com ([130.8.218.154]) with mapi id 14.03.0439.000; Mon, 29 Jul 2019 17:11:38 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: 'Juliusz Chroboczek' <jch@irif.fr>
CC: 'Baptiste Jonglez' <baptiste.jonglez@imag.fr>, 'Mahesh Jethanandani' <mjethanandani@gmail.com>, "'babel@ietf.org'" <babel@ietf.org>
Thread-Topic: [babel] Babel-RTT information model and example parameters
Thread-Index: AQHVQvuPaANjEbh89UaQNFKB91p2lKbdZ2D4gABGqICABG4pkA==
Date: Mon, 29 Jul 2019 21:11:38 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114E248BD3@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <20190725151332.ywxjpxpxoritx4ql@imag.fr> <59AF71F0-DFD6-40D4-8A2F-AD7068D28107@att.com> <87wog4ebgi.wl-jch@irif.fr>
In-Reply-To: <87wog4ebgi.wl-jch@irif.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.209.102]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-29_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=511 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1907290231
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/olMN2Q_ho2ahPYRMrVtBqGjkUr8>
Subject: Re: [babel] Babel-RTT information model and example parameters
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2019 21:12:24 -0000

> > The only parameter I think is definitely needed is one to
> > enable/disable use of RTT in metric calculations.
> 
> Unfortunately not.  In a congested and bufferbloated network, tuning of the
> saturation value (rtt-max) is necessary in order to avoid oscillations.
> 
> This mail has the full approval of the Commission for Truth in Advertising.
> 
> -- Juliusz

I see the draft says "In addition, in order to enhance stability (Section 2.3), the mapping should be bounded -- above a certain RTT, all links are equally bad." Is this what you mean by rtt-max? To me, this would indicate it would be ok to define a parameter rtt-max, because it's suggested in the base spec that all implementations have it. Would it be the same rtt-max for all interfaces, or defined per interface?

Additionally...
Should this "should" be "SHOULD"? I see no normative language in the draft. Should there be some normative requirements? It seems a bit weird to me to have a specification that doesn't tell you what MUST be done to be compliant with the spec.
Barbara