Re: [CCAMP] AD review of draft-ietf-ccamp-gmpls-general-constraints-ospf-te

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 11 February 2015 12:57 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 057461A8880; Wed, 11 Feb 2015 04:57:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.13
X-Spam-Level:
X-Spam-Status: No, score=-101.13 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77, USER_IN_WHITELIST=-100] 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 YF8g6gWxndya; Wed, 11 Feb 2015 04:57:07 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C076D1A887F; Wed, 11 Feb 2015 04:57:06 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id t1BCuwC4021133; Wed, 11 Feb 2015 12:56:58 GMT
Received: from 950129200 ([147.67.241.226]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id t1BCutnD021079 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 11 Feb 2015 12:56:56 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Leeyoung' <leeyoung@huawei.com>, draft-ietf-ccamp-gmpls-general-constraints-ospf-te.all@tools.ietf.org
Date: Wed, 11 Feb 2015 12:56:55 -0000
Message-ID: <000301d045fa$3825b440$a8711cc0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdBF+iy7+itT2GtwSc+MN94bqSs6Pw==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21320.006
X-TM-AS-Result: No--9.034-10.0-31-10
X-imss-scan-details: No--9.034-10.0-31-10
X-TMASE-MatchedRID: eVEkOcJu0F6nykMun0J1wtxajlW+zwxCVBDQSDMig9GqvcIF1TcLYFgr WOXzimgDQx95p3GYmc9UzHKDYQI4SI434Zqk7ja9Td1FGyH+HrIK3n1SHen81Vmmz7LVVfOpAvK 0O9Xf2H7qWMmhHFbtNb90Of+HRie+CaIwzQMUe5Kgx+na8dyT1SaXATIpQghoMKZRiezcUtPyF+ ujaIaPa+yCSv4LlfqpDvg2AyPRTe8B5kjkFVgUE37sp//jQ2LSZrbWdT9vCrwP5UNwUjScFCi1J mRhPGAWWrrOcmvP4NWH2VU8O9Ll7oKJRpKTDwLfDq5QZEGvahZeQC0fSIJk7K/FMdJb10vOJZXS peDM6Eqtjii34xRt/xLm2GUHz1pbTX7PJ/OU3vL+xOhjarOnHt0H8LFZNFG7hqz53n/yPno0LYR /5x137q9+cK3Qj/3qnG/3QN3RT3EXw0pBEUkdgboOfFLgUu3n
Archived-At: <http://mailarchive.ietf.org/arch/msg/ccamp/zPwU6b-4Ymdk-U-Wp0_wGnO6l-c>
Cc: 'Alvaro Retana' <aretana@cisco.com>, ccamp@ietf.org, teas@ietf.org
Subject: Re: [CCAMP] AD review of draft-ietf-ccamp-gmpls-general-constraints-ospf-te
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 12:57:09 -0000

Thanks Young,

Just the last point to be covered...

> Did you consider including a short manageability section?
> 
> YOUNG>> No, as you see the content. Do you have any suggestion in mind?
> 
> Are there any existing management tools that are impacted by the new
> sub-TLVs?
> 
> YOUNG>> I don't think so.
> 
> What might a user expect to configure related to these sub-TLVs?
> 
> What might a user expect to be able to read from a device?
> 
> YOUNG>> These questions sound like either a mib or yang question. I think the
> TLVs defined in this document can be configured/read by EMS or NMS or other
> system.
> Shall a companion document (mib or yang, which by the way I am working on
> WSON Yang model on these TLVs included) if you will address these questions?

So perhaps something like...

x. Manageability Considerations

   No existing management tools handle the additional TE parameters as
   defined in this document and distributed in OSPF-TE.  The existing 
   MIB module contained in [RFC6825] allows the TE information 
   distributed by OSPF-TE to be read from a network node: this MIB 
   module could be augmented (possibly by a sparse augmentation) to
   report this new information.

   The current environment in the IETF favors NETCONF [RFC6241] and YANG
   [RFC6020] over SNMP and MIB modules.  Work is in progress in the TEAS
   working group to develop a YANG module to represent the generic TE 
   information that may be present in a Traffic Engineering Database 
   (TED).  This model may be extended to handle the additional 
   information described in this document to allow that information to 
   be read from network devices or exchanged between consumers of the
   TED.  Furthermore, links state export using BGP (BGP-LS) [draft-ietf-
   idr-ls-distribution] enables the export of TE information from a 
   network using BGP.  Work could realistically be done to extend BGP-LS
   to also carry the information defined in this document.

   It is not envisaged that the extensions defined in this document will
   place substantial additional requirements on Operations, Management,
   and Administration (OAM) mechanisms currently used to diagnose and 
   debug OSPF systems.  However, tools that examine the contents of
   opaque LSAs will need to be enhanced to handle these new sub-TLVs.


Edit this to read the way you want it to, and post a revision.

Thanks,
Adrian