[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Draft agenda, SIP at IETF 72
On Jul 17, 2008, at 24:31 , Hadriel Kaplan wrote:
I'm also very surprised SIP can be scheduled in conflict with any
other RAI WG, especially a brand new one. :(
All the RAI groups that requested more than one session had their
second session scheduled in conflict with another meeting. If anyone
wants toFrom sip-bounces at ietf.org Fri Jul 18 11:47:36 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 882983A6A54;
Fri, 18 Jul 2008 11:47:36 -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 DB11728C10B
for <sip at core3.amsl.com>; Fri, 18 Jul 2008 11:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level:
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5
tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
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 1z6y7zbuYjU7 for <sip at core3.amsl.com>;
Fri, 18 Jul 2008 11:47:33 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
by core3.amsl.com (Postfix) with ESMTP id 9A0D23A68CC
for <sip at ietf.org>; Fri, 18 Jul 2008 11:47:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,211,1215388800"; d="scan'208";a="128550889"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
by sj-iport-6.cisco.com with ESMTP; 18 Jul 2008 18:48:07 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m6IIm7HZ031084;
Fri, 18 Jul 2008 11:48:07 -0700
Received: from [142.131.206.177] (sjc-vpn5-1491.cisco.com [10.21.93.211])
by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m6IIm7Ur019623;
Fri, 18 Jul 2008 18:48:07 GMT
Message-Id: <69762338-7636-45B9-8A58-70616FC87A0A at cisco.com>
From: Cullen Jennings <fluffy at cisco.com>
To: "Hadriel Kaplan" <HKaplan at acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC30EFF77827F at mail.acmepacket.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Fri, 18 Jul 2008 11:51:17 -0700
References: <E22BEE62-CA95-4FAC-839D-A4654950C404 at softarmor.com><B70B8EAC-2BC3-446D-AB56-522871BD5B28 at nostrum.com><0D5F89FAC29E2C41B98A6A762007F5D0E9B5B7 at GBNTHT12009MSX.gb002.siemens.net>
<E6C2E8958BA59A4FB960963D475F7AC30EFF77827F at mail.acmepacket.com>
X-Mailer: Apple Mail (2.928.1)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=804; t=1216406887; x=1217270887;
c=relaxed/simple; s=sjdkim4002;
h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
d=cisco.com; i=fluffy at cisco.com;
z=From:=20Cullen=20Jennings=20<fluffy at cisco.com>
|Subject:=20Re=3A=20[Sip]=20Draft=20agenda,=20SIP=20at=20IE
TF=2072 |Sender:=20;
bh=rPkl3+mz/F9YXHB9DeYWbGDft7t5asjLV4wu/r2DIno=;
b=hTaDqsow42azub/Xo8DVRbk2+W0pwUeHS7yNSOZSuq2F68Vkeuch5H3pZr
9c82xztQXFOzc8apyqXZNjS2aCywWSI4o5GgJ7M4vmfCQLtYG8bKojnZ82xI
Cll7bZc5Ai;
Authentication-Results: sj-dkim-4; header.From=fluffy at cisco.com; dkim=pass (
sig from cisco.com/sjdkim4002 verified; );
Cc: SIP IETF <sip at ietf.org>, Dean Willis <dean.willis at softarmor.com>, "Elwell,
John" <john.elwell at siemens.com>
Subject: Re: [Sip] Draft agenda, SIP at IETF 72
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-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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
On Jul 17, 2008, at 24:31 , Hadriel Kaplan wrote:
I'm also very surprised SIP can be scheduled in conflict with any
other RAI WG, especially a brand new one. :(
All the RAI groups that requested more than one session had their
second session scheduled in conflict with another meeting. If anyone
wants to tell me tell me what groups should be closed to make more time for
SIP, or what WG needs less time than they are currently getting, well
that would be very useful input to me. Wishing there was more time is
something the IESG is working on for IETF 73. We are trying to
consider how to run meetings on Friday afternoon to provide more time.
No final decisions have been made on this but you can expect to hear
more about this in Dublin before any decisions get made.
_______________________________________________
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
what groups should be closed to make more time for
SIP, or what WG needs less time than they are currently getting, well
that would be very useful input to me. Wishing there was more time is
something the IESG is working on for IETF 73. We are trying to
consider how to run meetings on Friday afternoon to provide more time.
No final decisions have been made on this but you can expect to hear
more about this in Dublin before any decisions get made.
_______________________________________________
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