Re: IETF areas re-organisation steps

"Eggert, Lars" <> Sat, 27 December 2014 09:28 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 887721AD4B2; Sat, 27 Dec 2014 01:28:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mBQXRaqTfj3B; Sat, 27 Dec 2014 01:28:05 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D7E131AD4B1; Sat, 27 Dec 2014 01:28:02 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.07,650,1413270000"; d="asc'?scan'208";a="27804769"
Received: from ([]) by with ESMTP; 27 Dec 2014 01:26:59 -0800
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.995.29; Sat, 27 Dec 2014 01:26:56 -0800
Received: from ([::1]) by ([fe80::e8a8:c186:82ed:f6ce%21]) with mapi id 15.00.0995.031; Sat, 27 Dec 2014 04:26:56 -0500
From: "Eggert, Lars" <>
To: Ted Hardie <>
Subject: Re: IETF areas re-organisation steps
Thread-Topic: IETF areas re-organisation steps
Thread-Index: AQHQIHdU66HHK8Qui0yE9nczNXUAuZyjLN6AgABUh4A=
Date: Sat, 27 Dec 2014 09:26:55 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-mailer: Apple Mail (2.1993)
x-originating-ip: []
Content-Type: multipart/signed; boundary="Apple-Mail=_6C597563-05D0-432B-95D0-985BC4CE2FCA"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: IETF-Discussion list <>, Jari Arkko <>, IESG <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 27 Dec 2014 09:28:06 -0000

On 2014-12-27, at 03:24, Ted Hardie <> wrote:
> The third is that the proposal for a single mega-area that handles all upper-layer protocols and transports does not strike me, personally, as that well thought out.  The reality is that there are multiple contexts within the upper layers and that the overlap those contexts have is often at the border with the lower layers, rather than with each other.  The result of that is that finding someone who understands the full context of the work within the mega area will be difficult.  Within the APPs area that used to result in the area having a "web AD" and a "messaging AD"; making an upper layer body which then informally has a "web AD", a "messaging AD", a "VoIP AD" and a "Transport AD" thus seems likely to result.  Why it is better for that to be informal, rather than formalized into areas doesn't get set out that well in the statement you've given, and if that isn't the expectation, more explanation of how you expect that to work would be valuable.  I'm also, frankly, concerned that it will look to the rest of the industry like the IETF is minimize the importance of the work in those contexts.  That would be a very bad result indeed.


Will have more feedback after the holidays.