Re: [Openv6] Comments on draft-karagiannis-aponf-problem-statement-02

Tom Taylor <tom.taylor.stds@gmail.com> Wed, 09 July 2014 20:02 UTC

Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: openv6@ietfa.amsl.com
Delivered-To: openv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E826A1A8BB7 for <openv6@ietfa.amsl.com>; Wed, 9 Jul 2014 13:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 hFFnKmV4mBRu for <openv6@ietfa.amsl.com>; Wed, 9 Jul 2014 13:02:47 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF68F1A8BB5 for <openv6@ietf.org>; Wed, 9 Jul 2014 13:02:46 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id lx4so5779012iec.1 for <openv6@ietf.org>; Wed, 09 Jul 2014 13:02:46 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=k2Js32ZfxCaP3v2DAsxmwqBVDxDfi0dezgj7kdpuYyE=; b=sC7Npa6YyWCXBZYRYAQgXPLA1D6ZFbK6PyoBU0K6mMgr42WMev6Ebx6mmzZGRN+yB2 cN1mW+ivY5kklTErpBnqeKs1fSIbt0ZWR5wQCdWJieFzXtXI4kI18PPT4TtUbhfIV1cs B2Fxzp9zk3OJsBgD0fVq1w8Jept3xK2wgxI1uT6DloJnlmrx5Rz7sjpDrXxZ9kjGm2Bm TO5Tn/tGr8cD68TtTFSDcWfTTNviOqv0I1AbhJ4G06aMRHzf8//yKsox4pu5ayU7asZw HgAJ3jrd5pKFQXt44Lu/AaKkUaPTRnmyNkfF6cGcx5TS8Lu7XgkoWor0rTLqQk9Ln07i gDEg==
X-Received: by 10.42.22.193 with SMTP id p1mr50741015icb.43.1404936166248; Wed, 09 Jul 2014 13:02:46 -0700 (PDT)
Received: from [192.168.0.102] (dsl-173-206-11-121.tor.primus.ca. [173.206.11.121]) by mx.google.com with ESMTPSA id b2sm18248711igg.1.2014.07.09.13.02.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Jul 2014 13:02:45 -0700 (PDT)
Message-ID: <53BD9FE3.9020006@gmail.com>
Date: Wed, 09 Jul 2014 16:02:43 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "openv6@ietf.org" <openv6@ietf.org>
References: <53BC9F97.20704@gmail.com> <CFE2CADB.2D654%eckelcu@cisco.com>
In-Reply-To: <CFE2CADB.2D654%eckelcu@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/openv6/t4xvge-o2gTz8_ROdDWnAh9lGeU
Subject: Re: [Openv6] Comments on draft-karagiannis-aponf-problem-statement-02
X-BeenThere: openv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Openv6 discussion list <openv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openv6>, <mailto:openv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/openv6/>
List-Post: <mailto:openv6@ietf.org>
List-Help: <mailto:openv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openv6>, <mailto:openv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jul 2014 20:02:49 -0000

OK, I see I read too much into the APONF problem statement. Part of the 
problem is that I assumed at the back of my mind that the upper-most box 
in the figure was a management application, whereas AECON for sure 
assumes it is an user application. Since the APONF problem statement is 
talking about service development, I would modify the figure to show two 
top boxes:

End User Application, joined to devices with AECON input.

Service Development Application, joined to Network Management 
Application as already shown, but without AECON mediation.

I'm not quite happy with this because it isn't clear exactly how SFC 
fits in with AECON. draft-conet-aeon-problem-statement-01 says:
      "Flow characteristics communicated via AEON could be
       used as input into an SFC classifier and it could be transported
       as SFC metadata."
Does that mean SFC templates would go directly to devices?

Tom Taylor

On 09/07/2014 1:36 PM, Charles Eckel (eckelcu) wrote:
> Hi Tom,
>
> If I understand the diagram correctly, it would be more accurate to show
> AECON for a line from the "end user application" to ³individual devices²,
> assuming individual devices are network elements (e.g. routers, switches,
> firewalls, etc.). AECON would not be used for end user application to
> network management application communication, at least not directly.
>
> Cheers,
> Charles
>
> On 7/8/14, 6:49 PM, "Tom Taylor" <tom.taylor.stds@gmail.com> wrote:
>
>> The APONF problem statement is definitely shaping up, although I think
>> there are still some extraneous elements that were pasted in from the
>> draft charter but don't really belong in the draft. I complained about
>> the presence of architectural descriptions in earlier versions, but I
>> suggest a summary figure showing the high-level architecture would be
>> helpful in the description of the different aspects of total problem as
>> they relate to different WGs. Here is the figure I have in mind, based
>> on my reading of the problem statement:
>>
>>                      ---------------
>>                      |  End user   |
>>                      | application |
>>                      ---------------
>>                             |
>>                             |
>>                             |
>>                   AECON-developed interface
>>                     SFC-developed model
>>                    ---------------------
>>                    | Network management |
>>                    |   application      |
>>                    ----------------------
>>                             |
>>                             |     APONF
>>                             |   transport
>>                             |
>>                             | (SFC-developed
>>                             |  templates?)
>>                             |
>>                    ----------------------
>>                    | Network management |
>>                    |      control       |
>>                    | ... and then a     |
>>                    | miracle happens :) |
>>                    |   APONF-developed  |
>>                    |     mapping?       |
>>                    ----------------------
>>                             |
>>                             |
>>                    To individual devices
>>
...