IETF Logo Mail Archive

Re: [Aeon] Next step, IETF 90?

Reinaldo Penno <rapenno@gmail.com> Mon, 21 July 2014 18:18 UTC

Return-Path: <rapenno@gmail.com>
X-Original-To: aeon@ietfa.amsl.com
Delivered-To: aeon@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA53A1A0356; Mon, 21 Jul 2014 11:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 x0q7vILFkgpV; Mon, 21 Jul 2014 11:18:11 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 652DE1A0350; Mon, 21 Jul 2014 11:18:11 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id a108so5852565qge.16 for <multiple recipients>; Mon, 21 Jul 2014 11:18:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=m+ABGYHmi40qVWiIfcCd4E8isjHPc2JZKWyqYpG9BH4=; b=xbShqAQRCd5UyQWkOKkEkueMqjlO0k8L3c3dde1vjWRgGXlvANuVYl3Fyn2iEjjAmS nCanCDakYpLKgCypwc9rOoXPkv4G97HTmQmlWO5YOIPtuGlZxFeGw07pzT0e9R5f4bDq 9XVAiWd6ITpW/7Fr3GrmQb2HZmeghVcrREPUNSzV1qarcyDVqEgWceUmm9FOTaI2BHDj 0IFbJzSXhWz1uAsUSctrqUTdkTiPPYfI3P0w0XEJJt+qPUUZk0dI5PNzWABdIRR90t6L aewJ8mAdN8in6Rzwno8XBeh+8bKEevCFt0utGhHq442CXLVolWpFstFMz5ZEtHMwh2PQ HjoA==
X-Received: by 10.224.172.201 with SMTP id m9mr46189565qaz.32.1405966690493; Mon, 21 Jul 2014 11:18:10 -0700 (PDT)
Received: from [10.82.208.178] (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPSA id t9sm23533503qai.28.2014.07.21.11.18.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jul 2014 11:18:09 -0700 (PDT)
Message-ID: <53CD5964.8090400@gmail.com>
Date: Mon, 21 Jul 2014 14:18:12 -0400
From: Reinaldo Penno <rapenno@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "karagian@cs.utwente.nl" <karagian@cs.utwente.nl>, "fanpeng@chinamobile.com" <fanpeng@chinamobile.com>
References: <EA4C43BE752A194597B002779DF69BAE23B3DD5C@ESESSMB303.ericsson.se> <00bb01cf95f7$e9ef2b60$bdcd8220$@chinamobile.com> <33687996-B978-4CC8-891C-0917907EC089@huawei.com> <CAKEbE1ZXgxd+ANkrjFeEi5pYTOMcf-tVHmNuKBSK65pzRi=3Kg@mail.gmail.com> <C0E0A32284495243BDE0AC8A066631A8183D6C82@szxeml557-mbs.china.huawei.com> <FF1A9612A94D5C4A81ED7DE1039AB80F4F496A68@EXMBX23.ad.utwente.nl> <CFE16C01.2D462%eckelcu@cisco.com> <00e701cf9b74$41ddf2d0$c599d870$@chinamobile.com> <FF1A9612A94D5C4A81ED7DE1039AB80F5D5729AF@EXMBX23.ad.utwente.nl> <005401cf9ce0$f1e9c330$d5bd4990$@chinamobile.com> <FF1A9612A94D5C4A81ED7DE1039AB80F5D572B35@EXMBX23.ad.utwente.nl> <C0E0A32284495243BDE0AC8A066631A81840C2A4@szxeml557-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A818429453@szxeml557-mbs.china.huawei.com> <53CD5108.6050203@gmail.com> <CFF2CDD2.2F5AE%eckelcu@cisco.com>
In-Reply-To: <CFF2CDD2.2F5AE%eckelcu@cisco.com>
Content-Type: multipart/alternative; boundary="------------000304010707060609000304"
Archived-At: http://mailarchive.ietf.org/arch/msg/aeon/M0wlUoFj4EZ1C6I_QtpkASIJGJk
Cc: "Szilveszter.Nadas@ericsson.com" <Szilveszter.Nadas@ericsson.com>, "aeon@ietf.org" <aeon@ietf.org>, "Openv6@ietf.org" <Openv6@ietf.org>
Subject: Re: [Aeon] Next step, IETF 90?
X-BeenThere: aeon@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Application Enabled Open Networking \(AEON\)" <aeon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aeon>, <mailto:aeon-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aeon/>
List-Post: <mailto:aeon@ietf.org>
List-Help: <mailto:aeon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aeon>, <mailto:aeon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2014 18:18:13 -0000

I just responded to the other comment but (2) does not seem to be IETF 
work. IETF is about on the wire protocol interoperability, what happens 
inside a device probably has a good venue in some other SDO.

On 7/21/14, 2:11 PM, Charles Eckel (eckelcu) wrote:
> Perhaps some network devices will allow themselves to be controlled by 
> end user application applications, but that is not the model proposed 
> by AECON. Rather, AECON separates:
>
>  1. the communication of the flow characteristics from
>  2. the policy decisions and actions made by network devices based on
>     that communication
>
> AECON is about the first, not the second.

v2.23.0 | Report a Bug | By Email