Re: [Rtg-yang-coord] I-D Action: draft-openconfig-mpls-consolidated-model-00.txt

Alia Atlas <akatlas@gmail.com> Thu, 19 March 2015 16:13 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC2101ACE13; Thu, 19 Mar 2015 09:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.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, USER_IN_WHITELIST=-100] 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 cnNTRnWuICMW; Thu, 19 Mar 2015 09:13:33 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01DE51A1A32; Thu, 19 Mar 2015 09:13:33 -0700 (PDT)
Received: by obbgg8 with SMTP id gg8so58164693obb.1; Thu, 19 Mar 2015 09:13:32 -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=9nB3wtBsxhcUndcr2maFuJVbGiM3RMglNBfNjN3Qp8Y=; b=ZNyMdjE6canL425dToxArq52Ca+Qb5eIpSmfIZfelyLlxPDVj8duCETmAqAipaK9JO ogIQHmnqPmFLPUBwcK0lVtW7JOKWWGGxCr6HAx0hkJ0HWrGfWwuB2nfv9jRDMc1Z/J47 rxfRjQbR+gqzpwAMjz7Cq7Ixs7yfytejSaEQ94hIYJBp5Za1NloRnbfkd0WhZc2U5WsE /gDl4XkdB5RShTVFac2k1CzlwpcV07BoyGuUw5OsRCK5jaFsmfnHVgs7DthD7SY9nq3m rPj+ucMiifRFI4r+JLnK3cQsRMyPEQHsAxVs2IFvNverx1bCBOCW/AYdm+xlRIU+b5qP Lv7g==
MIME-Version: 1.0
X-Received: by 10.60.42.211 with SMTP id q19mr62257060oel.58.1426781612452; Thu, 19 Mar 2015 09:13:32 -0700 (PDT)
Received: by 10.60.44.198 with HTTP; Thu, 19 Mar 2015 09:13:32 -0700 (PDT)
In-Reply-To: <550AD956.20800@pi.nu>
References: <20150309224815.8246.60629.idtracker@ietfa.amsl.com> <14c12af9498.27e9.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <14c12b948f8.27e9.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <CAKL6Z6kXHuARkLtVT19TmLwtOGnrur_7KgOgP91p+5tMFxTF3A@mail.gmail.com> <5507588A.9010105@labn.net> <5507E141.5010807@pi.nu> <550841BA.4040205@labn.net> <55084C4D.3050107@pi.nu> <5508522E.8020402@labn.net> <63CB93BC589C1B4BAFDB41A0A19B7ACD1A05F905@USIDCWVEMBX08.corp.global.level3.com> <D12DCF90.10C80%acee@cisco.com> <5509AB9E.6090201@labn.net> <550A95DF.4080805@pi.nu> <550A9F40.10109@pi.nu> <550AD63A.8030008@labn.net> <550AD956.20800@pi.nu>
Date: Thu, 19 Mar 2015 12:13:32 -0400
Message-ID: <CAG4d1reyAd5LwAB3_bg57DZuwV-hwogxK0+Zm_-j1sjWKxKQsQ@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: Loa Andersson <loa@pi.nu>
Content-Type: multipart/alternative; boundary=089e0111dcc22eb0430511a67b5f
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/0IsyimHYZln27eadynl1C6RzGg0>
Cc: "draft-openconfig-mpls-consolidated-model@ietf.org" <draft-openconfig-mpls-consolidated-model@ietf.org>, "rtg-yang-coord@ietf.org" <rtg-yang-coord@ietf.org>, Lou Berger <lberger@labn.net>, Alia Atlas <akatlas@juniper.net>, Joshua George <jgeorge@google.com>
Subject: Re: [Rtg-yang-coord] I-D Action: draft-openconfig-mpls-consolidated-model-00.txt
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2015 16:13:35 -0000

Hi Lou and Loa,

Thanks for your focus and concern on this.

I share very similar concerns about how to handle the interactions and
structure between different
YANG models.  In fact, I am in the process of setting up a routing area
design team to write
up a routing yang architecture.  This may also include common conventions
and recommendations
for how to handle information to be used by multiple models and so on.

At the Routing WG Chairs lunch, one of the topics will be discussing how to
coordinate and handle
the various proposed YANG models and the overlaps.

