IETF Logo Mail Archive

Re: [Teas] A clarification request for draft-ietf-teas-mpls-tp-rsvpte-ext-associated-lsp

"Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com> Fri, 20 February 2015 15:39 UTC

Return-Path: <rgandhi@cisco.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC0B1A87AD for <teas@ietfa.amsl.com>; Fri, 20 Feb 2015 07:39:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 2VGKr_XeEOoL for <teas@ietfa.amsl.com>; Fri, 20 Feb 2015 07:39:48 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 776FC1A87AB for <teas@ietf.org>; Fri, 20 Feb 2015 07:39:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1018; q=dns/txt; s=iport; t=1424446789; x=1425656389; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=Et8FoCIiurGtGfZ89hJMsryy78W2C9DXiFkVn6mqhMw=; b=L4mEOFMj1IzoCK16CDCQXS5WJql01RTYsjeONTuboFJUXWeFP0TbHzcQ lkU3I92m0FHkPV6TXpHMfDAfDt/yIHDSkV3LcgF7LmtK+M12RWMRP+/Z7 xRSZXeME8L64kErxDn827KkwcxK86joRon5RP58qP+nuzU+wAlj607jG+ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CVBQB5VOdU/4sNJK1bgwZSWgTCZgqFcQKBGEMBAQEBAQF8hBABAQQBAQE3MQMZBAEIGB4rDAslAgQBEogvDdRgAQEBAQEBAQECAQEBAQEBAQEWBASLC4QMEQFXhCoFj06JQZMrIoIygTxvgQs5fwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,615,1418083200"; d="scan'208";a="125442616"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-6.cisco.com with ESMTP; 20 Feb 2015 15:39:48 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t1KFdlZp017495 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 20 Feb 2015 15:39:47 GMT
Received: from xmb-aln-x07.cisco.com ([169.254.2.221]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Fri, 20 Feb 2015 09:39:47 -0600
From: "Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com>
To: Loa Andersson <loa@pi.nu>, Lou Berger <lberger@labn.net>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] A clarification request for draft-ietf-teas-mpls-tp-rsvpte-ext-associated-lsp
Thread-Index: AQHQSHS1IlNxC6WSUE6zKODZmDhq1pz2E2gAgAPjIwD//9A0AA==
Date: Fri, 20 Feb 2015 15:39:47 +0000
Message-ID: <D10CBD7B.504F7%rgandhi@cisco.com>
In-Reply-To: <54E73708.9080205@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [161.44.212.199]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AB37BA87401C4D4081C6A8D5EE544ECC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/0Qk-pmOyFpilSRzLa_bJJ8wUsF4>
Subject: Re: [Teas] A clarification request for draft-ietf-teas-mpls-tp-rsvpte-ext-associated-lsp
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 15:39:50 -0000

Hi Loa,

This is for the associated bidirectional LSPs when using single sided
provisioning. 
Specially, when the initiating node is inserting the ASSOCIATION Object
with Association Type "Single Sided Associated Bidirectional LSP" to
trigger creation of reverse LSP on the egress node.

Thanks,
Rakesh


On 2015-02-20 8:30 AM, "Loa Andersson" <loa@pi.nu> wrote:

>Lou,
>
>There are lots of "forward LSPs" out there, what is the criteria more
>in detail where the REVERSE_LSP Object will be required if we choose
>option 1?
>
>/Loa
>
>On 2015-02-18 10:09, Lou Berger wrote:
>> Some options:
>> a) Always require a  REVERSE_LSP Object in the forward LSP
>
>-- 
>
>
>Loa Andersson                        email: loa@mail01.huawei.com
>Senior MPLS Expert                          loa@pi.nu
>Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
>_______________________________________________
>Teas mailing list
>Teas@ietf.org
>https://www.ietf.org/mailman/listinfo/teas

v2.23.0 | Report a Bug | By Email