IETF Logo Mail Archive

Re: [Supa] SUPA success

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 16 December 2016 17:32 UTC

Return-Path: <jmh@joelhalpern.com>
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 5F3581279EB for <supa@ietfa.amsl.com>; Fri, 16 Dec 2016 09:32:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level:
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 wdZCuwzQRhK5 for <supa@ietfa.amsl.com>; Fri, 16 Dec 2016 09:32:55 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 06D4A1294B6 for <supa@ietf.org>; Fri, 16 Dec 2016 09:32:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id E56152686BD; Fri, 16 Dec 2016 09:32:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1481909574; bh=uH5uT6aUCusCsbDJAEViIRO3FUovOEWD4fwJSDwm1C8=; h=Subject:To:References:From:Date:In-Reply-To:From; b=GA7LyPZHOoU9KF2OuTrzjHGKBRNa7APoCgLOclgNn6OXeM/s1nj0pCVdeSq87Z9aQ vraw/GCqrObFq9T8ApfP63MSQvFyEiQQGjR+vzUigiWwhDI1ZVhjUkRrBm3rISztFu COtaVO7NIt3t8DTSUrNVGM0uJcQhlzvATTy65Hmk=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id BF66D241553; Fri, 16 Dec 2016 09:32:53 -0800 (PST)
To: Benoit Claise <bclaise@cisco.com>, "supa@ietf.org" <supa@ietf.org>
References: <94be5dc4-350f-c32b-9de7-04fa60bf5551@cisco.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <6ed59f4e-48da-8747-5fd5-dc290a0cec62@joelhalpern.com>
Date: Fri, 16 Dec 2016 12:32:50 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <94be5dc4-350f-c32b-9de7-04fa60bf5551@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/supa/Z7ODsWoZp-yePMXJqhZa2MsSFMU>
Subject: Re: [Supa] SUPA success
X-BeenThere: supa@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 16 Dec 2016 17:32:56 -0000

While your statement is true, it seems a bit odd.  Since we have not yet 
add the ECA data model elements to the SUPA DM, it would have been a bit 
hard for anyone to use it up till now.
Even when we add such, I expect people will want some indication from 
the WG that it is stable before they will use it.  (And I as xo-author 
can not ask for any such indication until we have given the WG the YANG, 
and gien enough examples for folks to see how it works.)

Yours,
Joel



On 12/16/16 10:23 AM, Benoit Claise wrote:
> Dear all,
>
> As I mentioned a few times, reading the charter: "The working group will
> have succeeded when the SUPA policy constructs are re-used in future
> IETF specifications (and ideally specifications from other SDOs)"
>
> During the IETF hackathon, Joe Clark developed a YANG impact analysis tool.
> So we have
> http://yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-supa-policy&recurse=0&rfcs=1,
> which is a good metric for the SUP success. Conclusion so far (which is
> fine at this point in time, but we should focus on this): the
> ietf-supa-policy is not yet reused.
>
> Regards, Benoit
>
>
>
> _______________________________________________
> Supa mailing list
> Supa@ietf.org
> https://www.ietf.org/mailman/listinfo/supa
>

v2.23.0 | Report a Bug | By Email