One of the useful aspects of this particular model is that it's looking at
it from a "what does it do for me" perspective instead of a "here's what
the protocol knobs are".  Of course, that doesn't address many
of the questions around multiple uses of the same technology for different
purposes or how to handle
different feature sets being implemented.

I am somewhat reluctant to request breaking up of a model into multiple
drafts simply to accommodate
the IETF Working Group structure - if it doesn't also improve the models or
make it easier to get really
good reviews.

So, in short - let's have some good discussion on this, work towards having
an architecture with meta-model
for at least routing, and see what makes the most sense.

Thanks,
Alia

On Thu, Mar 19, 2015 at 10:12 AM, Loa Andersson <loa@pi.nu> wrote:

> Lou,
>
> I take this to mean:
> "Yes, we can take the discussion as suggest below in Dallas, but we also
>  need a discussion on the rtg-yang-coord@ietf.org, possibly before,
>  during and after the Dallas meeting."
>
> I agree to that!
>
> /Loa
>
>
> On 2015-03-19 14:59, Lou Berger wrote:
>
>>
>>
>> On 3/19/2015 6:04 AM, Loa Andersson wrote:
>>
>>> All,
>>>
>>> This of course triggered the obvious question - "What is your plan"?
>>>
>>> So what I'd like to to see for draft-openconfig-mpls-consolidated-model
>>> discussions in Dallas is
>>>
>>> - that the discussion on the overall structure goes to the rtgwg
>>>
>>> - that the technology specific parts are discussed in the relevant
>>>     working group; it see the following wg's that (should) have an
>>>     interest in this
>>>     - teas
>>>     - mpls
>>>     - spring
>>>     - i2rs (?), this might be more of an interest in the overall
>>>       structure.
>>>
>>> For mpls this discussion will take place on Friday, if we during the
>>> week can agree on a plan forward, and we need time to socialize that
>>> I think there are a few minutes available in the mpls meeting do that.
>>>
>>
>> So the general questions I see / have, which are wider than the scope of
>> this draft, are:
>> 1. how does the whole control plane (including te+non-te signaling and
>> routing) picture fit together and relate to other/existing models?
>> 2. how do all the different topology/service models fit together?
>> 3. What is the commonality in the data plane models of MPLS and GMPLS
>> (LSPs)?
>>     (Yes this assumes that there isn't a full model per controlled
>> technology.)
>>
>> I think different WGs are/can be involved in addressing these.  As I
>> said before, I personally care more about these being discussed then
>> where they are discussed.  I like your plan as it provides a place to
>> catch any topics not already covered earlier in the week.
>>
>> In the interim, it would be good to start on the actual discussions on
>> this (or whichever appropriate) list.
>>
>> Lou
>>
>>> /Loa
>>>
>>>
>>>
>>> On 2015-03-19 10:24, Loa Andersson wrote:
>>>
>>>> Folks,
>>>>
>>>> I have not seen any reaction to this, what is the plan?
>>>>
>>>> /Loa
>>>>
>>>> On 2015-03-18 17:45, Lou Berger wrote:
>>>>
>>>>> Sounds like there's a plan afoot to give rtgwg time to discuss this
>>>>> thread/draft (as well as relive some of the overall time constraints. )
>>>>>     My understanding is that the overall structure  &  base document
>>>>> will
>>>>> be discussed there, while the other WG-specific information /
>>>>> sub-models
>>>>> (e.g., LDP, RSVP, TE, SR, ...) will covered in their respective WGs.
>>>>>
>>>>> Alia/ADs/Authors,
>>>>>
>>>>> Can you confirm?
>>>>>
>>>>> Thanks,
>>>>> Lou
>>>>>
>>>>> On 3/17/2015 12:35 PM, Acee Lindem (acee) wrote:
>>>>>
>>>>>> RTGWG agenda is already jam packed - no room for any additions.
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Rtg-yang-coord mailing list
>>>>> Rtg-yang-coord@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/rtg-yang-coord
>>>>>
>>>>>
>>
>> _______________________________________________
>> Rtg-yang-coord mailing list
>> Rtg-yang-coord@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtg-yang-coord
>>
>>
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
> _______________________________________________
> Rtg-yang-coord mailing list
> Rtg-yang-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/rtg-yang-coord
>