[CCAMP] Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Path Diversity using Exclude Routes

John E Drake <jdrake@juniper.net> Wed, 02 October 2013 18:32 UTC

Return-Path: <jdrake@juniper.net>
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 A21CF21F9ED1 for <ccamp@ietfa.amsl.com>; Wed, 2 Oct 2013 11:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 ZDsnC+qS52sH for <ccamp@ietfa.amsl.com>; Wed, 2 Oct 2013 11:31:59 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe006.messaging.microsoft.com [216.32.181.186]) by ietfa.amsl.com (Postfix) with ESMTP id 1AAB221F88FB for <ccamp@ietf.org>; Wed, 2 Oct 2013 11:26:41 -0700 (PDT)
Received: from mail37-ch1-R.bigfish.com (10.43.68.251) by CH1EHSOBE008.bigfish.com (10.43.70.58) with Microsoft SMTP Server id 14.1.225.22; Wed, 2 Oct 2013 18:26:41 +0000
Received: from mail37-ch1 (localhost [127.0.0.1]) by mail37-ch1-R.bigfish.com (Postfix) with ESMTP id 2587E4E0188 for <ccamp@ietf.org>; Wed, 2 Oct 2013 18:26:41 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -8
X-BigFish: VPS-8(zzddf5rzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah1de097h186068h8275dhz2fh2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail37-ch1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ;
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(199002)(189002)(15202345003)(69226001)(31966008)(51856001)(74502001)(47446002)(4396001)(74662001)(46102001)(83072001)(59766001)(47736001)(50986001)(47976001)(81686001)(49866001)(83322001)(19580395003)(65816001)(81816001)(15975445006)(80022001)(77982001)(80976001)(63696002)(79102001)(33646001)(66066001)(81542001)(81342001)(53806001)(74876001)(76482001)(54356001)(56816003)(77096001)(74316001)(74706001)(56776001)(54316002)(76176001)(76576001)(76786001)(76796001)(74366001)(85306001)(568214003)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB141; H:BY2PR05MB142.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en;
Received: from mail37-ch1 (localhost.localdomain [127.0.0.1]) by mail37-ch1 (MessageSwitch) id 1380738399743940_5684; Wed, 2 Oct 2013 18:26:39 +0000 (UTC)
Received: from CH1EHSMHS009.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.245]) by mail37-ch1.bigfish.com (Postfix) with ESMTP id A785940040 for <ccamp@ietf.org>; Wed, 2 Oct 2013 18:26:39 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by CH1EHSMHS009.bigfish.com (10.43.70.9) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 2 Oct 2013 18:26:39 +0000
Received: from BY2PR05MB141.namprd05.prod.outlook.com (10.242.39.148) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.359.1; Wed, 2 Oct 2013 18:26:37 +0000
Received: from BY2PR05MB142.namprd05.prod.outlook.com (10.242.39.144) by BY2PR05MB141.namprd05.prod.outlook.com (10.242.39.148) with Microsoft SMTP Server (TLS) id 15.0.775.9; Wed, 2 Oct 2013 18:26:35 +0000
Received: from BY2PR05MB142.namprd05.prod.outlook.com ([169.254.12.177]) by BY2PR05MB142.namprd05.prod.outlook.com ([169.254.12.177]) with mapi id 15.00.0775.005; Wed, 2 Oct 2013 18:26:35 +0000
From: John E Drake <jdrake@juniper.net>
To: "CCAMP (ccamp@ietf.org)" <ccamp@ietf.org>
Thread-Topic: Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Path Diversity using Exclude Routes
Thread-Index: Ac6/mpvpLKMUWgFOTvGxqewIiE5jbQ==
Date: Wed, 02 Oct 2013 18:26:34 +0000
Message-ID: <a7a636bf5b6942a8b74ebf2c71a3212f@BY2PR05MB142.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0987ACA2E2
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: [CCAMP] Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Path Diversity using Exclude Routes
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: Wed, 02 Oct 2013 18:32:10 -0000

HI,

I was reading:   http://datatracker.ietf.org/doc/draft-ietf-ccamp-lsp-diversity/?include_text=1, and I happened to notice the following paragraph:

"The means by which the node calculating or expanding the route of the signaled LSP discovers the route of the path(s) from which the signaled LSP
 requires diversity are beyond the scope of this document. "

Doesn't this disclaimer effectively render this draft useless?  The draft also does not define how the node that initially signaled the LSP finds the 'node calculating
or expanding the route'  nor how it delivers the signaled LSP request to that node.

As an aside, the draft:  http://datatracker.ietf.org/doc/draft-ali-ccamp-rsvp-te-include-route/?include_text=1 would be subject to the same criticism
except that the above quoted paragraph is replaced with:

"The above-mentioned use cases require relevant path inclusion requirements to be communicated to the route expanding nodes.  This document addresses
 these requirements and defines procedures to address them." 

Even though this is helpful, the draft doesn't actually define these procedures.

Yours Irrespectively,

John