IETF Logo Mail Archive

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

"DRAGE, Keith (Keith)" <drage@alcatel-lucent.com> Thu, 16 April 2009 23:40 UTC

Return-Path: <drage@alcatel-lucent.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 E9F1B3A691B for <sipcore@core3.amsl.com>; Thu, 16 Apr 2009 16:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.04
X-Spam-Level:
X-Spam-Status: No, score=-4.04 tagged_above=-999 required=5 tests=[AWL=-1.791, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 Rq0VViFcSqE9 for <sipcore@core3.amsl.com>; Thu, 16 Apr 2009 16:40:11 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id F36C73A67C0 for <sipcore@ietf.org>; Thu, 16 Apr 2009 16:40:10 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n3GNfLtU030024 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 17 Apr 2009 01:41:21 +0200
Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.39]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Fri, 17 Apr 2009 01:41:21 +0200
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: Adam Roach <adam@nostrum.com>, SIPCORE <sipcore@ietf.org>
Date: Fri, 17 Apr 2009 01:41:18 +0200
Thread-Topic: [sipcore] Call for Consensus: draft-holmberg-sip-keep
Thread-Index: Acm+62XcdDn9STxeQ1qQnDx4MrUBQwAAUwmw
Message-ID: <28B7C3AA2A7ABA4A841F11217ABE78D6758C6061@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com>
References: <49E7BF9D.10706@nostrum.com>
In-Reply-To: <49E7BF9D.10706@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
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: Thu, 16 Apr 2009 23:40:12 -0000

While I understand the documents are substantially the same, it mught be better to ask the question of:
 
http://www.ietf.org/internet-drafts/draft-holmberg-sipcore-keep-00.txt

regards

Keith


________________________________

	From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On Behalf Of Adam Roach
	Sent: Friday, April 17, 2009 12: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