Re: [Sip] Let's talk about a Dublin agenda

Hadriel Kaplan <HKaplan@acmepacket.com> Tue, 24 June 2008 23:36 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 283403A6A24; Tue, 24 Jun 2008 16:36:20 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 674643A6820 for <sip@core3.amsl.com>; Tue, 24 Jun 2008 16:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level:
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599]
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 eEtjcaYsRTFt for <sip@core3.amsl.com>; Tue, 24 Jun 2008 16:36:18 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 75F583A6A24 for <sip@ietf.org>; Tue, 24 Jun 2008 16:36:18 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.278.0; Tue, 24 Jun 2008 19:38:07 -0400
Received: from mail.acmepacket.com ([216.41.24.7]) by mail.acmepacket.com ([216.41.24.7]) with mapi; Tue, 24 Jun 2008 19:35:31 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Dan Wing <dwing@cisco.com>, 'Dean Willis' <dean.willis@softarmor.com>, "sip@ietf.org" <sip@ietf.org>
Date: Tue, 24 Jun 2008 19:36:17 -0400
Thread-Topic: [Sip] Let's talk about a Dublin agenda
Thread-Index: AcjWLzVVXmf8yzqAT3SGmzN/KRwFSQACpurgAAVAu3AAAErVgA==
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC30DAAD0D1F0@mail.acmepacket.com>
References: <A786AB6D-F6C7-4048-98B5-3AE64140FCDA@softarmor.com> <E6C2E8958BA59A4FB960963D475F7AC30DAAD0D03C@mail.acmepacket.com> <08a301c8d64e$f55b8cb0$c2f0200a@cisco.com>
In-Reply-To: <08a301c8d64e$f55b8cb0$c2f0200a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: 'Keith Drage' <drage@alcatel-lucent.com>
Subject: Re: [Sip] Let's talk about a Dublin agenda
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

That's because you posted that on a list no one pays attention to. :)
(who even knew there was an rai-discuss@ietf.org separate from rai@ietf.org??)

And you proposed overlapping things with SIP and MMUSIC, which does seem tough.
I'm thinking more like...

Thread-safe:
Thread-1          Thread-2        Thread-3
--------          --------        --------
speermint         xcon            p2psip
drinks            mediactrl
enum              speechsc


Global:
-------
avt
bliss
mmusic
simple
sip
sipping
ecrit
geopriv

Any Thread WG can conflict with a WG from another Thread.  No Global or Thread WG can conflict with a Global WG.
You could probably create a Thread-4 with ecrit and geopriv, but 3 concurrent threads seem enough.

-hadriel


> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
>
> I was shot down when I proposed it:
> http://www.ietf.org/mail-archive/web/rai-
> discuss/current/threads.html#00009
>
> I do hope we reconsider.
>
> -d

_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip