IETF Logo Mail Archive

Re: [sop] [Sdnp] Fwd: SOP and SDN Question

Sam Aldrin <sam.aldrin@gmail.com> Fri, 24 February 2012 16:09 UTC

Return-Path: <sam.aldrin@gmail.com>
X-Original-To: sop@ietfa.amsl.com
Delivered-To: sop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64A2921F885A for <sop@ietfa.amsl.com>; Fri, 24 Feb 2012 08:09:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.901
X-Spam-Level:
X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ziyuv1lnied for <sop@ietfa.amsl.com>; Fri, 24 Feb 2012 08:09:19 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B5C4E21F8807 for <sop@ietf.org>; Fri, 24 Feb 2012 08:09:19 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so2880428pbc.31 for <sop@ietf.org>; Fri, 24 Feb 2012 08:09:19 -0800 (PST)
Received-SPF: pass (google.com: domain of sam.aldrin@gmail.com designates 10.68.224.9 as permitted sender) client-ip=10.68.224.9;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sam.aldrin@gmail.com designates 10.68.224.9 as permitted sender) smtp.mail=sam.aldrin@gmail.com; dkim=pass header.i=sam.aldrin@gmail.com
Received: from mr.google.com ([10.68.224.9]) by 10.68.224.9 with SMTP id qy9mr9220024pbc.102.1330099759629 (num_hops = 1); Fri, 24 Feb 2012 08:09:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=fs0sua57lB5KLvCr3dGWa8dU6Dv1LhxZcvYXV1NW6LE=; b=xLdSX4SaNNQrsQ40rk+cU10uXfOJ3QgzyH23wWFDiO5okZRQb01V2dlX+p2LEeuBzi eL2BQZ0fGhsCpMzkgVJCzWgS33Jo1MKqNJ18MwTw3wHNSvuYr33tsNbVtIXfGzgczU2A t+0noFsA3uwwCkB2dx4HRkmtyts1urLI5PRHI=
Received: by 10.68.224.9 with SMTP id qy9mr7714230pbc.102.1330099759519; Fri, 24 Feb 2012 08:09:19 -0800 (PST)
Received: from [192.168.1.3] (c-107-3-156-34.hsd1.ca.comcast.net. [107.3.156.34]) by mx.google.com with ESMTPS id 3sm4673878pbx.66.2012.02.24.08.09.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 24 Feb 2012 08:09:18 -0800 (PST)
References: <CAA3wLqUZNK1XpMm8bZuXK4UcLxy4fKbjLvYK6iX537bWWEfqpw@mail.gmail.com> <CAA3wLqW3y5_ucz+P5+be1+Js-56TnbJGNRQ=sB1p=SWyVZZt3Q@mail.gmail.com> <353D9CCB-2576-4A88-AAFC-DCE82FAF1101@lucidvision.com> <CAA3wLqWTkjx4ongiRoK887yOCKB-sMBRLZbVRq8VeUTzz+s_mQ@mail.gmail.com> <C9AE5879-FD8A-46FA-B08E-D1A2DDB010F3@lucidvision.com> <4F47B03C.8070301@raszuk.net> <2FB85049-EE2C-4D28-80A3-D2364B2FDB42@lucidvision.com>
In-Reply-To: <2FB85049-EE2C-4D28-80A3-D2364B2FDB42@lucidvision.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
Message-Id: <CA900321-5ED7-47B0-8083-8970E9428CA4@gmail.com>
X-Mailer: iPad Mail (9A405)
From: Sam Aldrin <sam.aldrin@gmail.com>
Date: Fri, 24 Feb 2012 08:09:16 -0800
To: Thomas Nadeau <tnadeau@lucidvision.com>
Cc: "sdnp@lucidvision.com" <sdnp@lucidvision.com>, "sop@ietf.org" <sop@ietf.org>, "robert@raszuk.net" <robert@raszuk.net>
Subject: Re: [sop] [Sdnp] Fwd: SOP and SDN Question
X-BeenThere: sop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Service Orchestration and Desciption for Cloud Services <sop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sop>, <mailto:sop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sop>
List-Post: <mailto:sop@ietf.org>
List-Help: <mailto:sop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sop>, <mailto:sop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2012 16:09:21 -0000

I think SDN is being over loaded and confusion exists, not just between Driven and Defined, but also what each of those does. The way i understood and also being presented is, ONF SDN encompasses not just openflow, but network applications with the help of northbound API between controller and applications. Where SDNP plays pivotal role in defining protocol elements  and api to interconnect network elements and applications. It is high time to gets the terms identified along with clear definition of what it does, and more importantly, start using them in future conversations could alleviate the confusion.

Cheers
Sam

Sent from my iPad

On Feb 24, 2012, at 7:48 AM, Thomas Nadeau <tnadeau@lucidvision.com> wrote:

> 
> On Feb 24, 2012, at 10:43 AM, Robert Raszuk wrote:
> 
>> Hi Tom,
>> 
>>>> You seem to suggest that Open Flow can be expanded to include services
>>>> besides networking.
>>> 
>>> I think you misunderstood what I wrote. Software Defined Networks (i.e.:
>>> OpenFlow) is targeted at working at the hardware abstraction level only.
>> 
>> That's completely inaccurate.
> 
>    Not completely. *)
>    
>> SDN is all about network applications. You perhaps are confusing it with ONF which indeed at this point is focused on defining OpenFlow protocol.
> 
>    Software DRIVEN Networks is all about network applications *and* their interaction with network services and elements, of which a
> subset is Software *defined* Networks (I.e.: OpenFlow).   We really need to pick a different term for Software Driven Networks because 
> it is confusing everyone. People seem to equate "SDN" with OpenFlow without being clear about the "D".
> 
>    --Tom
> 
> 
> 
>> But protocols are not defined just by bunch of hardware enthusiasts. They are defined to address specific software defined applications.
>> 
>> Best,
>> R.
>> 
>> 
>> 
>> Software *Driven* Networks is
>>> targeted at services and network elements.
>>> There is a clear difference.
>>> 
>>> --Tom
>> 
>> 
> 
> _______________________________________________
> SDNP mailing list
> SDNP@lucidvision.com
> http://lucidvision.com/mailman/listinfo/sdnp

v2.23.0 | Report a Bug | By Email