Re: [Isis-wg] comments on draft-litkowski-isis-yang-isis-cfg-01

Alia Atlas <akatlas@gmail.com> Tue, 29 July 2014 19:41 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B362D1A0ABD for <isis-wg@ietfa.amsl.com>; Tue, 29 Jul 2014 12:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 cD9Pi5eoc7rw for <isis-wg@ietfa.amsl.com>; Tue, 29 Jul 2014 12:41:49 -0700 (PDT)
Received: from mail-yk0-x236.google.com (mail-yk0-x236.google.com [IPv6:2607:f8b0:4002:c07::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 969851A0A91 for <isis-wg@ietf.org>; Tue, 29 Jul 2014 12:41:49 -0700 (PDT)
Received: by mail-yk0-f182.google.com with SMTP id q9so90850ykb.41 for <isis-wg@ietf.org>; Tue, 29 Jul 2014 12:41:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7pnbMZnGDZasK7SuZtY/BGT911nUDdHgv4mnMP/ESvE=; b=HchDUtzvmtvOMKmtfKPxv24vDEZEneUFAXRSgfJQwHQKeZ/O0fKhutGdAdJp62dUoj 50yRWtem2A0fdqZ87eXWWF/CC2tJvJ2gUrhHQLtVkmHpmmb7s5bxeEaLxj4moBas7GyY /feP1ZFHZg6uz98BnFVfxpeq3aPvxwHE7IMH0o7qsnX6/Hd15XumZj2zTQoQhpf+60JU iA2iK46wtmjiulIL9ONmWuRKFXJ2kpWmf04sFviW3O/5KNvVOAifOsGu8fznRc6Ixit/ +NhyE0IvkwT2R36qEnuF7qNJpvhW25ocRJ5LK8d4QK9gNqXH3JPlAQjVBCFCUvgPolY9 kqmQ==
MIME-Version: 1.0
X-Received: by 10.236.85.208 with SMTP id u56mr6254895yhe.48.1406662908927; Tue, 29 Jul 2014 12:41:48 -0700 (PDT)
Received: by 10.170.110.17 with HTTP; Tue, 29 Jul 2014 12:41:48 -0700 (PDT)
In-Reply-To: <23146_1406621095_53D755A7_23146_1836_1_9E32478DFA9976438E7A22F69B08FF9205E34E@OPEXCLILM34.corporate.adroot.infra.ftgroup>
References: <0F26584357FD124DB93F1535E4B0A65036804905@szxema508-mbx.china.huawei.com> <4223_1406059402_53CEC38A_4223_4491_1_9E32478DFA9976438E7A22F69B08FF92044506@OPEXCLILM34.corporate.adroot.infra.ftgroup> <0F26584357FD124DB93F1535E4B0A65036804A82@szxema508-mbx.china.huawei.com> <20140728153855.GB18120@juniper.net> <23146_1406621095_53D755A7_23146_1836_1_9E32478DFA9976438E7A22F69B08FF9205E34E@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Date: Tue, 29 Jul 2014 15:41:48 -0400
Message-ID: <CAG4d1rf_BLx8Wecyk=vTT-Dt2=OTjv+D3+xL_SxUpAQsa8ZLHg@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: Stephane Litkowski <stephane.litkowski@orange.com>
Content-Type: multipart/alternative; boundary=20cf301af725016ccc04ff5a3bcd
Archived-At: http://mailarchive.ietf.org/arch/msg/isis-wg/-Uy7Uv0mgvoVeCGVz7CSygBH6Tk
Cc: Hannes Gredler <hannes@juniper.net>, "Wunan \(Eric\)" <eric.wu@huawei.com>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] comments on draft-litkowski-isis-yang-isis-cfg-01
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2014 19:41:51 -0000

Hi Stephane,

On Tue, Jul 29, 2014 at 4:04 AM, <stephane.litkowski@orange.com> wrote:

> Hi Hannes,
>
> > hmm can we first collect some TE related atrributes that apply both to
> OSPF and IS_IS before making that call ?
>
> Based on the last discussions we had at IETF, the best solution would be
> to have TE attributes directly in the ISIS model in a similar way as OSPF
> rather than trying to define a common augmented model. I think this
> discussion is similar to the "superset" IGP Link State model where we did
> not want to go into ...


Is there a reason not to look for common groups of information where we
can?  I wouldn't necessarily go for augmenting but for a common group that
both ISIS and OSPF could include.

You might also look at draft-clemm-i2rs-yang-network-topo-00 .

Alia



>  > that one might get hairy pretty soon ... as some vendors define their
> leak policy as prefix, lists and some others call into execution of a
> policy language.
>
> Right, the issue with policy is more global rather than just an ISIS issue
> ... it's not really my priority for now ...
>
>
> Stephane
>
>
> -----Original Message-----
> From: Hannes Gredler [mailto:hannes@juniper.net]
> Sent: Monday, July 28, 2014 17:39
> To: Wunan (Eric)
> Cc: LITKOWSKI Stephane SCE/IBNF; isis-wg@ietf.org
> Subject: Re: [Isis-wg] comments on draft-litkowski-isis-yang-isis-cfg-01
>
> hi eric, stephane,
>
> On Wed, Jul 23, 2014 at 06:04:28PM +0000, Wunan (Eric) wrote:
> [ ... ]
> |    6. Missing traffic engineering ?
> |
> |
> |
> |    [SLI] Only wide metrics are there , but not traffic-eng. I was
> wondering
> |    if TE should be part of a separate datamodel (using augmentation) and
> so
> |    can be used for both OSPF and ISIS protocols    point to discuss
> |
> |    [Eric] Agree to be a separate model. That's will be better.
>
> hmm can we first collect some TE related atrributes that apply both to
> OSPF and IS_IS before making that call ?
>
>
> [ ... ]
> |    8. Missing redistribution related cfg ?
> |
> |
> |
> |    [SLI] Route-filters are part of the core data model. But maybe we
> need to
> |    augment stuffs    I did not look at it yet.
>
> that one might get hairy pretty soon ... as some vendors define their leak
> policy as prefix, lists and some others call into execution of a policy
> language.
>
>
> |    9. Multi-topology should allow to configure more besides ipv4-uni,
> |    ipv6-uni, ipv4-multi, ipv6-multi
> |
> |    These are commonly used configuration which should not be omitted.
> |
> |
> |
> |    [SLI] Please provide more details on what you want.
> |
> |    [Eric] Multi-topology for non-standard ones. This model should allow
> this.
>
> do you have a use-case for this ? - any document that you can refer to ?
>
>
> /hannes
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg
>