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

Leeyoung <leeyoung@huawei.com> Wed, 11 February 2015 20:04 UTC

Return-Path: <leeyoung@huawei.com>
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 241A31A904F; Wed, 11 Feb 2015 12:04:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.211
X-Spam-Level:
X-Spam-Status: No, score=-3.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 77bd2MX-cviw; Wed, 11 Feb 2015 12:04:35 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CB3C1A904D; Wed, 11 Feb 2015 12:04:34 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPE40512; Wed, 11 Feb 2015 20:04:32 +0000 (GMT)
Received: from DFWEML701-CHM.china.huawei.com (10.193.5.50) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 11 Feb 2015 20:04:31 +0000
Received: from DFWEML706-CHM.china.huawei.com ([10.193.5.225]) by dfweml701-chm ([10.193.5.50]) with mapi id 14.03.0158.001; Wed, 11 Feb 2015 12:04:20 -0800
From: Leeyoung <leeyoung@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "draft-ietf-ccamp-gmpls-general-constraints-ospf-te.all@tools.ietf.org" <draft-ietf-ccamp-gmpls-general-constraints-ospf-te.all@tools.ietf.org>
Thread-Topic: [CCAMP] AD review of draft-ietf-ccamp-gmpls-general-constraints-ospf-te
Thread-Index: AdBF+iy7+IEXXswS1kuaJyYtd/AcTwAO1S4Q
Date: Wed, 11 Feb 2015 20:04:19 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729C82197@dfweml706-chm>
References: <000301d045fa$3825b440$a8711cc0$@olddog.co.uk>
In-Reply-To: <000301d045fa$3825b440$a8711cc0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.134.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/ccamp/p4iEWoatDC9SYNB5uhJY9P34smw>
Cc: 'Alvaro Retana' <aretana@cisco.com>, "ccamp@ietf.org" <ccamp@ietf.org>, "teas@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
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 20:04:40 -0000

Thanks, Adrian for the suggested text. A new revision has been published. 

http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-general-constraints-ospf-te-09.txt


Best Regards,
Young

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk] 
Sent: Wednesday, February 11, 2015 6:57 AM
To: Leeyoung; draft-ietf-ccamp-gmpls-general-constraints-ospf-te.all@tools.ietf.org
Cc: 'Alvaro Retana'; ccamp@ietf.org; teas@ietf.org
Subject: RE: [CCAMP] AD review of draft-ietf-ccamp-gmpls-general-constraints-ospf-te

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