RE: Alvaro Retana's Discuss on draft-ietf-rtgwg-backoff-algo-07: (with DISCUSS and COMMENT)

<bruno.decraene@orange.com> Tue, 13 March 2018 08:33 UTC

Return-Path: <bruno.decraene@orange.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F27A126CB6; Tue, 13 Mar 2018 01:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.628
X-Spam-Level:
X-Spam-Status: No, score=-2.628 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 Cl8rIOyTj-aM; Tue, 13 Mar 2018 01:33:20 -0700 (PDT)
Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95C6C120727; Tue, 13 Mar 2018 01:33:20 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id E40C3408F3; Tue, 13 Mar 2018 09:33:18 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id C0CA61C005D; Tue, 13 Mar 2018 09:33:18 +0100 (CET)
Received: from OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06]) by OPEXCLILM5D.corporate.adroot.infra.ftgroup ([fe80::9898:741c:bc1d:258d%19]) with mapi id 14.03.0382.000; Tue, 13 Mar 2018 09:33:18 +0100
From: <bruno.decraene@orange.com>
To: Alia Atlas <akatlas@gmail.com>
CC: Alvaro Retana <aretana.ietf@gmail.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-rtgwg-backoff-algo@ietf.org" <draft-ietf-rtgwg-backoff-algo@ietf.org>
Subject: RE: Alvaro Retana's Discuss on draft-ietf-rtgwg-backoff-algo-07: (with DISCUSS and COMMENT)
Thread-Topic: Alvaro Retana's Discuss on draft-ietf-rtgwg-backoff-algo-07: (with DISCUSS and COMMENT)
Thread-Index: AQHTuj1Zof1O/ufRrE6kTjpO4bOnHKPNzvww
Date: Tue, 13 Mar 2018 08:33:18 +0000
Message-ID: <6173_1520929998_5AA78CCE_6173_300_1_53C29892C857584299CBF5D05346208A479CDD88@OPEXCLILM21.corporate.adroot.infra.ftgroup>
References: <151910656889.29750.3686523183770186132.idtracker@ietfa.amsl.com> <11836_1519842985_5A96F6A9_11836_240_1_53C29892C857584299CBF5D05346208A479B3D9E@OPEXCLILM21.corporate.adroot.infra.ftgroup> <CAG4d1rezzMkfvW3-Uxh1kvyYNQu+_kuaDYV3Gjzf2CKCd2bK9w@mail.gmail.com>
In-Reply-To: <CAG4d1rezzMkfvW3-Uxh1kvyYNQu+_kuaDYV3Gjzf2CKCd2bK9w@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A479CDD88OPEXCLILM21corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/CO2Fheh-pgoUsFcns7XUR5dzAxs>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2018 08:33:22 -0000

Hi Alia,

On my side, I’m waiting for Alvaro’s answers on our reply and propositions https://mailarchive.ietf.org/arch/msg/rtgwg/RcOpRdFVQUrwUS9NZxUdH8VmJo4

> It would be excellent to have this approved before Weds at IETF 101.
+1

> I am happy to approve an updated draft being submitted, if necessary, before IETF starts.
Thank you.
As of today, I think I can find some time this week to update the document as/if needed.

Thanks
--Bruno


From: Alia Atlas [mailto:akatlas@gmail.com]


Hi Alvaro, Deborah & Bruno,

Does the most recent version (draft-ietf-rtgwg-backoff-algo-09) resolve the concerns?
It would be excellent to have this approved before Weds at IETF 101.

I am happy to approve an updated draft being submitted, if necessary, before IETF starts.


Thanks,
Alia

On Wed, Feb 28, 2018 at 1:36 PM, <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>> wrote:
Alvaro,

Please find below a follow up on one point

> From: DECRAENE Bruno IMT/OLN
 > Sent: Tuesday, February 27, 2018 11:44 AM

 [...]

>  > -----Original Message-----
 >  > From: Alvaro Retana [mailto:aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>]
 >  > Sent: Tuesday, February 20, 2018 7:03 AM

[...]

>  > ----------------------------------------------------------------------
 >  > COMMENT:
 >  > ----------------------------------------------------------------------

[...]

>
 >  > (2.3) For completeness, the HOLDDOWN_TIMER expiration events (5 and 6) should
 >  > include resetting all the timers, just in case...and to be consistent with the
 >  > initialization description.
 >
 > [Bruno] Good point a priori. However, I don't think anything needs to be changed because:
 > - SPF_TIMER must not be reset as it can still run (if LONG_SPF_DELAY >
 > HOLDDOWN_INTERVAL)
 > - HOLDDOWN_TIMER has already expired by hypothesis
 > - For transition 5 (from LONG_WAIT state), LEARN_TIMER has already expired by hypothesis.
 > - For transition 6 (from SHORT_WAIT state) LEARN_TIMER has already expired because of the
 > following constraint: " The
 >    HOLDDOWN_INTERVAL MUST be defaulted or configured to be longer than the
 > TIME_TO_LEARN_INTERVAL."

Thinking more about this,
Given that transition 6 should not be used if the constraint is enforced on the timers, but transition 6 is still documented for completeness and robustness, I think it makes sense to talk about the LEARN_TIMER during this transition 6.
But actually, this is already in the draft:

   Transition 6: HOLDDOWN_TIMER expiration, while in SHORT_WAIT.

   Actions on event 6:
   o  Deactivate LEARN_TIMER.
   o  Transition to QUIET state.

https://tools.ietf.org/html/draft-ietf-rtgwg-backoff-algo-08#section-5.1

Thanks
--Bruno

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_______________________________________________
rtgwg mailing list
rtgwg@ietf.org<mailto:rtgwg@ietf.org>
https://www.ietf.org/mailman/listinfo/rtgwg


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.