Re: [Spud] Interactions between SPUD and I2NSF

"Black, David" <david.black@emc.com> Wed, 11 February 2015 00:13 UTC

Return-Path: <david.black@emc.com>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8885F1A1B11 for <spud@ietfa.amsl.com>; Tue, 10 Feb 2015 16:13:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 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_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 LyliTONzA5k1 for <spud@ietfa.amsl.com>; Tue, 10 Feb 2015 16:13:50 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D162E1A1BA5 for <spud@ietf.org>; Tue, 10 Feb 2015 16:13:28 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t1B0DQSI002333 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2015 19:13:26 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com t1B0DQSI002333
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1423613607; bh=4F1NHiXkrwzdZRRbwCa5njAihww=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=eTOffPjNiMHd6SCVKDyhLaiVhCrbdAqPxRK0FPq6Tn3v2uv6k8nmAkH2BBzyO9ffM 0WFjXO8TENkGrSZStdU827XPGvgnFYG5mmTrFhyPVlcuJzRgyGAUOjuyRnoOYPTZ7a dW5GqxpuHPSoNam2TFR9FAwQrZnuXmPmRb3hwQJk=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com t1B0DQSI002333
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd04.lss.emc.com (RSA Interceptor); Tue, 10 Feb 2015 19:13:12 -0500
Received: from mxhub28.corp.emc.com (mxhub28.corp.emc.com [10.254.110.184]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id t1B0DEsN005856 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Feb 2015 19:13:14 -0500
Received: from MXHUB208.corp.emc.com (10.253.68.34) by mxhub28.corp.emc.com (10.254.110.184) with Microsoft SMTP Server (TLS) id 8.3.327.1; Tue, 10 Feb 2015 19:13:14 -0500
Received: from MX104CL02.corp.emc.com ([169.254.8.236]) by MXHUB208.corp.emc.com ([10.253.68.34]) with mapi id 14.03.0195.001; Tue, 10 Feb 2015 19:13:13 -0500
From: "Black, David" <david.black@emc.com>
To: "Philipp S. Schmidt" <phils@in-panik.de>, "spud@ietf.org" <spud@ietf.org>
Thread-Topic: [Spud] Interactions between SPUD and I2NSF
Thread-Index: AQHQRU4CzEpRshcNjEO5dhukE9/BC5zqkn4A
Date: Wed, 11 Feb 2015 00:13:13 +0000
Message-ID: <CE03DB3D7B45C245BCA0D24327794936362C50@MX104CL02.corp.emc.com>
References: <A8E35FF3-A4E6-43CE-BE3C-BD968967081A@in-panik.de>
In-Reply-To: <A8E35FF3-A4E6-43CE-BE3C-BD968967081A@in-panik.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.238.44.129]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/9MkcpXxjcKETMPJTtviIiJ0KPj8>
Subject: Re: [Spud] Interactions between SPUD and I2NSF
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Feb 2015 00:13:55 -0000

Philipp,

> as a response to our position paper at IAB SEMI workshop, I was asked to
> comment on the not-yet-chartered I2NSF WG (Interface to Network Security
> Functions).
>
> I see a lot of overlap between the "service layer" defined in [draft-dunbar-
> i2nsf-problem-statement], but I am a little shaken between have an “joint
> approach” the complexity the whole framing of I2NSF implies.

What sort of "joint approach" is involved?

My reason for asking is that the proposed I2NSF charter: 
	http://www.ietf.org/mail-archive/web/i2nsf/current/msg00245.html

contains this clear sentence:

	It is a non-goal to create new protocols or data modeling languages for I2NSF interfaces.

Obviously, I2NSF is concerned with firewalls, and punching pinholes in at least
firewalls and NATs are things that SPUD needs to be concerned about, but is
there more?

At the other extreme, the design of SPUD should not touch the I2NSF service layer,
again quoting from the I2NSF draft charter:

	The Security Service and Policy Layer is for clients to express and monitor
		security policies for their specific flows.

We should leave that sort of security to the security experts, and hope that they
leave transport to the transport experts ;-).

And if anyone from the IESG is lurking on this list, here's one more example of
why Areas matter to the structure of the IETF.

Thanks,
--David


> -----Original Message-----
> From: Spud [mailto:spud-bounces@ietf.org] On Behalf Of Philipp S. Schmidt
> Sent: Tuesday, February 10, 2015 11:23 AM
> To: spud@ietf.org
> Subject: [Spud] Interactions between SPUD and I2NSF
> 
> Hi,
> 
> as a response to our position paper at IAB SEMI workshop, I was aksed to
> comment on the not-yet-cartered I2NSF WG (Interface to Network Security
> Functions).
> 
> I see a lot of overlap between the "service layer" defined in [draft-dunbar-
> i2nsf-problem-statement], but I am a little shaken between have an “joint
> approach” the complexity the whole frameing of I2NSF implies.
> 
> AVE!
>   Philipp S. Schmidt / phils…
> --
>    {phils}--->---(phils@in-panik.de)--->---(http://phils.in-panik.de)----,
>       wenn w eine   aube ist dn      man au dran dre en                   |
>            o     Schr        an muss     hc         h   (Kurt Schwitters) |
> :wq!  <---(phone: +49-179-6737439)---<---(jabber: phils@jabber.ccc.de)---'
> 
> _______________________________________________
> Spud mailing list
> Spud@ietf.org
> https://www.ietf.org/mailman/listinfo/spud