[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Let's talk about a Dublin agenda
> That's because you posted that on a list no one pays attention to. :)
> (who even knew there was an rai-discuss at ietf.org separate
> from rai at ietf.org??)
Neither are used much at all, for whatever that's worth.
> And you propFrom sip-bounces at ietf.org Tue Jun 24 16:50:24 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id A77183A6783;
Tue, 24 Jun 2008 16:50:24 -0700 (PDT)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 00DA43A6783
for <sip at core3.amsl.com>; Tue, 24 Jun 2008 16:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level:
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038,
BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 QXBhNDZvkwoS for <sip at core3.amsl.com>;
Tue, 24 Jun 2008 16:50:23 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
by core3.amsl.com (Postfix) with ESMTP id 305143A6782
for <sip at ietf.org>; Tue, 24 Jun 2008 16:50:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,699,1204531200"; d="scan'208";a="59996577"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
by sj-iport-2.cisco.com with ESMTP; 24 Jun 2008 16:50:24 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m5ONoOQv028439;
Tue, 24 Jun 2008 16:50:24 -0700
Received: from dwingwxp01 ([10.32.240.194])
by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m5ONoOaS026782;
Tue, 24 Jun 2008 23:50:24 GMT
From: "Dan Wing" <dwing at cisco.com>
To: "'Hadriel Kaplan'" <HKaplan at acmepacket.com>,
"'Dean Willis'" <dean.willis at softarmor.com>, <sip at ietf.org>
References: <A786AB6D-F6C7-4048-98B5-3AE64140FCDA at softarmor.com>
<E6C2E8958BA59A4FB960963D475F7AC30DAAD0D03C at mail.acmepacket.com>
<08a301c8d64e$f55b8cb0$c2f0200a at cisco.com>
<E6C2E8958BA59A4FB960963D475F7AC30DAAD0D1F0 at mail.acmepacket.com>
Date: Tue, 24 Jun 2008 16:50:22 -0700
Message-ID: <090c01c8d655$117ae4d0$c2f0200a at cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC30DAAD0D1F0 at mail.acmepacket.com>
Thread-Index: AcjWLzVVXmf8yzqAT3SGmzN/KRwFSQACpurgAAVAu3AAAErVgAABJmRw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=917; t=1214351424; x=1215215424;
c=relaxed/simple; s=sjdkim1004;
h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
d=cisco.com; i=dwing at cisco.com;
z=From:=20=22Dan=20Wing=22=20<dwing at cisco.com>
|Subject:=20RE=3A=20[Sip]=20Let's=20talk=20about=20a=20Dubl
in=20agenda |Sender:=20;
bh=wyUssYuw/FZIcgt51Gtjeh0qvR3LN07nVtvE2atrzc0=;
b=adwcGUlyUocu2+3KvzNesuC5zDUYHQO9ioQUF0DEEgxupDjiA9ByDRIoXd
myJkKTxNdLXzkQr3HRXV5bi4b6XEKEuSyH2KHi5mPeAQg2hf+vxTLUn79Z/l
qp52uKKuOg0zOn5VP12lDanQ0OIJ6Na8F5gzW1YljnizbG2h+RdDo=;
Authentication-Results: sj-dkim-1; header.From=dwing at cisco.com; dkim=pass (
sig from cisco.com/sjdkim1004 verified; );
Cc: 'Keith Drage' <drage at alcatel-lucent.com>
Subject: Re: [Sip] Let's talk about a Dublin agenda
X-BeenThere: sip at 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 at ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sip>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
> That's because you posted that on a list no one pays attention to. :)
> (who even knew there was an rai-discuss at ietf.org separate
> from rai at ietf.org??)
Neither are used much at all, for whatever that's worth.
> And you proposed oveosed 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.
Sounds great to me!
-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 at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
rlapping 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.
Sounds great to me!
-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 at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip