IETF Logo Mail Archive

[alto] Pub-sub interfaces

"Diego R. Lopez" <diego@tid.es> Fri, 27 December 2013 15:58 UTC

Return-Path: <diego@tid.es>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CDF11AE20E for <alto@ietfa.amsl.com>; Fri, 27 Dec 2013 07:58:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.04
X-Spam-Level:
X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7SPU7YQwpEIv for <alto@ietfa.amsl.com>; Fri, 27 Dec 2013 07:58:13 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id A20C31AE221 for <alto@ietf.org>; Fri, 27 Dec 2013 07:58:12 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MYH00HT830TDO@tid.hi.inet> for alto@ietf.org; Fri, 27 Dec 2013 16:58:05 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49]) by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 4B.D4.02810.B83ADB25; Fri, 27 Dec 2013 16:58:03 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MYH00HT430RDO@tid.hi.inet> for alto@ietf.org; Fri, 27 Dec 2013 16:58:03 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.204]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.03.0158.001; Fri, 27 Dec 2013 16:58:03 +0100
Date: Fri, 27 Dec 2013 15:58:02 +0000
From: "Diego R. Lopez" <diego@tid.es>
X-Originating-IP: [10.95.64.115]
To: "alto@ietf.org ALTO" <alto@ietf.org>
Message-id: <4DFA6345-8D80-4205-B1A7-C91FDF15AA1C@tid.es>
Content-id: <8AE27FF6A5A80E4F962ACE0F87CDDC12@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset="utf-8"
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, es-ES
Thread-topic: Pub-sub interfaces
Thread-index: AQHPAxxst12elKh7j0usAdu5KoPD8A==
X-AuditID: 0a5f4e69-b7f9b8e000000afa-0e-52bda38ba09e
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrALMWRmVeSWpSXmKPExsXCFe9nqNu9eG+QwZMbZhYPt+9ldWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxoxTO9gLpvBVHD/ygKmB8QlvFyMnh4SAicSRFXeYIWwxiQv3 1rN1MXJxCAlsY5S48vAAlPOdUWLGzktQzkxGidY1t5lAWlgEVCWm/GgHs9mA7EfNv9m7GDk4 hAWkJc5OTIGYqiDx59xjFhBbREBDYtLXOawgNq+ApcSU/9vA4swCZhJTbl5lg4gLSvyYfI8F ZAyzgLrElCm5ECXiEs2tN6HKFSWmLWpgBLEZBWQl3s2fzwoxXkFizYpbzBC2nsTa7TfYIE4Q kFiy5zzUk6ISLx//Y53AKDoLyeZZSDbPQtg8C8nmWUg2L2BkXcUoVpxUlJmeUZKbmJmTbmCk l5Gpl5mXWrKJERIrmTsYl+9UOcQowMGoxMPrsGFPkBBrYllxZe4hRgkOZiUR3q8L9wYJ8aYk VlalFuXHF5XmpBYfYmTi4JRqYFQ7tEhqRy037+knbtvmmen5xpkV1k/tWHXbYcYTbc7JBsxr zlse5musWVTO2NCSWJ945479eomWkEWMJgxn+lVN7yUtOX7NPd7lwGdtJyWZzXMqkoM8/5Qu fnG1zdS/Tov9t8WLPXrsRW97jwd7xB7OfNNfv5GxIn2W6Omygj3cmyed0j6hp8RSnJFoqMVc VJwIAEVO7A1zAgAA
Subject: [alto] Pub-sub interfaces
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Dec 2013 15:58:15 -0000

Hi,

Some time ago we discussed about the pros and cons of using Websockets for implementing server-to-client notifications and I mentioned the possibility of using a pub-sub schema for creating a general notification framework.

While reviewing some messages during my end-of-year tidying I came through this draft:
http://tools.ietf.org/html/draft-camwinget-i2rs-pubsub-sec-00
contributed to I2RS, that discusses the application of the model in the access to a programmatic interface to the routing system. I think it provides a good overview of the model, and that many of the considerations are applicable to ALTO notifications, and even more to a generalized topology service.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

v2.23.0 | Report a Bug | By Email