IETF Logo Mail Archive

Re: [CCAMP] draft-ali-ccamp-rc-objective-function-metric-bound-03.txt

"Zafar Ali (zali)" <zali@cisco.com> Fri, 09 August 2013 16:52 UTC

Return-Path: <zali@cisco.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1783D11E8143 for <ccamp@ietfa.amsl.com>; Fri, 9 Aug 2013 09:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.952
X-Spam-Level:
X-Spam-Status: No, score=-9.952 tagged_above=-999 required=5 tests=[AWL=0.647, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qa3pAey+9c7o for <ccamp@ietfa.amsl.com>; Fri, 9 Aug 2013 09:52:44 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 936E521F9831 for <ccamp@ietf.org>; Fri, 9 Aug 2013 09:46:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2377; q=dns/txt; s=iport; t=1376066793; x=1377276393; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=zyZkONJULUd7l6F0NuUv5yCq2owJz0XVBjQrhu76J6k=; b=EV6YHrr+ulR3Pw1Yz2CN0p+e5Z3jHBUH4DDujQL7RnbznJBlYrZKTlVr mFCq7TH8mcgp04TI9Pe12zva4FPKhQ3jd6xx7DzjQfie4e2Ez0j5VSwVx PW7sZlYNIAyRLLWGF+6hAkHLMu7Ft+ur1z9gsnMXXBGc7FRSCRIDCk62n Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFACMcBVKtJXG9/2dsb2JhbABbgwY1UL5RgRoWdIIkAQEBBAEBAWsXBgEIEQMBAQELHS4LFAkIAQEEARIIiAgMuSoEkAE4BoMUdQOpMYMbgio
X-IronPort-AV: E=Sophos;i="4.89,846,1367971200"; d="scan'208";a="245530813"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-8.cisco.com with ESMTP; 09 Aug 2013 16:46:18 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r79GkHmJ016748 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 9 Aug 2013 16:46:17 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.213]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Fri, 9 Aug 2013 11:46:17 -0500
From: "Zafar Ali (zali)" <zali@cisco.com>
To: Fatai Zhang <zhangfatai@huawei.com>, John E Drake <jdrake@juniper.net>, "CCAMP (ccamp@ietf.org)" <ccamp@ietf.org>
Thread-Topic: [CCAMP] draft-ali-ccamp-rc-objective-function-metric-bound-03.txt
Thread-Index: Ac6UXh3OMYPEaNUmSzSE7m3SYlvx7wARnPhAACDxnIA=
Date: Fri, 09 Aug 2013 16:46:16 +0000
Message-ID: <B6585D85A128FD47857D0FD58D8120D30EA01E48@xmb-rcd-x14.cisco.com>
In-Reply-To: <F82A4B6D50F9464B8EBA55651F541CF84EE47162@SZXEML552-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.82.215.174]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <0B75DD73FC52C549931D9B672E6A6EFC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [CCAMP] draft-ali-ccamp-rc-objective-function-metric-bound-03.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 16:52:49 -0000

Hi John/ Fatai-

ERO expansion is an already supported functionality since early days of
RSVP-TE and is widely deployed. There is a new requirement to convey
latency bound in TE networks. Hence a very simple and logical extension in
RSVP TE to support the newly defined TE (latency) metrics.

If we go with your logic, any operator that wants to deploy latency metric
will be forced to deploy a PCE (including in the existing deployments)
which is a no-go. Especially given the RSVP TE extensions are so simple.

Latency is an important "traffic engineering" metric and suggesting not to
support it in RSVP-TE ("traffic engineering") is much odd. If we go with
your logic, we should just simply retire RSVP-TE and FORCE every SP to
deploy PCE (in addition of RSVP-TE) for TE.

Thanks

Regards Š Zafar


-----Original Message-----
From: Fatai Zhang <zhangfatai@huawei.com>
Date: Thursday, August 8, 2013 10:04 PM
To: "jdrake@juniper.net" <jdrake@juniper.net>, "ccamp@ietf.org"
<ccamp@ietf.org>
Subject: Re: [CCAMP]
draft-ali-ccamp-rc-objective-function-metric-bound-03.txt

>Hi John,
>
>Completely agree. 
>
>I also raised this comment in front of the mic during Berlin meeting.
>
>
>
>Best Regards
>
>Fatai
>
>
>-----Original Message-----
>From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of
>John E Drake
>Sent: Friday, August 09, 2013 1:49 AM
>To: CCAMP (ccamp@ietf.org)
>Subject: [CCAMP] draft-ali-ccamp-rc-objective-function-metric-bound-03.txt
>
>Hi,
>
>I have a real concern with this draft because it appears to be heading us
>down the road of re-inventing PCEP in RSVP signaling with the dubious
>justification that it is needed in those situations in which a PCE is not
>available.  However, if you re-invent PCEP in RSVP signaling, then you
>have effectively ensured that there are no situations in which a PCE or
>its signaling equivalent are not available.
>
>Why is this better than simply ensuring that a PCE is available in those
>situations in which it is needed?
>
>Yours Irrespectively,
>
>John
>
>
>_______________________________________________
>CCAMP mailing list
>CCAMP@ietf.org
>https://www.ietf.org/mailman/listinfo/ccamp
>_______________________________________________
>CCAMP mailing list
>CCAMP@ietf.org
>https://www.ietf.org/mailman/listinfo/ccamp

v2.23.0 | Report a Bug | By Email