IETF Logo Mail Archive

Re: [Teas] Last Call: <draft-ietf-teas-native-ip-scenarios-08.txt> (Scenarios and Simulation Results of PCE in Native IP Network) to Informational RFC

S Moonesamy <sm+ietf@elandsys.com> Sat, 28 September 2019 11:47 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72EA712004D; Sat, 28 Sep 2019 04:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 3ibFWGQZ5YyF; Sat, 28 Sep 2019 04:47:10 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 9CF5E120110; Sat, 28 Sep 2019 04:47:10 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.155.140]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x8SBktLD022829 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 28 Sep 2019 04:47:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1569671229; x=1569757629; i=@elandsys.com; bh=RaJl6Ic8PSnwPviFuJz6r9wjDDNZRBMWdrNzFxqVNcI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tCC/0fMdO5YCqMfU7tYlZY1Yl83Ne+twqTWJZYqAWpWT3pA8iLhFzvwftRnGgKLXe O7M8VIVJbMLhSOy9JESK66ZmGtUOcSGSjRtVfyqIdVar3aR0H6EjX7m5iw/te0PNte X8RLPN3dE6RurscGC4k/xrma0ZbsUX5sJ6ihgess=
Message-Id: <6.2.5.6.2.20190928043919.0e4ada60@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 28 Sep 2019 04:46:33 -0700
To: Aijun Wang <wangaijun@tsinghua.org.cn>, teas@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: teas-chairs@ietf.org
In-Reply-To: <51A8CA43-16EB-434F-B197-70EDEB9A90AD@tsinghua.org.cn>
References: <6.2.5.6.2.20190928012653.0c02af80@elandnews.com> <51A8CA43-16EB-434F-B197-70EDEB9A90AD@tsinghua.org.cn>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/CPx-Z8Nl3PK6m2M4yy8OPxXC80M>
Subject: Re: [Teas] Last Call: <draft-ietf-teas-native-ip-scenarios-08.txt> (Scenarios and Simulation Results of PCE in Native IP Network) to Informational RFC
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Sep 2019 11:47:12 -0000

Hi Aijun,
At 02:48 AM 28-09-2019, Aijun Wang wrote:
>Together with the solutions draft, I think they are fit to the 
>deliverables described in the charter of TEAS WG.

Could you or another WG participant else please explain under which 
point in the WG Charter does the draft fit in?

>And actually, the operator's network is composed by the devices from 
>vendors, and the algorithm may be from the university. Isn't such 
>cooperation the direction of operator?

I am not arguing against such cooperation as cooperation is 
useful.  I would expect an operator or university to point out the 
pros and cons or else the document may sound too good to be 
true.  Furthermore, it can be useful to other operators if they are 
the intended audience.

Regards,
S. Moonesamy

v2.23.0 | Report a Bug | By Email