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

"Ashish Dalela (adalela)" <adalela@cisco.com> Thu, 16 February 2012 17:09 UTC

Return-Path: <adalela@cisco.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 9A34221F8891 for <sop@ietfa.amsl.com>; Thu, 16 Feb 2012 09:09:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.949
X-Spam-Level:
X-Spam-Status: No, score=-6.949 tagged_above=-999 required=5 tests=[AWL=3.649, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 iTdYZjHnHrxo for <sop@ietfa.amsl.com>; Thu, 16 Feb 2012 09:09:51 -0800 (PST)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 28D7621F87D4 for <sop@ietf.org>; Thu, 16 Feb 2012 09:09:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=adalela@cisco.com; l=15885; q=dns/txt; s=iport; t=1329412188; x=1330621788; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=5Lc+WC84to0ch0cgsll6KHQs6+kDfWABTVimczyGxVA=; b=Bhg8lD8UjGM6rdlQ90jil7ukHyvr/J/1FSLjIQkgyU1w1+r8SW3Hvtv2 Xr+bau0+EeMDiSxdR4v5meCPq64bIw6bqUvSeS/AKgKOenrzxf3MpfRfg LrGYnvuscF7I+FIzvXHyGVWUqzjcolgdn/9Q5+IFiVlo/9Q3nOQtxyRe6 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFABk3PU9Io8UY/2dsb2JhbABDglGlTwGJTYFyAQEBBAEBAQ8BCREDPgQHEAIBCA4DBAEBCwYTBAEGASYfCAEIAQEEAQoICBqHZp8TAZZoi24CAgQUAQUJNRGDbgEJBhgFAgcEBQILgkdjBIhMn1s
X-IronPort-AV: E=Sophos;i="4.73,430,1325462400"; d="scan'208,217";a="5730395"
Received: from vla196-nat.cisco.com (HELO bgl-core-3.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 16 Feb 2012 17:09:46 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q1GH9jKQ006738; Thu, 16 Feb 2012 17:09:45 GMT
Received: from xmb-bgl-416.cisco.com ([72.163.129.212]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Feb 2012 22:39:45 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCECCD.C7FB377D"
Date: Thu, 16 Feb 2012 22:39:44 +0530
Message-ID: <618BE8B40039924EB9AED233D4A09C5103001EEE@XMB-BGL-416.cisco.com>
In-Reply-To: <6EDB11CC-228B-4C1A-90F8-37E311D31878@lucidvision.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sop] [Sdnp] FW: New Non-WG Mailing List: sop -- ServiceOrchestration and Desciption for Cloud Services
Thread-Index: AczszQUBYlg39lZITcWs/++0DZJXRQAAFZvw
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> <6EDB11CC-228B-4C1A-90F8-37E311D31878@lucidvision.com>
From: "Ashish Dalela (adalela)" <adalela@cisco.com>
To: "Thomas Nadeau" <tnadeau@lucidvision.com>, "Michael Hammer" <mphmmr@gmail.com>
X-OriginalArrivalTime: 16 Feb 2012 17:09:45.0757 (UTC) FILETIME=[C82A54D0:01CCECCD]
Cc: sop@ietf.org, Ping Pan <ping@pingpan.org>
Subject: Re: [sop] [Sdnp] FW: New Non-WG Mailing List: sop -- ServiceOrchestration 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:09:55 -0000

Tom,

 

I would suggest to read the requirements draft, because number of
questions you and Ping are asking here about the goal, IETF-fit,
relationship to open-source are anticipated and discussed in that draft.
To your point about who needs it - inter-cloud is a service provider
need, hybrid-cloud is a provider and customer need, and
vendor-interoperability is both provider and customer need.

 

The requirements draft is here -
http://tools.ietf.org/html/draft-dalela-orchestration-00

 

Thanks, Ashish

 

From: sop-bounces@ietf.org [mailto:sop-bounces@ietf.org] On Behalf Of
Thomas Nadeau
Sent: Thursday, February 16, 2012 10:34 PM
To: Michael Hammer
Cc: sop@ietf.org; Ping Pan; Ashish Dalela (adalela)
Subject: Re: [sop] [Sdnp] FW: New Non-WG Mailing List: sop --
ServiceOrchestration and Desciption for Cloud Services

 

 

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