Re: [CCAMP] Question on LSP control in draft-ietf-ccamp-mpls-tp-rsvpte-ext-associated-lsp-04.txt

Lou Berger <lberger@labn.net> Tue, 04 September 2012 15:35 UTC

Return-Path: <lberger@labn.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 EE8A021F8674 for <ccamp@ietfa.amsl.com>; Tue, 4 Sep 2012 08:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.161
X-Spam-Level:
X-Spam-Status: No, score=-100.161 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YglxLYwaAJat for <ccamp@ietfa.amsl.com>; Tue, 4 Sep 2012 08:35:29 -0700 (PDT)
Received: from oproxy11-pub.bluehost.com (unknown [IPv6:2605:dc00:100:2::a3]) by ietfa.amsl.com (Postfix) with SMTP id 61D1821F8569 for <ccamp@ietf.org>; Tue, 4 Sep 2012 08:35:26 -0700 (PDT)
Received: (qmail 21457 invoked by uid 0); 4 Sep 2012 15:35:13 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy11.bluehost.com with SMTP; 4 Sep 2012 15:35:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=Bqkn6miuomHLhsF5bIMrMUAQU0lsJ+Aeiu+h7Ru5qtQ=; b=uZVKVWdPF7DxAFtDvQ1MNqaz004G6CtxZ8O7FjHUszX0fEP3MVmPju7mDqe38eKe8KQM5brFJMgh3guG9IwrNkakfb35HcId6jhzTTVXjHpk9LU9q8sxpsI7Q+fbGYXf;
Received: from box313.bluehost.com ([69.89.31.113]:33104 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1T8v9k-0006vL-Ot; Tue, 04 Sep 2012 09:35:12 -0600
Message-ID: <50461FB2.7080707@labn.net>
Date: Tue, 04 Sep 2012 11:35:14 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: "Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com>
References: <B7D2A316AA32B6469D9670B6A81B7C24075DFC@xmb-aln-x07.cisco.com>
In-Reply-To: <B7D2A316AA32B6469D9670B6A81B7C24075DFC@xmb-aln-x07.cisco.com>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Re: [CCAMP] Question on LSP control in draft-ietf-ccamp-mpls-tp-rsvpte-ext-associated-lsp-04.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: Tue, 04 Sep 2012 15:35:31 -0000

As I read the current rev, no such notification mechanism is specified.
 Looks like you get to propose one!

Lou (as WG participant).

On 8/31/2012 9:49 AM, Rakesh Gandhi (rgandhi) wrote:
> Hi Lou, Fei,
> 
> When an (originating) ingress node is provisioned with "5 (TBD)  Single Sided Associated Bidirectional LSPs  (A)" and wishes to control both forward and reverse  LSPs by adding "REVERSE_LSP" object, I would think that the ingress node needs to know about the signaling (path) errors (such as soft preemption or admission failure) on the reverse LSP.  Is there any text somewhere in an RFC/draft that describes how a mid-point node can send the signaling (path) error to the originating ingress node for the reverse LSP? Is there an assumption to use RSVP_NOTIFY message? Sorry if I had missed any previous discussion on this topic.
> 
> Thanks,
> Rakesh
> 
> 
> 
> 
>