Re: [smartpowerdir] Draft for PAP 1

Vint Cerf <vint@google.com> Thu, 17 June 2010 11:24 UTC

Return-Path: <vint@google.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 8F9183A68A0 for <smartpowerdir@core3.amsl.com>; Thu, 17 Jun 2010 04:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.376
X-Spam-Level:
X-Spam-Status: No, score=-103.376 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 5MSQ4bwIyIrw for <smartpowerdir@core3.amsl.com>; Thu, 17 Jun 2010 04:24:33 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 0C7053A6A4B for <smartpowerdir@ietf.org>; Thu, 17 Jun 2010 04:24:25 -0700 (PDT)
Received: from kpbe18.cbf.corp.google.com (kpbe18.cbf.corp.google.com [172.25.105.82]) by smtp-out.google.com with ESMTP id o5HBOTF6012662 for <smartpowerdir@ietf.org>; Thu, 17 Jun 2010 04:24:29 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1276773869; bh=W32esSjOuAUz5ge9dv6nJkKgYcY=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=BzDcBygg8Ru1M7mdtVR9GG+wn1SGRk8wURhvEwbxKZsCTuk80U5TFlHQQtA/oXx80 PEFY4pvoNY54vP24qo02w==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=nEayVPHuZpgVu2Nh8v9yhzO4PvGOPvV9R2gqeFD2Np4KwYnJR9G4vM4LbKiD7hXCr gvre2lGwgxEXIXbwOQ3Bg==
Received: from gwaa12 (gwaa12.prod.google.com [10.200.27.12]) by kpbe18.cbf.corp.google.com with ESMTP id o5HBORWY013798 for <smartpowerdir@ietf.org>; Thu, 17 Jun 2010 04:24:27 -0700
Received: by gwaa12 with SMTP id a12so9058333gwa.2 for <smartpowerdir@ietf.org>; Thu, 17 Jun 2010 04:24:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.131.11 with SMTP id e11mr11274903ybd.270.1276773866441; Thu, 17 Jun 2010 04:24:26 -0700 (PDT)
Received: by 10.150.183.19 with HTTP; Thu, 17 Jun 2010 04:24:19 -0700 (PDT)
In-Reply-To: <FE623618-6660-4CE6-9651-B122B4F04929@cisco.com>
References: <FE623618-6660-4CE6-9651-B122B4F04929@cisco.com>
Date: Thu, 17 Jun 2010 07:24:19 -0400
Message-ID: <AANLkTilmVgtgJMTXiZUoH-ovPclMmo11-fti7NxWnS0R@mail.gmail.com>
From: Vint Cerf <vint@google.com>
To: Fred Baker <fred@cisco.com>
Content-Type: multipart/mixed; boundary="000e0cd4cda2c48cda048938140b"
X-System-Of-Record: true
Cc: "David H. Su" <david.su@nist.gov>, IETF SmartPower Directorate <smartpowerdir@ietf.org>
Subject: Re: [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: Thu, 17 Jun 2010 11:24:34 -0000

see attached edits/suggestions on Fred's excellent draft

vint



On Sat, Jun 12, 2010 at 3:39 PM, Fred Baker <fred@cisco.com> wrote:

> 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?