RE: Expired draft-ietf-rtgwg-ipfrr-ip-mib

<stephane.litkowski@orange.com> Thu, 29 November 2018 13:15 UTC

Return-Path: <stephane.litkowski@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 9ADA7130DE9 for <rtgwg@ietfa.amsl.com>; Thu, 29 Nov 2018 05:15:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 QKaJ8BJ6WfZm for <rtgwg@ietfa.amsl.com>; Thu, 29 Nov 2018 05:15:51 -0800 (PST)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11E1C130DC8 for <rtgwg@ietf.org>; Thu, 29 Nov 2018 05:15:51 -0800 (PST)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 435J1K2hbwz1071; Thu, 29 Nov 2018 14:15:49 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.63]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 435J1K0QrRzDq7r; Thu, 29 Nov 2018 14:15:49 +0100 (CET)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM6E.corporate.adroot.infra.ftgroup ([fe80::f5a7:eab1:c095:d9ec%18]) with mapi id 14.03.0415.000; Thu, 29 Nov 2018 14:15:48 +0100
From: stephane.litkowski@orange.com
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
CC: Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "akatlas@juniper.net" <akatlas@juniper.net>, "chrisbowers.ietf@gmail.com" <chrisbowers.ietf@gmail.com>, Jeff Tantsura <jefftant.ietf@gmail.com>
Subject: RE: Expired draft-ietf-rtgwg-ipfrr-ip-mib
Thread-Topic: Expired draft-ietf-rtgwg-ipfrr-ip-mib
Thread-Index: AdSEs5ld+s1731mKSr61rYI3YnS5fwAvdI/AAGkeoBAAMf09MAAAXO/gAAF5+iA=
Date: Thu, 29 Nov 2018 13:15:48 +0000
Message-ID: <21043_1543497349_5BFFE685_21043_189_1_9E32478DFA9976438E7A22F69B08FF924B777B83@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <DB5PR0301MB19093956D0D74D81C602A1849DD60@DB5PR0301MB1909.eurprd03.prod.outlook.com> <32517_1543227580_5BFBC8BC_32517_117_1_9E32478DFA9976438E7A22F69B08FF924B776103@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <DB5PR0301MB19097935F182DF73573A29799DD10@DB5PR0301MB1909.eurprd03.prod.outlook.com> <13654_1543494092_5BFFD9CC_13654_57_1_9E32478DFA9976438E7A22F69B08FF924B777B34@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <DB5PR0301MB19091E693B03797DFDE4BBEC9DD20@DB5PR0301MB1909.eurprd03.prod.outlook.com>
In-Reply-To: <DB5PR0301MB19091E693B03797DFDE4BBEC9DD20@DB5PR0301MB1909.eurprd03.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF924B777B83OPEXCLILMA4corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/FPCHDk_gNWFYRBQVglSNHY2aTXc>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 29 Nov 2018 13:15:55 -0000

Hi Sasha,

Currently TILFA is part of the SR IGP Yang models and there is an augmentation of the existing fast-reroute container.

Consistency between YANG models is a valid concern ! for IS-IS and OSPF (including SR extensions) we are working very closely together to ensure consistency. However there is still a chance that we've missed something.


From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Thursday, November 29, 2018 13:42
To: LITKOWSKI Stephane OBS/OINIS
Cc: Michael Gorokhovsky; rtgwg@ietf.org; akatlas@juniper.net; chrisbowers.ietf@gmail.com; Jeff Tantsura
Subject: RE: Expired draft-ietf-rtgwg-ipfrr-ip-mib

Stephane,
Lots of thanks for a prompt response.

I think that a proposal to extract FRR-related things from the IGP YANG data models and to move them to a new document in a different WG would be rejected at this stage - and justly so.

On the other hand, I wonder what is supposed to happen with YANG for TI-LFA:

-          I would expect substantial overlap with YANG definitions for LFA-based FRR in IS-IS and OSPF

