IETF Logo Mail Archive

Re: [sipcore] Milestone to revise RFC 3265

"Elwell, John" <john.elwell@siemens-enterprise.com> Wed, 17 June 2009 10:14 UTC

Return-Path: <john.elwell@siemens-enterprise.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 8482E3A6809 for <sipcore@core3.amsl.com>; Wed, 17 Jun 2009 03:14:32 -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 svdyv6YovQL9 for <sipcore@core3.amsl.com>; Wed, 17 Jun 2009 03:14:31 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 0956D3A69CE for <sipcore@ietf.org>; Wed, 17 Jun 2009 03:14:31 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([172.23.15.171]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KLD0036YOEJ2P@siemenscomms.co.uk> for sipcore@ietf.org; Wed, 17 Jun 2009 11:13:31 +0100 (BST)
Date: Wed, 17 Jun 2009 11:13:32 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
In-reply-to: <4A3227D2.4020808@ericsson.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, SIPCORE <sipcore@ietf.org>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D002063E84@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: quoted-printable
Thread-Topic: [sipcore] Milestone to revise RFC 3265
Thread-Index: AcnrRQcGTO4lyl0RQ6eEVbQP4J3whAD7zFVg
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <4A3227D2.4020808@ericsson.com>
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: Wed, 17 Jun 2009 10:14:32 -0000

Yes to both.

John 

> -----Original Message-----
> From: sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] On Behalf Of Gonzalo Camarillo
> Sent: 12 June 2009 11:03
> To: SIPCORE
> 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