Re: [Teas] use of the FEC term in draft-ietf-teas-lsp-diversity

Loa Andersson <loa@pi.nu> Fri, 17 April 2015 08:23 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 E7A4B1B2AD8; Fri, 17 Apr 2015 01:23:19 -0700 (PDT)
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 sU9EXQ_BPQZF; Fri, 17 Apr 2015 01:23:17 -0700 (PDT)
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 94CED1B2AD4; Fri, 17 Apr 2015 01:23:17 -0700 (PDT)
Received: from [192.168.0.100] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (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 503CD1801127; Fri, 17 Apr 2015 10:23:15 +0200 (CEST)
Message-ID: <5530C2EA.90809@pi.nu>
Date: Fri, 17 Apr 2015 10:23:06 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>, draft-ietf-teas-lsp-diversity@ietf.org
References: <55304D4A.9050604@labn.net>
In-Reply-To: <55304D4A.9050604@labn.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/VBhm36K4N5IQlQLi9-XvdaYXXbc>
Cc: TEAS WG <teas@ietf.org>
Subject: Re: [Teas] use of the FEC term in draft-ietf-teas-lsp-diversity
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, 17 Apr 2015 08:23:20 -0000

Lou,

On 2015-04-17 02:01, Lou Berger wrote:
> Authors/WG,
>      I'm a bit uncomfortable with the document's use of FEC in the
> context if RSVP-TE.
Yes, I share that concern, the FEC terminology originated in LDP
context, but have since developed developed.

> RFC3209's usage of FEC is very loose and rfc4379
> only gives an indirect definition in one context.  I think that either
> the draft should avoid the term or it should point to a to be written
> formal definition of the term in the context of RSVP-TE (including in
> its GMPLS form).

I've been looking for a while for that defintion, and as far as I can
there is no RSVP-TE message or object that actually carry a FEC. It has
been said the the FEC definition is "implicit", but I don't think that
is a solution, rather it is part of the problem.

I think that "avoid" would be easiest, but if the authors go for
defining a FEC in RSVP-TE context, I think that the consensus call for
such a definiton need to involve teas and mpls, but I think ccamp and 
pce should also be notified for the such a consesus call.

/Loa
>
> Thoughts?
>
> Lou (with any / all hats)
>
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64