[smartpowerdir] Draft for PAP 1

Fred Baker <fred@cisco.com> Sat, 12 June 2010 19:39 UTC

Return-Path: <fred@cisco.com>
X-Original-To: smartpowerdir@core3.amsl.com
Delivered-To: smartpowerdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DEA773A6917 for <smartpowerdir@core3.amsl.com>; Sat, 12 Jun 2010 12:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.999
X-Spam-Level:
X-Spam-Status: No, score=-107.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-iuDUhqzDYn for <smartpowerdir@core3.amsl.com>; Sat, 12 Jun 2010 12:39:41 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 8D5423A67F2 for <smartpowerdir@ietf.org>; Sat, 12 Jun 2010 12:39:41 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAG5/E0yrR7H+/2dsb2JhbACfAnGkY5kshRoEg00
X-IronPort-AV: E=Sophos;i="4.53,408,1272844800"; d="scan'208";a="143771470"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 12 Jun 2010 19:39:44 +0000
Received: from Freds-Computer.local (sjc-vpn6-289.cisco.com [10.21.121.33]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o5CJda4l005862; Sat, 12 Jun 2010 19:39:38 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Sat, 12 Jun 2010 12:39:44 -0700
X-PGP-Universal: processed; by Freds-Computer.local on Sat, 12 Jun 2010 12:39:44 -0700
From: Fred Baker <fred@cisco.com>
Date: Sat, 12 Jun 2010 12:39:31 -0700
Message-Id: <FE623618-6660-4CE6-9651-B122B4F04929@cisco.com>
To: IETF SmartPower Directorate <smartpowerdir@ietf.org>, "David H. Su" <david.su@nist.gov>
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: [smartpowerdir] Draft for PAP 1
X-BeenThere: smartpowerdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Members of the Smart Power Directorate <smartpowerdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smartpowerdir>, <mailto:smartpowerdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smartpowerdir>
List-Post: <mailto:smartpowerdir@ietf.org>
List-Help: <mailto:smartpowerdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smartpowerdir>, <mailto:smartpowerdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jun 2010 19:39:43 -0000

Folks: George Arnold and David Su asked me the other day fo a draft to put into NIST's Priority Action Plan #1, which is intended to produce a recommendation regarding the role of IP in the Smart Grid. The requested draft specifies the minimal structure recommended for the use of IP in a secure network.

David: I started to write a new draft, and found myself in part generating new graphics and text, and in part cribbing a lot from http://tools.ietf.org/html/draft-baker-ietf-core. I wonder, what stops us from using an updated version of http://tools.ietf.org/html/draft-baker-ietf-core as this draft?

What needs to be covered, I think, is a relatively simple set of four pictures outlining four basic uses of the IP Protocol Suite:

+-------------------------+
|       Application       |
+-----+------+-----+------+
| TCP | SCTP | UDP | NORM |    Basic IP stack
+-----+------+-----+------+
|      Internet Layer     |
+-------------------------+
|        Link Layer       |
+-------------------------+
|      Physical Layer     |
+-------------------------+

+-------------------------+
|       Application       |
+-----+------+-----+------+
| TCP | SCTP | UDP | NORM |    IP Stack with IPsec in Transport Mode
+-----+------+-----+------+    (eg, HIP-like connectivity between two systems)
|    IP Security Layer    |
+-------------------------+
|      Internet Layer     |
+-------------------------+
|        Link Layer       |
+-------------------------+
|      Physical Layer     |
+-------------------------+

+-------------------------+
|       Application       |
+-----+------+-----+------+
| TCP | SCTP | UDP | NORM |    IP Stack with IPsec in Tunnel Mode
+-----+------+-----+------+    (IPsec VPN)
|      Internet Layer     |
+-------------------------+
|    IP Security Layer    |
+-------------------------+
|      Internet Layer     |
+-------------------------+
|        Link Layer       |
+-------------------------+
|      Physical Layer     |
+-------------------------+

+-------------------------+
|       Application       |
+------------+------------+
|   TLS      |   DTLS     |    IP Stack with TLS in the application
+-----+------+-----+------+    (Secured applications)
| TCP | SCTP | UDP | NORM |
+-----+------+-----+------+
|      Internet Layer     |
+-------------------------+
|        Link Layer       |
+-------------------------+
|      Physical Layer     |
+-------------------------+

and then some discussion of the use of the stack, which I think is mostly there, along with the use of DNS and DHCP.

I have asked and have not gotten any takers... I would really prefer that the security comments in this document were written by a security person. The comments I got from the security directorate told me what they thought was wrong, but didn't suggest what the right way to say it was, and we want to say it in the right way.

In any event, if draft-baker-ietf-core-protocols were cut down to that content, it seems to me that it pretty much fills the bill and is a reasonable IETF output that in fact could be pulled as text into the SGAC's Conceptual Model. 

Directorate, would you agree with that? David?