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

Loa Andersson <loa@pi.nu> Tue, 17 March 2015 15:46 UTC

Return-Path: <loa@pi.nu>
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 9A6571A701E; Tue, 17 Mar 2015 08:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 PsBpOZXvCVpW; Tue, 17 Mar 2015 08:46:26 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6F051A701A; Tue, 17 Mar 2015 08:46:25 -0700 (PDT)
Received: from [172.20.11.241] (unknown [46.218.58.213]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id B5FBD180145E; Tue, 17 Mar 2015 16:46:23 +0100 (CET)
Message-ID: <55084C4D.3050107@pi.nu>
Date: Tue, 17 Mar 2015 16:46:21 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>, Joshua George <jgeorge@google.com>
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>
In-Reply-To: <550841BA.4040205@labn.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/tBKIPMbREld1eVx5p-V3hwFMrSU>
Cc: draft-openconfig-mpls-consolidated-model@ietf.org, rtg-yang-coord@ietf.org
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: Tue, 17 Mar 2015 15:46:28 -0000

Lou,


On 2015-03-17 16:01, Lou Berger wrote:
>
> Loa,
>      See below.
>
<snip>

> Not sure why,but I leave it to the ADs either way.

Hmmm - the work you been doing here - driving the consensus in the
involved working groups are for the wg chairs, if we need a higher
level of "calling the consensus" that might be for the ADs.

>
>>> Does this make sense?
>> Makes sense to me. Just now we have a presentation on the MPLS agenda,
>> since time is the scarce thing during the IETF week, I don't think we
>> should present it more than in one place.
>
> Actually, I may disagree.  I do agree that having popup discussions on
> the same (overal structure) topic isn't too helpful.  But, I think
> having the relevant portion of the document presented in the relevant WG
> (with some context of course) makes the most sense.   If your comment
> was directed at the former, than I'm in complete agreement.

I was thinking about repeating the same discussion in more than one wg.

I'm struggling a bit to understand what you are saying. While I can
understand the formula "relevant piece of the to the relevant wg", this
is not what I see happening. What we have in the agendas posted today
is that mpls and teas have slots, but you say the draft (or pieces of
the draft) are relevant also at least to rtgwg, spring and i2rs, and
there are currently no agenda slots for that discussion in those
wg's, neither am I sure that splitting it up that much is most
productive.

To discuss the home(s) of the document, I think the entire scope should
be on the able somewhere (at least on some table somewhere during the
week).

So I'm wondering a bit about what instructions to give the authors for
the discussion in mpls.

We could tell them "give us some context, but for the rest keep to what
is strictly relevant for MPLS" or we could say "give us some context,
discuss what is relevant for MPLS and also bring up what you feel you
has not had opportunity to discuss in any other wg during week and we
will take this as a basis for discussing what will happen with the
document on this list".

Currently I'm in favor of the second alterntive, but I'm open to
discuss any other plan.

/Loa
>
>
>>
>> We have it on Friday, together with the rest of the mpls-yang
>> discussion. We can keep it on our agenda and have every other group
>> point to that discussion. Makes sense to me since we can use the
>> week for off-line and mailing list discussion and try to come up
>> with some educated approximation of a plan on Friday.
>
> TEAS also has a slot on it's agenda for the draft.  My expectation (as
> chair) most of the time will be spent discussing the WG-related portion
> of the document that overlaps other individual documents that are also
> being discussed, and perhaps also how the in-WG scope models tie into
> other models.  IMO omitting this draft from our Dallas discussions would
> hurt WG progress on the topic.
>
> I'm not expecting to cover the out of scope portions of the draft in our
> TEAS meeting in Dallas, and interest in the overall structure discussion
> let me to start this thread.
>
> Lou
>> /Loa
<snip>
> _______________________________________________
> 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