Re: [Lsr] draft-ietf-ospf-yang

<stephane.litkowski@orange.com> Wed, 05 December 2018 12:57 UTC

Return-Path: <stephane.litkowski@orange.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7067D124BF6; Wed, 5 Dec 2018 04:57:24 -0800 (PST)
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_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 zms7gGWGbfF9; Wed, 5 Dec 2018 04:57:22 -0800 (PST)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D96DB126BED; Wed, 5 Dec 2018 04:57:21 -0800 (PST)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 438zKB4Wr1z2xg3; Wed, 5 Dec 2018 13:57:18 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.3]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 438zKB36KBzCqkg; Wed, 5 Dec 2018 13:57:18 +0100 (CET)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM5D.corporate.adroot.infra.ftgroup ([fe80::9898:741c:bc1d:258d%19]) with mapi id 14.03.0415.000; Wed, 5 Dec 2018 13:57:18 +0100
From: <stephane.litkowski@orange.com>
To: tom petch <ietfc@btconnect.com>, "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>, "draft-ietf-ospf-yang@ietf.org" <draft-ietf-ospf-yang@ietf.org>, "draft-ietf-teas-yang-te-types@ietf.org" <draft-ietf-teas-yang-te-types@ietf.org>
Thread-Topic: draft-ietf-ospf-yang
Thread-Index: AQHUi/kRtclsquofMk2VeNQNSIp6MaVwGqNw
Date: Wed, 5 Dec 2018 12:57:17 +0000
Message-ID: <31017_1544014638_5C07CB2E_31017_130_1_9E32478DFA9976438E7A22F69B08FF924B77DE59@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <576_1542796445_5BF5349D_576_261_1_9E32478DFA9976438E7A22F69B08FF924B7731BE@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <58C71B78-1C6A-4FB5-B64A-7A38628028C1@cisco.com> <19021_1543406661_5BFE8445_19021_254_3_9E32478DFA9976438E7A22F69B08FF924B776CB0@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <31F7DFA5-7BB5-4E79-AFD9-829AE34BC485@cisco.com> <26904_1543488239_5BFFC2EF_26904_436_1_9E32478DFA9976438E7A22F69B08FF924B777AA8@OPEXCLILMA4.corporate.adroot.infra.ftgroup> <00ce01d48bf8$be184980$4001a8c0@gateway.2wire.net> <41B51A9E-9831-4669-AA87-AFA289303B71@cisco.com> <02b901d48c8b$48d5c920$4001a8c0@gateway.2wire.net>
In-Reply-To: <02b901d48c8b$48d5c920$4001a8c0@gateway.2wire.net>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/4PMgAPdKqHnByvbj94YV8ROvZPk>
Subject: Re: [Lsr] draft-ietf-ospf-yang
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2018 12:57:25 -0000

Hi Tom,

I think that having a different router-id configured per protocol is a matter of deployment. I don't think that we can impose anything in this area. There are use cases where it is good to have separate router-ids per protocol or instances of a protocol. For instance, when a router is part of multiple "administrative domains", it is worth having separate router-ids per admin domain.

However I have a concern about the router-id or te-node-id  bound to a 32 bits number only. How do we do in a pure IPv6 network ?

Brgds,


-----Original Message-----
From: tom petch [mailto:ietfc@btconnect.com] 
Sent: Wednesday, December 05, 2018 12:14
To: Acee Lindem (acee); LITKOWSKI Stephane OBS/OINIS; lsr@ietf.org; draft-ietf-ospf-yang@ietf.org; draft-ietf-teas-yang-te-types@ietf.org
Subject: Re: draft-ietf-ospf-yang

Acee

(Top-posting because the indentation usually fails)

On the TEAS te-types, I had a quick look at where
typedef te-node-id
is used and the answer is lots of places, because it is part of
  grouping explicit-route-hop {
    description    "The explicit route subobject grouping";
    choice type {
      description   "The explicit route subobject type";
      case num-unnum-hop {
        container num-unnum-hop {
          leaf node-id {
            type te-types:te-node-id;
            description   "The identifier of a node in the TE
topology.";
and YANG uses of that grouping are many, in several WGs; however,
because it is a grouping, then the impact of changing the type should be
minimal at least in terms of the I-Ds.

On the multiple router definitions, my research of the IETF memo only
came up with the two cited RFC which, to me, say that you should use an
existing router-id if there is one.

I did look at the documentation of A Major Router Manufacturer and while
they did not give any advice, the default for a te router-id was
loopback0
while the default for a more general router-id, one without te, was
loopback0
which gives me the message, you can make them different but SHOULD NOT
(in IETF terminology).

So while I agree that the two lsr modules should allow per-protocol
configuration, I think that it should carry a health warning in the body
of the I-D that this is not a good idea (I struggle to think of when it
would be a good idea, to use three separate identifiers for, say, BGP
and the two lsr protocols).

Tom Petch

----- Original Message -----
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "tom petch" <ietfc@btconnect.com>om>; <stephane.litkowski@orange.com>om>;
<lsr@ietf.org>rg>; <draft-ietf-ospf-yang@ietf.org>rg>;
<draft-ietf-teas-yang-te-types@ietf.org>
Sent: Tuesday, December 04, 2018 7:46 PM

> Hi Tom,
>
> Let me try to explain.
>
> On 12/4/18, 12:44 PM, "tom petch" <ietfc@btconnect.com> wrote:
>
>     The router id in this I-D confuse me.
>
>     RFC8294 defines
>          typedef router-id { type yang:dotted-quad;
>
> Some implementations configure a global router-id while others only
allow it at the control-plane-protocol level. This is why we have it in
both places.
>
>     ospf-yang defines
>      leaf ipv4-router-id { type inet:ipv4-address;
>
> For better or worse, OSPF has a separate TE address that is routable
and referred to as the TE router-id. You'll note that this is part of
the te-rid container in both the OSPF and IS-IS YANG models. We could
add "-te-" to the leaves to avoid confusion.
>
>     draft-ietf-teas-yang-te-types defines
>       typedef te-node-id {     type yang:dotted-quad;
>      ...       This attribute is mapped to Router ID ....
>
> This is just wrong. It is a routable address in the IGP TE extensions.
I've copied the draft authors.
>
> Thanks,
> Acee Lindem
>
>
>     Three different YANG types for a router id.
>
>     Why?
>
>     Behind this, ospf-yang gives as references for a router te id
>     RFC3630(V2) and RFC5329(V3).  Reading these, my take is that a
router id
>     is needed for te but that the existing id should be used where
possible
>     i.e. creating an additional identifier for the same instance of
the same
>     entity is A Bad Thing (which sounds like a good general
principle).
>     With two objects in the lsr protocols, that would appear to make
at
>     least three identifiers for the same instance of the same entity.
>
>     Why?
>
>     I copy Stephane on this since the same issues apply to the other
lsr
>     protocol, mutatis mutandi.
>
>     Tom Petch
>
>
>
>


_________________________________________________________________________________________________________________________

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.