IETF Logo Mail Archive

Re: [sipcore] Call for Consensus: draft-holmberg-sip-keep

"Schmidt, Christian 1. (NSN - DE/Munich)" <christian.1.schmidt@nsn.com> Fri, 17 April 2009 06:26 UTC

Return-Path: <christian.1.schmidt@nsn.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 EDA8E3A67F8 for <sipcore@core3.amsl.com>; Thu, 16 Apr 2009 23:26:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.265
X-Spam-Level:
X-Spam-Status: No, score=-4.265 tagged_above=-999 required=5 tests=[AWL=-1.667, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 pRiOJ-3i2nDr for <sipcore@core3.amsl.com>; Thu, 16 Apr 2009 23:26:07 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [217.115.75.234]) by core3.amsl.com (Postfix) with ESMTP id 41FA03A6D4E for <sipcore@ietf.org>; Thu, 16 Apr 2009 23:25:46 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id n3H6QwAO028312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 17 Apr 2009 08:26:58 +0200
Received: from demuexc024.nsn-intra.net (demuexc024.nsn-intra.net [10.159.32.11]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id n3H6QuOd011225; Fri, 17 Apr 2009 08:26:57 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 17 Apr 2009 08:26:57 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9BF25.81C97324"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 17 Apr 2009 08:26:56 +0200
Message-ID: <B846208195B11F4EA16E16BE9DC8A9CC018E34A8@DEMUEXC013.nsn-intra.net>
In-Reply-To: <49E7BF9D.10706@nostrum.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sipcore] Call for Consensus: draft-holmberg-sip-keep
Thread-Index: Acm+616TpvXWtFBBQIe+as7Y7apT8gAOhM1w
References: <49E7BF9D.10706@nostrum.com>
From: "Schmidt, Christian 1. (NSN - DE/Munich)" <christian.1.schmidt@nsn.com>
To: ext Adam Roach <adam@nostrum.com>, SIPCORE <sipcore@ietf.org>
X-OriginalArrivalTime: 17 Apr 2009 06:26:57.0253 (UTC) FILETIME=[82006950:01C9BF25]
Subject: Re: [sipcore] Call for Consensus: draft-holmberg-sip-keep
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, 17 Apr 2009 06:26:08 -0000

yes
 
/christian

________________________________

From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On
Behalf Of ext Adam Roach
Sent: Friday, April 17, 2009 1:31 AM
To: SIPCORE
Subject: [sipcore] Call for Consensus: draft-holmberg-sip-keep


[as chair]

There was already a request for consensus around adopting the document
draft-holmberg-sip-keep on the SIP working group mailing list. The call
was for adopting it "as a WG document in RAI (WG tbd)". The specific
call for consensus can be found here:

  <http://www.ietf.org/mail-archive/web/sip/current/msg27141.html>
<http://www.ietf.org/mail-archive/web/sip/current/msg27141.html> 

There were 15 messages in support of doing so, and no objections.

I'm asking a related but slightly different question: Given that SIPCORE
has a charter milestone for "Mechanism for indicating support for
keep-alives," do you think we should adopt draft-holmberg-sip-keep as
the basis for completing this milestone? As before, a simple "yes" is
fine; however, if you don't think we should adopt this document, please
provide rationale.

/a

v2.23.0 | Report a Bug | By Email