IETF Logo Mail Archive

Re: [babel] information model open issues

"STARK, BARBARA H" <bs7652@att.com> Thu, 02 August 2018 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 E2E43130E29 for <babel@ietfa.amsl.com>; Thu, 2 Aug 2018 14:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 qKI4gwLJGtms for <babel@ietfa.amsl.com>; Thu, 2 Aug 2018 14:12:33 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 58F3E130E20 for <babel@ietf.org>; Thu, 2 Aug 2018 14:12:33 -0700 (PDT)
Received: from pps.filterd (m0049297.ppops.net [127.0.0.1]) by m0049297.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id w72L6Ogq021703; Thu, 2 Aug 2018 17:12:31 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049297.ppops.net-00191d01. with ESMTP id 2km88qj4wx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 02 Aug 2018 17:12:31 -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 w72LCUe4020164; Thu, 2 Aug 2018 17:12:30 -0400
Received: from zlp30483.vci.att.com (zlp30483.vci.att.com [135.47.91.189]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w72LCPbZ020071; Thu, 2 Aug 2018 17:12:26 -0400
Received: from zlp30483.vci.att.com (zlp30483.vci.att.com [127.0.0.1]) by zlp30483.vci.att.com (Service) with ESMTP id AF5E74014663; Thu, 2 Aug 2018 21:12:25 +0000 (GMT)
Received: from GAALPA1MSGHUBAF.ITServices.sbc.com (unknown [130.8.218.155]) by zlp30483.vci.att.com (Service) with ESMTPS id 9E38A4014661; Thu, 2 Aug 2018 21:12:25 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.5]) by GAALPA1MSGHUBAF.ITServices.sbc.com ([130.8.218.155]) with mapi id 14.03.0408.000; Thu, 2 Aug 2018 17:12:25 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: 'Toke Høiland-Jørgensen' <toke@toke.dk>, 'Juliusz Chroboczek' <jch@irif.fr>
CC: Babel at IETF <babel@ietf.org>
Thread-Topic: [babel] information model open issues
Thread-Index: AdQpvguYwHH3NQYTQdev//suP86yMQATSk8AABSHJmAAFrhEgAAE2p0A
Date: Thu, 02 Aug 2018 21:12:24 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DE6411E@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <2D09D61DDFA73D4C884805CC7865E6114DE63655@GAALPA1MSGUSRBF.ITServices.sbc.com> <87600tsnzb.wl-jch@irif.fr> <2D09D61DDFA73D4C884805CC7865E6114DE6390D@GAALPA1MSGUSRBF.ITServices.sbc.com> <87o9eky3ho.fsf@toke.dk>
In-Reply-To: <87o9eky3ho.fsf@toke.dk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.244.33]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-08-02_05:, , 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=762 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1808020207
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/JkrflXt012oRqyX5TEOjdUr5Qiw>
Subject: Re: [babel] information model open issues
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 02 Aug 2018 21:12:35 -0000

> > What intervals make sense to be able to report?
> > It sounds like ones that are simply a reaction to (or the value of) an
> > interval sent by a neighbor do not make sense. I think that would get
> > rid of the babel-neighbor-ihu-interval that Toke initially challenged.
> > But maybe it makes sense to keep the (optional) Hello interval
> > parameters (multicast and unicast)?
> > What about the update interval?
> 
> Both Hello and Update intervals are configurable in Bird, which to me implies
> that reporting the current values in the information model is probably
> worthwhile :)

Cool. Do you make them configurable per interface, or globally? I see that it is possible to send Updates by unicast. If an implementation were to support this, would it make sense for Update intervals to be configurable per neighbor? Or would an interface Update interval still be sufficient for all?
Barbara

v2.23.0 | Report a Bug | By Email