[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] sip to draft/interop report discussion
And I said, "yes," so there are more editors in the pool than the
empty set.
[no empty suit jokes, please]
On Jul 29, 2008, at 1:52 PM, James M. Polk wrote:
At 07:45 AM 7/29/2008, Robert Sparks wrote:
At today's SIP meeting, the room strongly felt that progressing parts
of SIP to Draft standard is not helpful at this time.
We will continue discussion on whether to continue down the path
we've
been on for some time, maintaining SIP through the essential
correction process or biting off the very large task of a SIP-bis.
(Much of the room felt like a SIP-bis would be useful, but recognized
the arguments we would have to have, and finding the people to do the
editing work would be really difficult).
this was the question Ted started, but wasn't asked of the room,
i.e., who has "some" time to help in writing this. The question
that was asked is "who has the cycles to write this", as if an
editor was to be assigned today...
James
However that conversation goes, the room felt proceeding with the
interoperability/implementation report was worth doing now. To that
end, I'd like to ask again that everyone review the list of
staFrom sip-bounces at ietf.org Tue Jul 29 10:28:29 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 90D443A6A4F;
Tue, 29 Jul 2008 10:28:29 -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 4FC533A67EB
for <sip at core3.amsl.com>; Tue, 29 Jul 2008 10:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.231
X-Spam-Level:
X-Spam-Status: No, score=-2.231 tagged_above=-999 required=5 tests=[AWL=0.368,
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 DOjPI3wwgOUr for <sip at core3.amsl.com>;
Tue, 29 Jul 2008 10:28:27 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 7B6323A6A4F
for <sip at ietf.org>; Tue, 29 Jul 2008 10:28:27 -0700 (PDT)
Received: from [130.129.20.50] (port=54002)
by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
(Exim 4.68) (envelope-from <eburger at standardstrack.com>)
id 1KNszm-0005iK-AH; Tue, 29 Jul 2008 10:28:22 -0700
Message-Id: <B55E4E12-503A-4903-9B6F-A62C8B35AF67 at standardstrack.com>
From: Eric Burger <eburger at standardstrack.com>
To: Robert Sparks <rjsparks at nostrum.com>
In-Reply-To: <XFE-SJC-2112uzq8sCg00005dce at xfe-sjc-211.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Tue, 29 Jul 2008 18:28:22 +0100
References: <D5B6AA99-3755-47CA-B473-211910AA4E34 at nostrum.com>
<XFE-SJC-2112uzq8sCg00005dce at xfe-sjc-211.amer.cisco.com>
X-Mailer: Apple Mail (2.926)
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: SIP IETF <sip at ietf.org>
Subject: Re: [Sip] sip to draft/interop report discussion
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
And I said, "yes," so there are more editors in the pool than the
empty set.
[no empty suit jokes, please]
On Jul 29, 2008, at 1:52 PM, James M. Polk wrote:
At 07:45 AM 7/29/2008, Robert Sparks wrote:
At today's SIP meeting, the room strongly felt that progressing parts
of SIP to Draft standard is not helpful at this time.
We will continue discussion on whether to continue down the path
we've
been on for some time, maintaining SIP through the essential
correction process or biting off the very large task of a SIP-bis.
(Much of the room felt like a SIP-bis would be useful, but recognized
the arguments we would have to have, and finding the people to do the
editing work would be really difficult).
this was the question Ted started, but wasn't asked of the room,
i.e., who has "some" time to help in writing this. The question
that was asked is "who has the cycles to write this", as if an
editor was to be assigned today...
James
However that conversation goes, the room felt proceeding with the
interoperability/implementation report was worth doing now. To that
end, I'd like to ask again that everyone review the list of
statements
tements
in the draft and make sure they're at the right level and complete.
I'm going to set up a series of calls in August/September to work on
finishing the list of statements. If you have time to help, please
send me a note, and preferably at least statement to add to the list
(or refine one of the statements that are already there).
RjS
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
in the draft and make sure they're at the right level and complete.
I'm going to set up a series of calls in August/September to work on
finishing the list of statements. If you have time to help, please
send me a note, and preferably at least statement to add to the list
(or refine one of the statements that are already there).
RjS
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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