Re: [RTG-DIR] defining signaling parameters for GMPLS

Lou Berger <lberger@labn.net> Wed, 02 January 2019 12:02 UTC

Return-Path: <lberger@labn.net>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3169E1276D0 for <rtgwg@ietfa.amsl.com>; Wed, 2 Jan 2019 04:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 QK2scC2GWetT for <rtgwg@ietfa.amsl.com>; Wed, 2 Jan 2019 04:02:20 -0800 (PST)
Received: from gproxy1-pub.mail.unifiedlayer.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E5CD12D4E9 for <rtgwg@ietf.org>; Wed, 2 Jan 2019 04:02:20 -0800 (PST)
Received: from cmgw11.unifiedlayer.com (unknown [10.9.0.11]) by gproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id D43356239A4C9 for <rtgwg@ietf.org>; Wed, 2 Jan 2019 04:51:05 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id ef3BgqHY6qZYcef3BgwkTd; Wed, 02 Jan 2019 04:51:05 -0700
X-Authority-Reason: nr=8
X-Authority-Analysis: $(_cmae_reason
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:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=C9Mvv/zLsDO9MZC4kIaTo3KTBXO268K4T0Gdzj/NYQ0=; b=pWSQExhOy0HrQe9a3xYbAJG8QI WBNXk73NMBd0bDRAJDtIO/FecjI6Ne9+7lOcV9Bt8WLbkwyRUxuKDbxSFRyGkp2/EoxXjqTVh+y3R eeJVRHFxtG0jsyGisaD8kD3sU;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:32956 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1gef3B-001p0Q-Er; Wed, 02 Jan 2019 04:51:05 -0700
Subject: Re: [RTG-DIR] defining signaling parameters for GMPLS
To: tom petch <ietfa@btconnect.com>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>
Cc: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, LSR WG Chairs <lsr-chairs@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE292563246@dggeml510-mbx.china.huawei.com> <30620f3f-be62-bdbd-72fb-fab27439351b@cisco.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE292566105@dggeml510-mbx.china.huawei.com> <037301d42a4d$aa9dbe60$4001a8c0@gateway.2wire.net> <1e7f439a-b050-0ab2-bce3-9b91e2926b22@cisco.com> <017f01d42b08$850ad780$4001a8c0@gateway.2wire.net> <d0e9e7f5-2a43-4ac1-b921-22a8d8ac3825@cisco.com> <006a01d4a284$c5b8ea80$4001a8c0@gateway.2wire.net>
From: Lou Berger <lberger@labn.net>
Message-ID: <222061ca-c721-5f35-ea85-b5c0a34ccfcc@labn.net>
Date: Wed, 2 Jan 2019 06:51:04 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1
MIME-Version: 1.0
In-Reply-To: <006a01d4a284$c5b8ea80$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1gef3B-001p0Q-Er
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net ([IPv6:::1]) [72.66.11.201]:32956
X-Source-Auth: lberger@labn.net
X-Email-Count: 4
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/9-oQY9VViuC52QPe7R3HMWCt0QQ>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2019 12:02:22 -0000

Tom,

Good catch!

I'll talk this over with the various co chairs and come back with a 
suggestion on how to reconcile the LSR and TEAS drafts.

Lou

(TEAS Co-chair)

On 1/2/2019 5:20 AM, tom petch wrote:
> The TEAS WG is producing a te-types I-D which contains definitions, in
> YANG form, for many of the signaling parameters used by GMPLS.
>
> Meanwhile, the LSR WG has a need to defind the signaling parameters used
> for TE and so has created its own definitions thereof.
>
> There is an expired I2RS I-D with similar definitions.
>
> Perhaps, in future, the MPLS or CCAMP WG will also find a need to define
> these parameters and create their own definitions.
>
> Meanwhile, these parameters have, for over 15 years, been registered
> with IANA.
>
> Defining things good, defining things in standards multiple times, not
> so good.
>
> I think there is a need for these parameters, some, although perhaps not
> all, of
>
> http://www.iana.org/assignments/gmpls-sig-parameters/gmpls-sig-parameter
> s.xhtml#gmpls-sig-parameters-3
>
> to be turned into a YANG module for all WG to use.  Such an exercise has
> been successfully carried out by the NETMOD WG for interface definitions
> (RFC7224).
>
> Tom Petch
>