[Supa] Fw: review for draft-ietf-supa-generic-policy-data-model-03

"Haining Wang" <18901341229@189.cn> Thu, 11 May 2017 05:43 UTC

Return-Path: <18901341229@189.cn>
X-Original-To: supa@ietfa.amsl.com
Delivered-To: supa@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01434128BC8 for <supa@ietfa.amsl.com>; Wed, 10 May 2017 22:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.55
X-Spam-Level: ****
X-Spam-Status: No, score=4.55 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FROM_LOCAL_DIGITS=0.001, FROM_LOCAL_HEX=0.006, HTML_MESSAGE=0.001, RCVD_IN_PSBL=2.7, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=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 Wdr9VoLMSqME for <supa@ietfa.amsl.com>; Wed, 10 May 2017 22:43:30 -0700 (PDT)
Received: from 189.cn (unknown [121.14.53.135]) by ietfa.amsl.com (Postfix) with ESMTP id BAAE11201F8 for <supa@ietf.org>; Wed, 10 May 2017 22:43:29 -0700 (PDT)
HMM_SOURCE_IP: 10.64.8.34:55255.43129327
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from clientip-219.142.69.75 (unknown [10.64.8.34]) by 189.cn (HERMES) with ESMTP id 85329374541 for <supa@ietf.org>; Thu, 11 May 2017 13:43:26 +0800 (CST)
Received: from ctbri-t440 ([219.142.69.75]) by zm-as4 with ESMTP id 0b68d593-99c1-4123-b3ab-232ae62c149a for supa@ietf.org; Thu May 11 13:43:26 2017
0/X-Total-Score: 0:
X-Real-From: 18901341229@189.cn
X-Receive-IP: 219.142.69.75
X-MEDUSA-Status: 0
Date: Thu, 11 May 2017 13:43:34 +0800
From: Haining Wang <18901341229@189.cn>
To: supa <supa@ietf.org>
X-Priority: 3
X-GUID: 470A7B29-2547-49F5-B692-F3742663B7E9
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 8, 378[cn]
Mime-Version: 1.0
Message-ID: <2017051113433386215911@189.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart774478681231_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/supa/rmmozkdOJks5zB2Co3uToIhP1hs>
Subject: [Supa] Fw: review for draft-ietf-supa-generic-policy-data-model-03
X-BeenThere: supa@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is to discuss SUPA \(Simplified Use of Policy Abstractions\) related issues." <supa.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/supa>, <mailto:supa-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/supa/>
List-Post: <mailto:supa@ietf.org>
List-Help: <mailto:supa-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/supa>, <mailto:supa-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 May 2017 07:20:00 -0000

Dear all,

It seems my previous email failed to be posted to the email list. So I change to another email to send it again. Hope this time it works.
Thanks!


Best regards
Haining Wang
China Telecom Beijing Research Institute


 
发件人: Haining Wang
发送时间: 2017-05-10 11:58
收件人: supa
主题: review for draft-ietf-supa-generic-policy-data-model-03
Dear all,
 
This is Haining from China Telecom. I was invited to review SUPA DM v3 on behalf of China Telecom as well as the vice chair of ETSI ENI.
 
First of all, this is a very detailed document to follow in guiding the use of policy. My feeling is it seems that the document is all good except that ECA Data Model is still missing in this version(or maybe I failed to find it, if yes, really sorry), although the Abstract and Introduction claim that “The second is an exemplary extension of the first generic policy model, and defines rules as event-condition-action-policies”.
 
I understand that the GPIM YANG model provides an example of how to convert IM to DM (for general policy), and John’s SNMP blocking example (https://mailarchive.ietf.org/arch/msg/supa/DWEzaSBK6KBdsmQ0FE2-eypTzeY) exposes some details. But I am sorry that the whole picture is still not clear to me. It would be nice if the ECA Data Model part can explain in more details.
 
I believe the ECA Data Model is critical for the adoption of SUPA in real systems, given that ECA is the most common policy we plan to use in real system. I suggest that this should be an important task for the SUPA team. Thanks.



Best regards
Haining Wang
China Telecom Beijing Research Institute