IETF Logo Mail Archive

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

Loa Andersson <loa@pi.nu> Fri, 20 February 2015 13:31 UTC

Return-Path: <loa@pi.nu>
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 0600D1A888B for <teas@ietfa.amsl.com>; Fri, 20 Feb 2015 05:31:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 G5mhloBmaY-B for <teas@ietfa.amsl.com>; Fri, 20 Feb 2015 05:30:59 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB1DA1A8759 for <teas@ietf.org>; Fri, 20 Feb 2015 05:30:58 -0800 (PST)
Received: from [192.168.1.12] (unknown [49.149.157.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 9A01C1801127; Fri, 20 Feb 2015 14:30:55 +0100 (CET)
Message-ID: <54E73708.9080205@pi.nu>
Date: Fri, 20 Feb 2015 21:30:48 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>, "teas@ietf.org" <teas@ietf.org>
References: <D104E278.4F421%rgandhi@cisco.com> <54E3F440.9070500@labn.net>
In-Reply-To: <54E3F440.9070500@labn.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/biYSUaVygqMvE-ihSkRCWogtnSE>
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 13:31:01 -0000

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

v2.23.0 | Report a Bug | By Email