[martini] Olive & Cocktail Napkins

Cullen Jennings <fluffy@cisco.com> Sat, 06 November 2010 23:30 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: martini@core3.amsl.com
Delivered-To: martini@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A6283A68BA for <martini@core3.amsl.com>; Sat, 6 Nov 2010 16:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZ2wM6-FXNMu for <martini@core3.amsl.com>; Sat, 6 Nov 2010 16:30:21 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 894023A68A7 for <Martini@ietf.org>; Sat, 6 Nov 2010 16:30:21 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAE6C1UyrRN+K/2dsb2JhbACiCnGgY5pOhUgEhFiFfYMK
X-IronPort-AV: E=Sophos;i="4.58,308,1286150400"; d="scan'208";a="213040893"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 06 Nov 2010 23:30:38 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id oA6NUb0W023565 for <Martini@ietf.org>; Sat, 6 Nov 2010 23:30:38 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Sat, 6 Nov 2010 17:30:56 -0600
Message-Id: <3C8A22A6-2D1F-4064-A1E1-F599867AEB1D@cisco.com>
To: "martini@ietf.org" <Martini@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [martini] Olive & Cocktail Napkins
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of en-mass SIP PBX registration mechanisms <martini.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/martini>
List-Post: <mailto:martini@ietf.org>
List-Help: <mailto:martini-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Nov 2010 23:30:22 -0000

I suspect this general approach can work but I was really hoping to see far more of the details worked out  - it's still pretty much a back of the cocktail napkin level design. For example,, when a given 4 digit dialing plan is partitioned across a couple PBX and perhaps some of the elements support and some don't, I wonder about what will happened. Its hard to figure out if it all works or not without getting more of the details fleshed out. That said, I think this looks promising, I just wish it was further along - and I'm not volunteering to send text :-)