IETF Logo Mail Archive

Re: [sipcore] Milestone to revise RFC 3265

Dean Willis <dean.willis@softarmor.com> Sat, 13 June 2009 18:48 UTC

Return-Path: <dean.willis@softarmor.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 958393A6948 for <sipcore@core3.amsl.com>; Sat, 13 Jun 2009 11:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 poP00aqBwZWE for <sipcore@core3.amsl.com>; Sat, 13 Jun 2009 11:48:24 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id D63413A6840 for <sipcore@ietf.org>; Sat, 13 Jun 2009 11:48:24 -0700 (PDT)
Received: from [192.168.2.2] (cpe-76-182-198-42.tx.res.rr.com [76.182.198.42]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id n5DImSZv006323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 13 Jun 2009 13:48:30 -0500
Message-ID: <4A33F477.3030901@softarmor.com>
Date: Sat, 13 Jun 2009 13:48:23 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
References: <4A3227D2.4020808@ericsson.com>
In-Reply-To: <4A3227D2.4020808@ericsson.com>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: SIPCORE <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: Sat, 13 Jun 2009 18:48:25 -0000

Gonzalo Camarillo wrote:
> 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
> 

I believe that RFC 3265 should be revised, and that SIPCORE is the right
place to do it. Of course, I feel the same about 3261, 3262, 3263...

Adam's draft seems like a very good start.

--
Dean

v2.23.0 | Report a Bug | By Email