Re: [mpls] Confusion over my comments in MPLS WG meeting

George Swallow <swallow.ietf@gmail.com> Tue, 19 July 2016 21:18 UTC

Return-Path: <swallow.ietf@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FADA12D921 for <mpls@ietfa.amsl.com>; Tue, 19 Jul 2016 14:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Khztm0tfx5DV for <mpls@ietfa.amsl.com>; Tue, 19 Jul 2016 14:18:32 -0700 (PDT)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 B254F12D500 for <mpls@ietf.org>; Tue, 19 Jul 2016 14:18:31 -0700 (PDT)
Received: by mail-wm0-x229.google.com with SMTP id q128so32905037wma.1 for <mpls@ietf.org>; Tue, 19 Jul 2016 14:18:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KuF6k6vAO17wbFuSBGhOo6r/pw6b9jld1r2v3G4InkI=; b=edWkX6S8GsETXrZizLPC3F4yzZ7eAO2PfZZYGxFKLb8QxQxMEExIHPRw0zCXE77Wr4 fLPMCcOPr2UBZMcvOgwLqC69arWEw6Pj/3kfWr9YvEI1TJIY0SRmJ3Bx8vn+2VR0apY2 gwFlKT4H/+nNJabWzAbs1ZEhNocqAWDL04CwdcmX5x65YY2Ss3syG6cL6+gA6F11y4RU UqXZGQDkg685GsU6kUJ4CXRlt7km35gE8eHYnbVgvliYGIeVmLhGWJF4A4w4+gU5Mc8j 9kKHCmbr6Mznjw3zt3AyA1BEoant/3s+4kiTe88eUm9A2N+5SeJOitnnF24Sf2qAz17c rsnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KuF6k6vAO17wbFuSBGhOo6r/pw6b9jld1r2v3G4InkI=; b=DPg+988plNuzLgwlm14VVA4qD5aafGagJ9rfuoV8cKuSajyfiFyf14VoEg6GvGdFNs +YypCzdsAeefd//UiXg3TF3raZ2rJL8kYW0WHSFwPPllFqPvFZ2DNrkEUxqrwchT98gt XhpXpZgHGnL9H4z/ryI1NiNjzDQdbDU5pswxkMVGXd4T3b3lz00jRyPw8XTtXRpYcYOn JAD/R4662O/D+PY/m/ytDffJLIH3lj5yErgk8zkmz10wmEAAxWC5ulHjhl1iQtaFE64M CTqTNBrlvy94yW/88WzVMF4uqL3TlGKgrHRL0tgkYiCmFETyP51XX8sYSJRc0v12q28r 6LVw==
X-Gm-Message-State: ALyK8tK/GbG6gGjfyzaBTp+/3HVdO4142XNORZKZrwm1xSqGsmarg77hOV655B20ZWxNQg==
X-Received: by 10.28.134.203 with SMTP id i194mr7000966wmd.22.1468963110212; Tue, 19 Jul 2016 14:18:30 -0700 (PDT)
Received: from [10.24.254.240] ([46.189.28.56]) by smtp.gmail.com with ESMTPSA id b203sm10034351wmh.20.2016.07.19.14.18.29 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 19 Jul 2016 14:18:29 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: George Swallow <swallow.ietf@gmail.com>
X-Mailer: iPhone Mail (13F69)
In-Reply-To: <009501d1e1d0$db05e9a0$9111bce0$@olddog.co.uk>
Date: Tue, 19 Jul 2016 23:18:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B62012B2-0956-442F-9059-5FBCA84AA3B7@gmail.com>
References: <009501d1e1d0$db05e9a0$9111bce0$@olddog.co.uk>
To: adrian@olddog.co.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/RUCBZualNEKHS6tq2b4dx89Lt_8>
Cc: mpls@ietf.org
Subject: Re: [mpls] Confusion over my comments in MPLS WG meeting
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 19 Jul 2016 21:18:34 -0000

Adrian restatement of what I said. It is not the job of these authors to expand their scope because someone else wants a more general solution. If that someone really wants it the can put in the work in the appropriate venue which IMHO is RTGWG. 

George

> On Jul 19, 2016, at 5:18 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> 
> Hi,
> 
> During our discussion of draft-shen-mpls-egress-protection-framework-02 I made
> some comments at the mic.
> 
> The Etherpad records me as saying 
> Adrian - Lets not hang up on word framework.
> 
> ...and that was pretty much my message.
> 
> It felt to me that we were obsessing about the precise interpretation of the
> document title rather than what it actually achieves. It is clear (to me) that
> the document could equally have a title like "framework for the use of MPLS to
> achieve foo" or a "framework to achieve foo in an MPLS network" and that that
> would be obviously an MPLS document. On the other hand (and historically) a
> framework is not an architecture: architectures are usually
> solution-independent; frameworks are often descriptions of how to achieve
> something from a number of building blocks. But if the word "framework" gets in
> the way, simply use a different word.
> 
> In the meeting I then rambled into my beard wondering what would be the point of
> an MPLS working group if we are not able to work on this document that I feel is
> clearly an MPLS document (IRRC Hannes and Kireeti also considered this to be an
> MPLS document). Someone may have misheard me as saying "close down MPLS".
> Although Ross' departure might make this a fitting option, it was not what I was
> saying.
> 
> I think George's point was that if someone thinks that there is value in a
> generic (not limited to MPLS) framework, then they are welcome to write one, and
> RTGWG would be a good venue.
> 
> Adrian
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls