IETF Logo Mail Archive

Re: IETF areas re-organisation steps

"Eggert, Lars" <lars@netapp.com> Wed, 14 January 2015 10:07 UTC

Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 682551ACE52 for <ietf@ietfa.amsl.com>; Wed, 14 Jan 2015 02:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 kSvdQRJFIqkm for <ietf@ietfa.amsl.com>; Wed, 14 Jan 2015 02:07:11 -0800 (PST)
Received: from mx144.netapp.com (mx144.netapp.com [216.240.21.25]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA1F41A8BB1 for <ietf@ietf.org>; Wed, 14 Jan 2015 02:07:10 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.07,754,1413270000"; d="asc'?scan'208";a="11529508"
Received: from hioexcmbx01-prd.hq.netapp.com ([10.122.105.34]) by mx144-out.netapp.com with ESMTP; 14 Jan 2015 02:01:48 -0800
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx01-prd.hq.netapp.com (10.122.105.34) with Microsoft SMTP Server (TLS) id 15.0.995.29; Wed, 14 Jan 2015 02:01:47 -0800
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::d8c:be2b:9e16:f915%21]) with mapi id 15.00.0995.031; Wed, 14 Jan 2015 02:01:48 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: IETF areas re-organisation steps
Thread-Topic: IETF areas re-organisation steps
Thread-Index: AQHQIHdU66HHK8Qui0yE9nczNXUAuZy0MN6AgAmZYACAAU+0AIAA7XKA
Date: Wed, 14 Jan 2015 10:01:47 +0000
Message-ID: <88694A4C-547E-4644-B53D-C07F9A9B9128@netapp.com>
References: <ED473823-2B1E-4431-8B42-393D20BA72DF@piuha.net> <54AC505B.8090802@nostrum.com> <8EFCB6B4-0D95-459E-A316-DB29C3945A33@cooperw.in> <CA+9kkMAYZ-vYPpLxsoNkSOjDO8kDf6S51gvE+NKtMdHEr6hKxw@mail.gmail.com>
In-Reply-To: <CA+9kkMAYZ-vYPpLxsoNkSOjDO8kDf6S51gvE+NKtMdHEr6hKxw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.1993)
x-originating-ip: [10.122.56.79]
Content-Type: multipart/signed; boundary="Apple-Mail=_5C1F27D2-3BBD-40D0-9788-4A67D8539B9A"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/qXoZW8r-YOTsboftJpKL5fVSEck>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 10:07:12 -0000

FWIW, this is very close to how I break down the architecture in my head, and I agree with Ted that if we are opening the door to restructure the areas, we might as well be a bit more radical.

On 2015-1-13, at 20:51, Ted Hardie <ted.ietf@gmail.com> wrote:
> 
> The bit that works on how to determine what path flows use to get from one part of the network to another
> The bit that works on how network elements behave
> The bit that works on how network operators work.
> The bit that works to protect the networks or flows from attackers
> The bit that works on node configuration and bootstrapping
> The bit that works on how to run the network on different kinds of links
> The bit that works on how the flows behave on the network to each other
> The bit that works on how applications create flows and what those flows' exchanges should be.

v2.23.0 | Report a Bug | By Email