IETF Logo Mail Archive

Re: [sipcore] Milestone to revise RFC 3265

Byron Campen <bcampen@estacado.net> Fri, 12 June 2009 13:56 UTC

Return-Path: <bcampen@estacado.net>
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 0778B3A68A9 for <sipcore@core3.amsl.com>; Fri, 12 Jun 2009 06:56:08 -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 C-zMj3cJFG3b for <sipcore@core3.amsl.com>; Fri, 12 Jun 2009 06:56:07 -0700 (PDT)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:266::2]) by core3.amsl.com (Postfix) with ESMTP id B9B473A686A for <sipcore@ietf.org>; Fri, 12 Jun 2009 06:56:06 -0700 (PDT)
Received: from dn3-233.estacado.net (dn3-233.estacado.net [172.16.3.233]) (authenticated bits=0) by estacado.net (8.14.2/8.14.2) with ESMTP id n5CDtZS3002922 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 12 Jun 2009 08:56:09 -0500 (CDT) (envelope-from bcampen@estacado.net)
Message-Id: <68C626DF-76DB-4849-A7FC-FDB84AE2A576@estacado.net>
From: Byron Campen <bcampen@estacado.net>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
In-Reply-To: <4A3227D2.4020808@ericsson.com>
Content-Type: multipart/signed; boundary="Apple-Mail-13-219796874"; micalg="sha1"; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 12 Jun 2009 08:56:09 -0500
References: <4A3227D2.4020808@ericsson.com>
X-Mailer: Apple Mail (2.935.3)
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: Fri, 12 Jun 2009 13:56:08 -0000

	Yes.

Best regards,
Byron Campen

> 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