IETF Logo Mail Archive

Re: [sipcore] Milestone to revise RFC 3265

"DOLLY, MARTIN C, ATTLABS" <mdolly@att.com> Fri, 12 June 2009 11:05 UTC

Return-Path: <mdolly@att.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F20943A6A70 for <sipcore@core3.amsl.com>; Fri, 12 Jun 2009 04:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.024
X-Spam-Level:
X-Spam-Status: No, score=-106.024 tagged_above=-999 required=5 tests=[AWL=0.575, 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 2J33EE65WEuI for <sipcore@core3.amsl.com>; Fri, 12 Jun 2009 04:05:10 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id 418FC3A685A for <sipcore@ietf.org>; Fri, 12 Jun 2009 04:05:10 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: mdolly@att.com
X-Msg-Ref: server-15.tower-129.messagelabs.com!1244804716!18652763!1
X-StarScan-Version: 6.0.0; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 27091 invoked from network); 12 Jun 2009 11:05:17 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-15.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Jun 2009 11:05:17 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpi135.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n5CB5GGt014774 for <sipcore@ietf.org>; Fri, 12 Jun 2009 07:05:16 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpi135.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id n5CB5DPF014754 for <sipcore@ietf.org>; Fri, 12 Jun 2009 07:05:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Fri, 12 Jun 2009 07:05:12 -0400
Message-ID: <14C85D6CCBE92743AF33663BF5D24EBA02BD4803@gaalpa1msgusr7e.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sipcore] Milestone to revise RFC 3265
Thread-Index: AcnrRP6Px0NtU7k9QZWPNmcS0gN2+gACKodI
From: "DOLLY, MARTIN C, ATTLABS" <mdolly@att.com>
To: Gonzalo.Camarillo@ericsson.com, sipcore@ietf.org
Subject: Re: [sipcore] Milestone to revise RFC 3265
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2009 11:05:11 -0000

Yes to both

----- Original Message -----
From: sipcore-bounces@ietf.org <sipcore-bounces@ietf.org>
To: SIPCORE <sipcore@ietf.org>
Sent: Fri Jun 12 06:02:58 2009
Subject: [sipcore] Milestone to revise RFC 3265

Folks,

since the publication of RFC 3265, we have gotten significant experience 
deploying SIP-based notification systems. It has been proposed to revise 
RFC 3265 based on that experience. We have two questions for the WG:

1) should we add a milestone to our charter to revise RFC 3265?

2) if we add such a milestone, should we take the following draft as the 
initial WG item for the milestone?

http://tools.ietf.org/html/draft-roach-sipcore-rfc3265bis-00

Thanks,

Gonzalo
SIPCORE co-chair
_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email