Re: [sop] [Sdnp] FW: New Non-WG Mailing List: sop -- Service Orchestration and Desciption for Cloud Services

Thomas Nadeau <tnadeau@lucidvision.com> Thu, 16 February 2012 17:04 UTC

Return-Path: <tnadeau@lucidvision.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 E57A021F885F for <sop@ietfa.amsl.com>; Thu, 16 Feb 2012 09:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level:
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 zB+s5IFayz0o for <sop@ietfa.amsl.com>; Thu, 16 Feb 2012 09:04:06 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id AAF3921F8864 for <sop@ietf.org>; Thu, 16 Feb 2012 09:04:06 -0800 (PST)
Received: from [192.168.1.94] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 301C7208E0F0; Thu, 16 Feb 2012 12:04:06 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_BDB191F1-1F98-4F06-8BAD-2111ECAF3FC3"
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <CAA3wLqW5mdKRpwheykEDXe2udjHsQBt5dHx7fsD62DhGGPaYLA@mail.gmail.com>
Date: Thu, 16 Feb 2012 12:04:05 -0500
Message-Id: <6EDB11CC-228B-4C1A-90F8-37E311D31878@lucidvision.com>
References: <CB62CCB4.C846D%mmorrow@cisco.com> <470D91CE-5D54-48F8-8889-438DA873A3FA@lucidvision.com> <618BE8B40039924EB9AED233D4A09C5103001E76@XMB-BGL-416.cisco.com> <CAHEV9L3EiCHutLEYHTCbPc0b439k_47mda1y1ONmwthKrQMiYw@mail.gmail.com> <618BE8B40039924EB9AED233D4A09C5103001E8E@XMB-BGL-416.cisco.com> <CAHEV9L0wgfFt_j6JPgb36vRSj0-LF3bS+NjUuKcTyKwoeVq3Sg@mail.gmail.com> <618BE8B40039924EB9AED233D4A09C5103001EA3@XMB-BGL-416.cisco.com> <CAHEV9L0w-E_Ejvbu=3DHo6kt4ssXmrZKZqzJe6NLCSrgak-cUg@mail.gmail.com> <8BEA2A9F-98D2-4828-BD68-5D980BD81EFE@lucidvision.com> <CAA3wLqW5mdKRpwheykEDXe2udjHsQBt5dHx7fsD62DhGGPaYLA@mail.gmail.com>
To: Michael Hammer <mphmmr@gmail.com>
X-Mailer: Apple Mail (2.1257)
Cc: sop@ietf.org, Ping Pan <ping@pingpan.org>, "Ashish Dalela \(adalela\)" <adalela@cisco.com>
Subject: Re: [sop] [Sdnp] FW: New Non-WG Mailing List: sop -- Service Orchestration and Desciption for Cloud Services
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: Thu, 16 Feb 2012 17:04:11 -0000

On Feb 16, 2012, at 11:47 AM, Michael Hammer wrote:

> For interoperability's sake across private and public clouds from different network providers, we are looking for a protocol to be developed.

	Is this a service provider requirement or one from equipment vendors?

> The analogy we are making is that on-demand provisioning of a voice/video  network circuit between two points is done with SIP.  Without interferring with that effort, and working in parallel, what is the difference with the on-demand provisioning of network/compute/storage over IP?
> 
> Would you also argue that all the SIP work should not have been done in IETF?
> Or that SIP should not have been done because there are open-source projects?

	I am not arguing either way; I was asking the question to the wider audience.

	--Tom


> 
> Mike
> 
> 
> On Thu, Feb 16, 2012 at 11:36 AM, Thomas Nadeau <tnadeau@lucidvision.com>; wrote:
> 
> 	Good point Ping. That is the question in my mind. Does this belong somewhere else like where OpenStack is being done, or otherwise?
> 
> 	--Tom
> 
> 	
> 
> On Feb 16, 2012, at 11:17 AM, Ping Pan wrote:
> 
>> On Thu, Feb 16, 2012 at 8:09 AM, Ashish Dalela (adalela) <adalela@cisco.com>; wrote:
>> This isn’t just about the network resources and SOP isn’t only about provisioning network resources. The protocol definition is generalized to support any kind of service – network included.
>> 
>> Be careful. Others have brought up similar proposal before. IETF stands for Internet Engineering TF... Networking is the name of the game. ;-) If not networking, I fear it would be wrong place to do the work.
>> 
>> In SDN, our focus is on networking. Further, we are trying to distance ourselves from the actual DC network fabric design (all vendor-specific so far).
>> 
>> Regards,
>> 
>> Ping
>> _______________________________________________
>> sop mailing list
>> sop@ietf.org
>> https://www.ietf.org/mailman/listinfo/sop
> 
> 
> _______________________________________________
> sop mailing list
> sop@ietf.org
> https://www.ietf.org/mailman/listinfo/sop
> 
>