-          Since these  definitions are in two different documents handled by the LSR WG, and TI-LFA is handled by the RTGWG, this would probably mean yet another draft, with its own lifecycle etc.
Keeping all these documents consistent (at least in their overlapping parts) can be quite non-trivial IMHO.

One practical (and easy to implement) step should be removal of the milestone "Submit MIB for IP Fast-Reroute for publication as Proposed Standard" (with the target date two years behind us already) from the RTGWG charter<https://datatracker.ietf.org/group/rtgwg/about/>. Chris/Jeff?

Regards,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com

From: stephane.litkowski@orange.com <stephane.litkowski@orange.com>
Sent: Thursday, November 29, 2018 2:22 PM
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Cc: Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>; rtgwg@ietf.org; akatlas@juniper.net; kkoushik@cisco.com
Subject: RE: Expired draft-ietf-rtgwg-ipfrr-ip-mib

That's a possibility. However for now, we have taken the approach to add FRR into the IGP models.
You could propose your view to the LSR list. ISIS and OSPF yang are in Shepherd's review state.


From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Wednesday, November 28, 2018 13:42
To: LITKOWSKI Stephane OBS/OINIS
Cc: Michael Gorokhovsky; rtgwg@ietf.org<mailto:rtgwg@ietf.org>; akatlas@juniper.net<mailto:akatlas@juniper.net>; kkoushik@cisco.com<mailto:kkoushik@cisco.com>
Subject: RE: Expired draft-ietf-rtgwg-ipfrr-ip-mib

Stephane,
Lots of thanks for a prompt response.

I have guessed that the reason for dropping the MIB draft for IP FRR was transition to YANG data models.
And it seems that the current versions of the OSPF and IS-IS Yang data model drafts cover not just FRR-related counters but also FRR-related configuration and state attributes.

However, this looks as duplicated definitions (with some protocol-specific variations). Doesn't it make more sense to place all these definitions into a single document?

Regards, and lots of thanks in advance,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>

From: stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com> <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Sent: Monday, November 26, 2018 12:20 PM
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>>; akatlas@juniper.net<mailto:akatlas@juniper.net>; kkoushik@cisco.com<mailto:kkoushik@cisco.com>
Cc: Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com<mailto:Michael.Gorokhovsky@ecitele.com>>; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: RE: Expired draft-ietf-rtgwg-ipfrr-ip-mib

Hi Sasha,

It was decided to stop the work on this document and focus on YANG. The IPFRR MIB counters are part of the OSPF and ISIS yang models.

Brgds,

From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
Sent: Sunday, November 25, 2018 12:46
To: akatlas@juniper.net<mailto:akatlas@juniper.net>; kkoushik@cisco.com<mailto:kkoushik@cisco.com>; LITKOWSKI Stephane OBS/OINIS
Cc: Michael Gorokhovsky; rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Subject: Expired draft-ietf-rtgwg-ipfrr-ip-mib

Dear colleagues,
I have noticed that  IP FRR MIB draft (that appears as one of the WG milestones with November-2015 as the target date) has expired more than 2 years ago.  At the same time I have not seen any YANG draft that could be considered as its replacement.

I wonder if there are any plans to resuscitate this draft or to replace it by a YANG one.

Your timely feedback would be highly appreciated.

Regards, and lots of thanks in advance,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>


___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this
transmission in error, please inform us by e-mail, phone or fax, and then delete the original
and all copies thereof.
___________________________________________________________________________

_________________________________________________________________________________________________________________________



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.

___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this
transmission in error, please inform us by e-mail, phone or fax, and then delete the original
and all copies thereof.
___________________________________________________________________________

_________________________________________________________________________________________________________________________



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.

___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this
transmission in error, please inform us by e-mail, phone or fax, and then delete the original
and all copies thereof.
___________________________________________________________________________

_________________________________________________________________________________________________________________________

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.