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> Fri, 27 September 2019 22:13 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 AD0B21202A0; Fri, 27 Sep 2019 15:13:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 sHpyB_YlxCPG; Fri, 27 Sep 2019 15:13:41 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 83A99120288; Fri, 27 Sep 2019 15:13:41 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.171.139]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x8RMDTSd022433 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Sep 2019 15:13:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1569622420; x=1569708820; i=@elandsys.com; bh=UQtlSvp/12jw7QMW/d0kd3nJRbfVLtJ4KU+fMHDiSss=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mn3l94571A4rG+pFc5Hpd1uXoyfFyd8yoO5FdJk2jk1rGVJaY5KaEUsg21TMlc0Pe 1h76UqTz+3xi1K82gpsJT4JIaK8yoJT0pWkdmNeHLoaV98vTOQwWMBgjcLaoIGFWSQ JIFPSYiMUFvnlGYZCXnSS7o0z98MM3BeQzPsY/dg=
Message-Id: <6.2.5.6.2.20190927150157.14fd5ac0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 27 Sep 2019 15:13:18 -0700
To: teas@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: teas-chairs@ietf.org
In-Reply-To: <156718853797.25814.8048969416443727476.idtracker@ietfa.ams l.com>
References: <156718853797.25814.8048969416443727476.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/BJkzGtWeBTDl6ZNOXGuPAk6dh20>
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: Fri, 27 Sep 2019 22:13:43 -0000
Hello, At 11:08 AM 30-08-2019, The IESG wrote: >The IESG has received a request from the Traffic Engineering Architecture and >Signaling WG (teas) to consider the following document: - 'Scenarios and >Simulation Results of PCE in Native IP Network' > <draft-ietf-teas-native-ip-scenarios-08.txt> as Informational RFC > >The IESG plans to make a decision in the next few weeks, and solicits final >comments on this action. Please send substantive comments to the >ietf@ietf.org mailing lists by 2019-09-13. Exceptionally, comments may be I am sending the comments to the working group mailing list to decrease the number of emails to ietf@. Section 1 of the draft states that it "provides path optimization simulation results to illustrate the applicability of the CCDR framework". There isn't much information about the different simulations (Section 4). It is not possible to verify the results given the absence of the information. I could not figure out how the draft fits within the WG Charter. What is the purpose of publishing this document as a RFC? Regards, S. Moonesamy
- [Teas] Last Call: <draft-ietf-teas-native-ip-scen… The IESG
- Re: [Teas] Last Call: <draft-ietf-teas-native-ip-… S Moonesamy
- [Teas] 答复: Last Call: <draft-ietf-teas-native-ip-… Aijun Wang
- Re: [Teas] Last Call: <draft-ietf-teas-native-ip-… S Moonesamy
- Re: [Teas] Last Call: <draft-ietf-teas-native-ip-… Aijun Wang
- Re: [Teas] Last Call: <draft-ietf-teas-native-ip-… S Moonesamy
- Re: [Teas] Last Call: <draft-ietf-teas-native-ip-… Aijun Wang
- Re: [Teas] Last Call: <draft-ietf-teas-native-ip-… S Moonesamy
- Re: [Teas] Last Call: <draft-ietf-teas-native-ip-… BRUNGARD, DEBORAH A
- Re: [Teas] Last Call: <draft-ietf-teas-native-ip-… S Moonesamy