[mpls] using a different name for the same thing is not so clever :-) really?

" 徐小虎(义先) " <xiaohu.xxh@alibaba-inc.com> Wed, 28 March 2018 08:00 UTC

Return-Path: <xiaohu.xxh@alibaba-inc.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 012F612426E; Wed, 28 Mar 2018 01:00:48 -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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alibaba-inc.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 U9oZI4JnmBJC; Wed, 28 Mar 2018 01:00:45 -0700 (PDT)
Received: from out0-139.mail.aliyun.com (out0-139.mail.aliyun.com [140.205.0.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E56B1200C1; Wed, 28 Mar 2018 01:00:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1522224039; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=GEt602qIeDRmm+E9GlP/LdLZPJNEFJ/enb3uH1sDiF4=; b=L2nqNtTPY6dKQQqOY6rtU8EM39FunMoYFF7SY9hS+lfuMtxuKybHexGK/w5jy3Iq2b2pAGq93uySZilfOax0MsNr2D9l0p0dWCauDm6KxclgsV7/+1e9kC3bTugEbc126z7jXcG9lZDLTdA8E4Bg9TduOzIg/n7MZEOjcKm1jlA=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R161e4; CH=green; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e01e01534; MF=xiaohu.xxh@alibaba-inc.com; NM=1; PH=DW; RN=4; SR=0; TI=W4_5211206_v5ForWebDing_0A930E47_1521808706771_o7001c8332;
Received: from WS-web (xiaohu.xxh@alibaba-inc.com[W4_5211206_v5ForWebDing_0A930E47_1521808706771_o7001c8332]) by e02c03304.eu6 at Wed, 28 Mar 2018 16:00:39 +0800
Date: Wed, 28 Mar 2018 16:00:39 +0800
From: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
To: adrian <adrian@olddog.co.uk>, "Ruediger.Geib" <Ruediger.Geib@telekom.de>, spring <spring@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Reply-To: "徐小虎(义先)" <xiaohu.xxh@alibaba-inc.com>
Message-ID: <a4a838f7-9665-44c5-a60b-a008cdbc1d1d.xiaohu.xxh@alibaba-inc.com>
X-Mailer: [Alimail-Mailagent revision 948139][W4_5221377][v5ForWebDing][Safari]
MIME-Version: 1.0
References: <946686b0-7802-4c59-9a96-991c94d76a3e.>
In-Reply-To: <946686b0-7802-4c59-9a96-991c94d76a3e.>
x-aliyun-mail-creator: W4_5221377_v5ForWebDing_QvNTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTJfNikgQXBwbGVXZWJLaXQvNjA0LjUuNiAoS0hUTUwsIGxpa2UgR2Vja28pIFZlcnNpb24vMTEuMC4zIFNhZmFyaS82MDQuNS42La
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_81983_55008940_5abb4ba7_49c4ae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/y7FTc38ysVf6PyJlA04MEFSN9nc>
Subject: [mpls] using a different name for the same thing is not so clever :-) really?
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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, 28 Mar 2018 08:00:48 -0000

Hi Adrian,
Please see my comments inline with [Xiaohu]------------------------------------------------------------------Adrian Farrel <adrian@olddog.co.uk>2018年3月22日(星期四) 22:32Ruediger.Geib <Ruediger.Geib@telekom.de>; spring <spring@ietf.org>Re: [spring] What is "TE" and the rechartering discussion
Hey Ruediger,

Our agreement may be so complete that we may get mistaken for each other in the
corridor.

Using a different name for different things is wise.
Of course, using a different name for the same thing is not so clever :-) So
digging a little to make sure we know what each group is talking about will
still be helpful.
[Xiaohu] I couldn't agree more. However, I still see that some people are happy to write drafts by using different name for the same thing which has been described in the existing drafts many years before:
One example is Section 6 of https://tools.ietf.org/html/draft-farrel-mpls-sfc vs https://tools.ietf.org/html/draft-xu-mpls-service-chaining-03 (note that this draft has been merged into https://tools.ietf.org/html/draft-xu-clad-spring-sr-service-chaining-00).
Best regards,Xiaohu

Adrian

> -----Original Message-----
> From: Ruediger.Geib@telekom.de [mailto:Ruediger.Geib@telekom.de]
> Sent: 22 March 2018 13:36
> To: adrian@olddog.co.ukspring@ietf.org
> Subject: AW: [spring] What is "TE" and the rechartering discussion
> 
> Hi Adrian,
> 
> that's a fair proposal, I think. In addition, it may help to avoid the term
"Traffic
> Engineering" when rechartering Spring. Spring needs to recharter now. I didn't
> see any emails on the list which advised against Spring policy routing and the
> related OAM mechanisms as future work items.
> 
> Regards,
> 
> Ruediger
> 
> -----Ursprüngliche Nachricht-----
> Von: spring [mailto:spring-bounces@ietf.org] Im Auftrag von Adrian Farrel
> Gesendet: Donnerstag, 22. März 2018 14:08
> An: spring@ietf.org
> Betreff: [spring] What is "TE" and the rechartering discussion
> 
> There *might* be some disconnect between:
> - What TEAS means by "TE"
> - What TEAS is perceived to mean by "TE"
> - What Spring means by "TE"
> - What Spring is perceived to mean by "TE"
> 
> An option (although it would slow the discussion a bit - it might speed it in
the
> long term) would be to try to clarify these points with a draft or a joint
discussion
> session.
> Of course, that MUST NOT delay or derail the development of protocol
> specifications, but I think the discussion about where work should be done is
a
> distraction: until that decision has been made (by the chairs and ADs) we
should
> write drafts and we should discuss them on any and all mailing lists where
people
> lurk who could help us get the work right.
> 
> Adrian
> 
> _______________________________________________
> spring mailing list
> spring@ietf.orghttps://www.ietf.org/mailman/listinfo/spring

_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring