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

Lou Berger <lberger@labn.net> Fri, 17 April 2015 09:48 UTC

Return-Path: <lberger@labn.net>
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 4C8B71AD0BC for <teas@ietfa.amsl.com>; Fri, 17 Apr 2015 02:48:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level:
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
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 AxO22AiTFlk3 for <teas@ietfa.amsl.com>; Fri, 17 Apr 2015 02:48:57 -0700 (PDT)
Received: from gproxy9-pub.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) by ietfa.amsl.com (Postfix) with SMTP id 21CAB1AD0AA for <teas@ietf.org>; Fri, 17 Apr 2015 02:48:49 -0700 (PDT)
Received: (qmail 14048 invoked by uid 0); 17 Apr 2015 09:48:48 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy9.mail.unifiedlayer.com with SMTP; 17 Apr 2015 09:48:48 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id Gxod1q0062SSUrH01xogpE; Fri, 17 Apr 2015 03:48:46 -0600
X-Authority-Analysis: v=2.1 cv=QKX7GG7L c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=gaoa-Wm5cTEA:10 a=kj9zAlcOel0A:10 a=wU2YTnxGAAAA:8 a=-NfooI8aBGcA:10 a=AqI0xvK1tnMA:10 a=e9J7MTPGsLIA:10 a=48vgC7mUAAAA:8 a=i0EeH86SAAAA:8 a=_DPyRagTQV-TBVbyZJUA:9 a=CjuIK1q_8ugA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject:References:In-Reply-To:Message-ID:Date:CC:To:From; bh=xBqGdq+yEjLtL6EHE7MK7vCccbInp2seD9bZxSQVlww=; b=hVI9BjRVOuNOHmR/9LJO6tDRUs18U2QiJGUcIXP39xT2Huiiv7+xB4yexVFMsxDeO4RKgdt06DEaQSmTTw9I5YveBCBTmOIgsaDLGoaFGa+VtzNVxn0VXODAGFpN+2Bt;
Received: from [74.96.190.213] (port=52002 helo=[11.4.0.117]) by box313.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82) (envelope-from <lberger@labn.net>) id 1Yj2t5-00005Q-2v; Fri, 17 Apr 2015 03:48:39 -0600
From: Lou Berger <lberger@labn.net>
To: Loa Andersson <loa@pi.nu>, draft-ietf-teas-lsp-diversity@ietf.org
Date: Fri, 17 Apr 2015 05:48:38 -0400
Message-ID: <14cc6c7a538.27e9.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <5530C2EA.90809@pi.nu>
References: <55304D4A.9050604@labn.net> <5530C2EA.90809@pi.nu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 AquaMail/1.5.5.19 (build: 21050019)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 74.96.190.213 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/3iPO2QbISyKW-S4wpagHxtyhT0Q>
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 09:48:58 -0000

Hi Loa,


On April 17, 2015 4:23:52 AM Loa Andersson <loa@pi.nu> wrote:

> 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,

This seems to be what Zafar was proposing.

> 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.
>

I completely agree. I also think this must be in its own document.

Lou
> /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
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>