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:akat...@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.decra...@orange.com<mailto:bruno.decra...@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.i...@gmail.com<mailto:aretana.i...@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.

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

Reply via email to