[dc] Service Orchestration Protocol
"Ashish Dalela (adalela)" <adalela@cisco.com> Thu, 16 February 2012 17:06 UTC
Return-Path: <adalela@cisco.com>
X-Original-To: dc@ietfa.amsl.com
Delivered-To: dc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6200521F8889 for <dc@ietfa.amsl.com>; Thu, 16 Feb 2012 09:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.892
X-Spam-Level:
X-Spam-Status: No, score=-6.892 tagged_above=-999 required=5 tests=[AWL=3.706, 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 7A0W1kKADrJg for <dc@ietfa.amsl.com>; Thu, 16 Feb 2012 09:06:18 -0800 (PST)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id CA73121F8864 for <dc@ietf.org>; Thu, 16 Feb 2012 09:06:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=adalela@cisco.com; l=9203; q=dns/txt; s=iport; t=1329411977; x=1330621577; h=mime-version:subject:date:message-id:from:to; bh=I7nK7jMsKQXbtIbDMHUH/BI+4naS28BzgryRJJTRivg=; b=a2XtuvD6QFFa4GjV1myQT5A8Zzx9qgN+uzwkS+uBWTqsux7YcQGeNb0A pIzgO7L+rza+InH+a0AeOlMk5vP9aiPgp0KjQHrm/+JxzO6ckkKjmGxIv HxE5rbzbzwIGgk1RuPUqa/63qQqMUOlnKtv+HxJKKML5rAbO2231Vo1Ea k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsIGAFY3PU9Io8UY/2dsb2JhbABEgk2FLqAhAYlNgXQBBAEBAQ8BCREDWwEaEAYYByYiDwEECxAah2aZEYEnAZ5Qi2QKBwILEjoRBgMCg2MBLAkEBQ0NgjpjBIhMniWBNg
X-IronPort-AV: E=Sophos;i="4.73,430,1325462400"; d="scan'208,217";a="5725019"
Received: from vla196-nat.cisco.com (HELO bgl-core-3.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 16 Feb 2012 17:06:13 +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 q1GH6DfV006195 for <dc@ietf.org>; Thu, 16 Feb 2012 17:06:13 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:36:13 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCECCD.498B189D"
x-cr-hashedpuzzle: xEo= ACG7 ADWs CyDo Dj5W EIi6 ETZx FXzN FlS3 GqUT HSLo ICVY JFvV JNNs Jyb0 J7ru; 1; ZABjAEAAaQBlAHQAZgAuAG8AcgBnAA==; Sosha1_v1; 7; {91E335D7-C9CE-472C-82BC-1B02D6729500}; YQBkAGEAbABlAGwAYQBAAGMAaQBzAGMAbwAuAGMAbwBtAA==; Thu, 16 Feb 2012 17:06:10 GMT; UwBlAHIAdgBpAGMAZQAgAE8AcgBjAGgAZQBzAHQAcgBhAHQAaQBvAG4AIABQAHIAbwB0AG8AYwBvAGwA
x-cr-puzzleid: {91E335D7-C9CE-472C-82BC-1B02D6729500}
Content-class: urn:content-classes:message
Date: Thu, 16 Feb 2012 22:36:10 +0530
Message-ID: <618BE8B40039924EB9AED233D4A09C5103001EEA@XMB-BGL-416.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Service Orchestration Protocol
Thread-Index: AczszUfin5PsG6PqTGqXkpH7GjPD4g==
From: "Ashish Dalela (adalela)" <adalela@cisco.com>
To: dc@ietf.org
X-OriginalArrivalTime: 16 Feb 2012 17:06:13.0457 (UTC) FILETIME=[499FEC10:01CCECCD]
Subject: [dc] Service Orchestration Protocol
X-BeenThere: dc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Data Center Mailing List <dc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dc>, <mailto:dc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dc>
List-Post: <mailto:dc@ietf.org>
List-Help: <mailto:dc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dc>, <mailto:dc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2012 17:06:22 -0000
Folks, This may not be completely relevant to the DC topic, but thought that some of you might be interested in it. We have a few drafts posted on a "Service Orchestration Protocol", with the intent to enable cloud interoperability. http://tools.ietf.org/html/draft-dalela-orchestration-00 - talks about why we need a protocol, a.k.a. requirements http://tools.ietf.org/html/draft-dalela-sop-architecture-00 - describes the use-cases and network deployments with the protocol http://tools.ietf.org/html/draft-dalela-sop-00 - describes the protocol's messages http://tools.ietf.org/html/draft-dalela-sdf-00 - describes scheme for service naming, workflows, etc. http://tools.ietf.org/html/draft-dalela-sop-flows-00 - describes some message flows A discussion alias https://www.ietf.org/mailman/listinfo/sop is setup for you to participate in case you find it interesting. Thanks and look forward to discussing there. -Ashish
- [dc] Service Orchestration Protocol Ashish Dalela (adalela)
- Re: [dc] Service Orchestration Protocol Bhumip Khasnabish
- Re: [dc] Service Orchestration Protocol Ashish Dalela (adalela)
- Re: [dc] Service Orchestration Protocol Bhumip Khasnabish