Re: [mpls] Should we split draft-bryant-mpls-synonymous-flow-labels into arch and application

Loa Andersson <loa@pi.nu> Wed, 23 September 2015 09:17 UTC

Return-Path: <loa@pi.nu>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E60D1AC3C5 for <mpls@ietfa.amsl.com>; Wed, 23 Sep 2015 02:17:35 -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 h-NTP7SK_79f for <mpls@ietfa.amsl.com>; Wed, 23 Sep 2015 02:17:33 -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 EE9F21A92AF for <mpls@ietf.org>; Wed, 23 Sep 2015 02:17:32 -0700 (PDT)
Received: from [192.168.0.102] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (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 28E0418013B2; Wed, 23 Sep 2015 11:17:31 +0200 (CEST)
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "stbryant@cisco.com" <stbryant@cisco.com>, "Andrew G. Malis" <agmalis@gmail.com>
References: <55D202B9.7040105@cisco.com> <55FD8852.7040307@pi.nu> <CAA=duU1+iOo_jaA7EOzGRQ6LqnMwLQwTNpJLfd8KVYofTJ9_yw@mail.gmail.com> <55FFCEC0.3020805@cisco.com> <7347100B5761DC41A166AC17F22DF112218DCB92@eusaamb103.ericsson.se>
From: Loa Andersson <loa@pi.nu>
Message-ID: <56026E29.8060104@pi.nu>
Date: Wed, 23 Sep 2015 11:17:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <7347100B5761DC41A166AC17F22DF112218DCB92@eusaamb103.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/p6d3UDSJvMkt-knYXl4KlHkEv18>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "draft-bryant-mpls-synonymous-flow-labels@tools.ietf.org" <draft-bryant-mpls-synonymous-flow-labels@tools.ietf.org>
Subject: Re: [mpls] Should we split draft-bryant-mpls-synonymous-flow-labels into arch and application
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2015 09:17:35 -0000

Greg and Stewart,

This is an individual document, if the co-authors have consensus on
splitting the document, please go ahead and do so.

My personal opinion is that extracting the architecture is fine as
long as we will have two viable documents.

/Loa

On 2015-09-21 20:00, Gregory Mirsky wrote:
> Dear All,
>
> I agree with Stewart that extracting architectural part of the
> synonymous labels discussion would improve the clarity and may add new
> use cases in addition to RFC 6374. As co-author I support the split and
> will be glad to work on that.
>
>                  Regards,
>
>                                  Greg
>
> *From:*mpls [mailto:mpls-bounces@ietf.org] *On Behalf Of *Stewart Bryant
> *Sent:* Monday, September 21, 2015 2:33 AM
> *To:* Andrew G. Malis; Loa Andersson
> *Cc:* mpls@ietf.org; draft-bryant-mpls-synonymous-flow-labels@tools.ietf.org
> *Subject:* Re: [mpls] Should we split
> draft-bryant-mpls-synonymous-flow-labels into arch and application
>
> Andy
>
> Worrying about the work needed to process the drafts (which will be
> quite small) is putting
> the cart before the horse.
>
> What is important is clarity of ideas and clarity of understanding by
> the reader. The IETF
> is somewhat unique in it's production of micro specs that provide
> separation of ideas
> and this has served us well over the years.
>
> Whilst the draft started out as an RFC6374 solution, the technology
> proposed has a
> more universal application.
>
> It therefore makes sense to me to produce a description of base
> technology uncluttered
> by a detailed solution to an application, and a separate text on the
> application.
>
> - Stewart
>
>
>
> On 19/09/2015 17:28, Andrew G. Malis wrote:
>
>     Loa,
>
>     If this was a big effort, I'd say go for the split, but it's a short
>     draft so I don't really see the need to double the overhead work for
>     the WG, chairs, ADs, and RFC Editor for what would be two very short
>     drafts!
>
>     Cheers,
>
>     Andy
>
>     On Sat, Sep 19, 2015 at 12:07 PM, Loa Andersson <loa@pi.nu
>     <mailto:loa@pi.nu>> wrote:
>
>     Working Group,
>
>     I have not seen any responses to this mail from Stewart! Take a look
>     and see if you have an opinion.
>
>     /Loa
>
>
>
>     On 2015-08-17 17:50, Stewart Bryant wrote:
>
>         At the last IETF the question arose as to what the correct
>         document structure should be for the synonymous
>         label work.
>
>         The core draft is: draft-bryant-mpls-synonymous-flow-labels
>         which is a mixture pure SFL work and RFC6374 applications
>         work.
>
>         My inclination is to split the draft in two to separate the
>         SFL architecture from the RFC6374 application. However I
>         would like to take the sense of the WG on this.
>
>         I know that there needs to be more work on requirements
>         and will do a word by word review of that text and make proposals
>         and of course review comments on any of these texts are
>         always welcome.
>
>         - Stewart
>
>         _______________________________________________
>         mpls mailing list
>         mpls@ietf.org <mailto:mpls@ietf.org>
>         https://www.ietf.org/mailman/listinfo/mpls
>
>
>     _______________________________________________
>     mpls mailing list
>     mpls@ietf.org <mailto:mpls@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mpls
>
>
>
>
> --
>
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>