IETF Logo Mail Archive

[sipcore] Milestone to revise RFC 3265

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Fri, 12 June 2009 10:02 UTC

Return-Path: <gonzalo.camarillo@ericsson.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 94B3528C106 for <sipcore@core3.amsl.com>; Fri, 12 Jun 2009 03:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 VTTVWrPZxKhq for <sipcore@core3.amsl.com>; Fri, 12 Jun 2009 03:02:52 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 96B763A6AAC for <sipcore@ietf.org>; Fri, 12 Jun 2009 03:02:52 -0700 (PDT)
X-AuditID: c1b4fb3e-b7bedae0000062bb-b8-4a3227d357fd
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id C0.9D.25275.3D7223A4; Fri, 12 Jun 2009 12:02:59 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Jun 2009 12:02:58 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 12 Jun 2009 12:02:58 +0200
Received: from [131.160.37.44] (EV001E681B5FE2.lmf.ericsson.se [131.160.37.44]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 901C9245F; Fri, 12 Jun 2009 13:02:58 +0300 (EEST)
Message-ID: <4A3227D2.4020808@ericsson.com>
Date: Fri, 12 Jun 2009 13:02:58 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: SIPCORE <sipcore@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Jun 2009 10:02:58.0704 (UTC) FILETIME=[F6C2E100:01C9EB44]
X-Brightmail-Tracker: AAAAAA==
Subject: [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 10:02:53 -0000

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

v2.23.0 | Report a Bug | By Email