Re: [Nsaas] Need your to reply to this email FW: A ore accurate name....

Myo Zarny <myo.zarny@gmail.com> Mon, 15 September 2014 01:35 UTC

Return-Path: <myo.zarny@gmail.com>
X-Original-To: nsaas@ietfa.amsl.com
Delivered-To: nsaas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72AA81A047C for <nsaas@ietfa.amsl.com>; Sun, 14 Sep 2014 18:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 7rPwm7Cgz8NC for <nsaas@ietfa.amsl.com>; Sun, 14 Sep 2014 18:35:45 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 973F41A0476 for <nsaas@ietf.org>; Sun, 14 Sep 2014 18:35:45 -0700 (PDT)
Received: by mail-ig0-f171.google.com with SMTP id r10so3178347igi.10 for <nsaas@ietf.org>; Sun, 14 Sep 2014 18:35:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8+Tl431F7npOVOhCRdIUwtDQTx31ApLxLz3TKR3WIls=; b=CugIkR+VPt0nqGGTJ5Y0Bx2RRmSLZ+Nj9wyAXPjvIj4OncvznYnrystEmdO/lNorJB wONxwZTbxdmGNJyx6w4JIiDT4pBXRxYEY6EvVfmYGPuoO/qRz+4sSyij0GP/ojzd/tef vnTKjAp7wXTSsQVB8bDplOQlvyJNzxOhBoaxH7OWC/TX5iSvBk4WE24uLg9rJuE1jvnT 6QYtv5MdOvJCyDtEi1m2OK8Usszqff4OAHBl1R/Dd53pFZQtxOnQ/0PmcAsYzZxLPIAD D7/GAofWVbOYjTh9fFXTkPx6Kw+W8mOrE3JbuaD3ESM3ds0A/yPmjc7wbWDMoFJ05+Lw PRGQ==
MIME-Version: 1.0
X-Received: by 10.42.84.9 with SMTP id j9mr266307icl.60.1410744445212; Sun, 14 Sep 2014 18:27:25 -0700 (PDT)
Received: by 10.107.17.205 with HTTP; Sun, 14 Sep 2014 18:27:25 -0700 (PDT)
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645DECABE@dfweml701-chm>
References: <4A95BA014132FF49AE685FAB4B9F17F645DECABE@dfweml701-chm>
Date: Sun, 14 Sep 2014 21:27:25 -0400
Message-ID: <CAFzRpbw-xn+COrqc0Kfmmh++MCJiX10gY9oSpWVi2K54dNLwLQ@mail.gmail.com>
From: Myo Zarny <myo.zarny@gmail.com>
To: brford@cisco.com, nsaas@ietf.org
Content-Type: multipart/alternative; boundary="90e6ba614d48869f7f0503108998"
Archived-At: http://mailarchive.ietf.org/arch/msg/nsaas/No00RMMzcBVztZLe67HzXzryVvM
X-Mailman-Approved-At: Mon, 15 Sep 2014 05:24:25 -0700
Cc: "Zarny, Myo" <Myo.Zarny@gs.com>, Linda Dunbar <linda.dunbar@huawei.com>
Subject: Re: [Nsaas] Need your to reply to this email FW: A ore accurate name....
X-BeenThere: nsaas@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "*NSaaS: Network Security as a Service mailing list*" <nsaas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nsaas>, <mailto:nsaas-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nsaas/>
List-Post: <mailto:nsaas@ietf.org>
List-Help: <mailto:nsaas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nsaas>, <mailto:nsaas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 02:54:55 -0000

Hi Brian,

I agree that the scopes of SACM and NSaaS aren't the same even though there
is overlap. NSaaS is broader. Its domain/scope is more than just endpoints,
consistent APIs, communication protocols between endpoints and
network-based security services. It's all that plus--as you've pointed
out--how security policies are translated and provisioned on the
"southbound" side--regardless of their form-factor (hardware, software,
hypervisor-based, container-based). And so on.

The challenge is in determining which ones should be prioritized. To me, as
a user (not a vendor) of services, being able to dynamically reserve
network (security) services and have appropriate (security) policies
dynamically applied is the holy grail. (Especially if those policies can be
defined in user friendly terms and the system be smart enough to translate
them.) The question is how do we define and prioritize the steps towards
achieving them.

Regards,



>  *From:* Nsaas [mailto:nsaas-bounces@ietf.org <nsaas-bounces@ietf.org>] *On
> Behalf Of *Brian Ford (brford)
> *Sent:* Wednesday, September 10, 2014 7:10 PM
> *To:* nsaas@ietf.org
> *Subject:* [Nsaas] A ore accurate name....
>
>
>
>
>
> Linda,
>
>
>
> IMO someone can make the argument that just about any acronym is like a
> ‘Marketing program’.  Changing the name of the pre-WG effort for that
> reason alone doesn’t seem wise ego me.  Changing it from something …’was’
> to include ‘Open’ doesn’t seem like a big win.
>
>
>
> When I first read your messages about Network Security as a Service I was
> interested.  I still am even though I know little more than the name.
>
>
>
> I have been watching and involved in SACM, Security Automation and
> Continuous Monitoring.  One of my concerns that I have about SACM are its
> almost myopic endpoint focus.  I’m particularly interested in NSaaS because
> it could or might address the application of security policy in networks
> that protect all devices be they endpoints or VMs or intelligent lightbulbs
> in an IoT (or IoE).
>
>
>
> I see ‘daylight’ between SACM and NSaaS.  But they could help each other.
>  Let’s start working on the real problem.
>
>
>
> Liberty,
>
>
>
> Brian
>
>
>
>
>
>  Via the offline discussion with Melinda, I learned that many people may
> think that NSaaS is more like Marketing slogan.
>
>
>
> Since the goal is to define a common interface for network security
> functions (like what I2RS has done for routers), so that Service Providers
> or 3rd party operators can offer Network Security Functions that may not
> physically present in the client premises.
>
>
>
> Is  "I2NSF" (Open Interface to Network Security functions) a more
> appropriate name? Any more suggestions?
>
>
>
> Linda
>
>
>
>  --
>
>   *Brian Ford | OCTAO | **brford@cisco.com* <:brford@cisco.com>* | Direct*
>  *212.714.4288 <212.714.4288> | Mobile: 516.769.5884 <516.769.5884> |
> twitter.com/ccie2106 <http://twitter.com/ccie2106>*
>



-- 
Regards,
Myo