IETF Logo Mail Archive

[Teas] inclusion of references in protocol feature configuration configuration

Lou Berger <lberger@labn.net> Sat, 11 November 2017 03:06 UTC

Return-Path: <lberger@labn.net>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E7C0128D19 for <teas@ietfa.amsl.com>; Fri, 10 Nov 2017 19:06:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.158
X-Spam-Level:
X-Spam-Status: No, score=-3.158 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, 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 kkJT8v5efpK7 for <teas@ietfa.amsl.com>; Fri, 10 Nov 2017 19:06:48 -0800 (PST)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) (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 CF96B1270AE for <teas@ietf.org>; Fri, 10 Nov 2017 19:06:45 -0800 (PST)
Received: from CMOut01 (unknown [10.0.90.82]) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 712831E07D5 for <teas@ietf.org>; Fri, 10 Nov 2017 20:06:39 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by CMOut01 with id YT6b1w00V2SSUrH01T6exP; Fri, 10 Nov 2017 20:06:39 -0700
X-Authority-Analysis: v=2.2 cv=K4VSJ2eI c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=sC3jslCIGhcA:10 a=7j7fafPWaBm9ODk6CxMA:9 a=QEXdDO2ut3YA: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: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=TrFT+XNW79pa9skjrvACVqPqjpMRb/TeDCstzZkcqzw=; b=Ni7d+IWKxpTlfKS0oeuUUuDtuA pq7HbL6uN3odrbakszpA5nz+85IOuzSZx04nUUEeMoK6k5+GhAJ2bvDVps3omuCdVsBfYy0aR7ndY kotGuxjKZYxbMDfWYH2mFDOS/;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([100.15.86.101]:42640 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <lberger@labn.net>) id 1eDM7v-000Apr-AK; Fri, 10 Nov 2017 20:06:35 -0700
To: draft-ietf-teas-yang-rsvp-te@ietf.org, draft-ietf-teas-yang-rsvp@ietf.org, draft-ietf-teas-yang-te@ietf.org
Cc: teas@ietf.org
References: <150932270746.3426.3220773532456344196@ietfa.amsl.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <8de1c9eb-133a-14ea-f323-ef5502a12f07@labn.net>
Date: Fri, 10 Nov 2017 23:29:07 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <150932270746.3426.3220773532456344196@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
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: 100.15.86.101
X-Exim-ID: 1eDM7v-000Apr-AK
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-86-101.washdc.fios.verizon.net ([IPv6:::1]) [100.15.86.101]:42640
X-Source-Auth: lberger@labn.net
X-Email-Count: 8
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/LFOdwXTxgm-cfhov97TfQHcan80>
Subject: [Teas] inclusion of references in protocol feature configuration configuration
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 11 Nov 2017 03:06:49 -0000

Hi,
	In reviewing the the yang-te, rsvp and rsvp=te modules I noticed that 
references aren't included in most config groupings/nodes.  Given the 
number of RFCs used to define the mechanisms covered by these modules I 
think it's important to include a reference to the RFC that defines the 
feature/information element covered in the model. I suspect this 
comments is also applicable to other modules.

Thanks,
Lou

v2.23.0 | Report a Bug | By Email