From daniel@olddog.co.uk Sat Dec 1 15:05:56 2012 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860AE11E80A5 for ; Sat, 1 Dec 2012 15:05:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.398 X-Spam-Level: X-Spam-Status: No, score=-102.398 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ueooptp1OQMy for ; Sat, 1 Dec 2012 15:05:55 -0800 (PST) Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 19FD311E8099 for ; Sat, 1 Dec 2012 15:05:51 -0800 (PST) Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qB1N5oio015805; Sat, 1 Dec 2012 23:05:50 GMT Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qB1N5mBS015785 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 1 Dec 2012 23:05:49 GMT From: "Daniel King" To: Date: Sat, 1 Dec 2012 23:05:42 -0000 Message-ID: <002601cdd018$63e90320$2bbb0960$@olddog.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0027_01CDD018.63EA1490" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac3QGCq7PEsKSZcUSKSYIv3/jtxaZA== Content-Language: en-gb Cc: adrian@olddog.co.uk, daniel@olddog.co.uk Subject: [Sdn] A new draft on an architecture for application-based network operations X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Dec 2012 23:05:56 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0027_01CDD018.63EA1490 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear SDNrg, Adrian and I posted an I-D which is a rather grandiose attempt to pull together a number of existing architectural components (PCE, VNTM, I2RS, policy, etc., etc.). This is a sort of meta-SDN PCE-based architect-thingy. It needed a name, so we called it Application-Based Network Operations (ABNO), warning it's not house trained and may answer to various other names: A PCE-based Architecture for Application-based Network Operations http://tools.ietf.org/html/draft-farrkingel-pce-abno-architecture-00 As some of you will know this is the result of numerous discussions we have had with a number of people over the last three months. Where pieces of the puzzle seem to have been coagulating, we thought it might be nice to build a framework in which the jelly (jello) can set. It is at a really early stage, so we are convinced you will all throw stuff at us, but what the hell! As it stands, the current draft includes: - A brief description of abstraction functional components and the interfaces between them. - An attempt to supply pointers to existing work (tool kit) where that may be applicable and there are some use case examples to give a feel for how it all works. - Various ABNO use cases. A number of areas need further discussion, especially the use cases. We decided to submit with the few we do have, in order to generate some feedback - anyone who wants to supply use case(s) and text, would receive hero status. We have pitched the document as a PCE working group document because PCE is a central component, but the document doesn't really fall inside the PCE charter. For the time being it might be best to send comments direct to us rather than clutter up any WG mailing list with discussions that are outside the charter (but if some WG chair wants to claim the work, then...) Thanks, Dan and Adrian ------=_NextPart_000_0027_01CDD018.63EA1490 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear = SDNrg,

 

Adrian and I posted an I-D which is a rather grandiose = attempt to pull together a number of existing architectural components = (PCE, VNTM, I2RS, policy, etc., etc.). This is a sort of meta-SDN = PCE-based architect-thingy. It needed a name, so we called it = Application-Based Network Operations (ABNO), warning it's not house = trained and may answer to various other names:

 

A PCE-based = Architecture for Application-based Network Operations

http://tools.ietf.org/html/draft-farrkingel-pce-abno-ar= chitecture-00

 

As some of you will know this is the result of = numerous discussions we have had with a number of people over the last = three months.  Where pieces of the puzzle seem to have been = coagulating, we thought it might be nice to build a framework in which = the jelly (jello) can set. It is at a really early stage, so we are = convinced you will all throw stuff at us, but what the = hell!

 

As it stands, the current draft = includes:

 

- A brief description of abstraction functional = components and the interfaces between them.

- An attempt to supply pointers to existing work (tool = kit) where that may be applicable and there are some use case examples = to give a feel for how it all works.

- Various ABNO use cases.

 

A number of = areas need further discussion, especially the use cases. We decided to = submit with the few we do have, in order to generate some feedback - = anyone who wants to supply use case(s) and text, would receive hero = status.

 

We have pitched the document as a PCE working group = document because PCE is a central component, but the document doesn't = really fall inside the PCE charter. For the time being it might be best = to send comments direct to us rather than clutter up any WG mailing list = with discussions that are outside the charter (but if some WG chair = wants to claim the work, then...)

 

Thanks,

Dan and = Adrian

------=_NextPart_000_0027_01CDD018.63EA1490-- From daniel@olddog.co.uk Thu Dec 13 12:31:57 2012 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E41B121F87FE for ; Thu, 13 Dec 2012 12:31:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.427 X-Spam-Level: X-Spam-Status: No, score=-102.427 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDI6cL+UBNz4 for ; Thu, 13 Dec 2012 12:31:57 -0800 (PST) Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id D2E4421F889C for ; Thu, 13 Dec 2012 12:31:56 -0800 (PST) Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDKVtQP017198; Thu, 13 Dec 2012 20:31:55 GMT Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDKVstG017186 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 13 Dec 2012 20:31:55 GMT From: "Daniel King" To: Date: Thu, 13 Dec 2012 20:31:52 -0000 Message-ID: <004f01cdd970$e2eb04f0$a8c10ed0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac3ZcNkqg3fuFXurQjuM0Rb2LKYMkw== Content-Language: en-gb Cc: adrian@olddog.co.uk Subject: [Sdn] ABNO Updated - draft-farrkingel-pce-abno-architecture-01 X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Dec 2012 20:31:58 -0000 Hi All,=20 Thanks for all the feedback so far. Please find a new version of the document: http://tools.ietf.org/html/draft-farrkingel-pce-abno-architecture-01 Updates include: - Clarification of scope (>data center and CDN) - Updates to architecture model=20 - Discussing implementation of the architecture - Placeholder for survivability and redundancy - General readability and nit fixes We know several people are working on text for additional use cases, and = we look forward to seeing those contributions! Br, Dan & Adrian. From: Daniel King [mailto:daniel@olddog.co.uk]=20 Sent: 01 December 2012 23:06 To:=20 Cc: adrian@olddog.co.uk; daniel@olddog.co.uk Subject: A new draft on an architecture for application-based network operations Dear SDNrg, Adrian and I posted an I-D which is a rather grandiose attempt to pull together a number of existing architectural components (PCE, VNTM, I2RS, policy, etc., etc.). This is a sort of meta-SDN PCE-based = architect-thingy. It needed a name, so we called it Application-Based Network Operations (ABNO), warning it's not house trained and may answer to various other names: A PCE-based Architecture for Application-based Network Operations http://tools.ietf.org/html/draft-farrkingel-pce-abno-architecture-00 As some of you will know this is the result of numerous discussions we = have had with a number of people over the last three months.=A0 Where pieces = of the puzzle seem to have been coagulating, we thought it might be nice to = build a framework in which the jelly (jello) can set. It is at a really early = stage, so we are convinced you will all throw stuff at us, but what the hell! As it stands, the current draft includes: - A brief description of abstraction functional components and the interfaces between them.=20 - An attempt to supply pointers to existing work (tool kit) where that = may be applicable and there are some use case examples to give a feel for = how it all works. - Various ABNO use cases.=20 A number of areas need further discussion, especially the use cases. We decided to submit with the few we do have, in order to generate some feedback - anyone who wants to supply use case(s) and text, would = receive hero status.=20 We have pitched the document as a PCE working group document because PCE = is a central component, but the document doesn't really fall inside the PCE charter. For the time being it might be best to send comments direct to = us rather than clutter up any WG mailing list with discussions that are = outside the charter (but if some WG chair wants to claim the work, then...) Thanks, Dan and Adrian