Re: [sipcore] rfc 5626 and connection-reuse-draft
Francois Audet <audet.francois@gmail.com> Tue, 01 December 2009 16:50 UTC
Return-Path: <audet.francois@gmail.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 DA5E23A67B6 for <sipcore@core3.amsl.com>; Tue, 1 Dec 2009 08:50:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.726
X-Spam-Level:
X-Spam-Status: No, score=-1.726 tagged_above=-999 required=5 tests=[AWL=0.873, 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 wuSxeoPmj2tb for <sipcore@core3.amsl.com>; Tue, 1 Dec 2009 08:50:45 -0800 (PST)
Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by core3.amsl.com (Postfix) with ESMTP id DE02F3A67A1 for <sipcore@ietf.org>; Tue, 1 Dec 2009 08:50:44 -0800 (PST)
Received: by bwz23 with SMTP id 23so3741488bwz.29 for <sipcore@ietf.org>; Tue, 01 Dec 2009 08:50:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=U+RcasUSrujGvwiIFeyxAI1oUtkz6b1wKtn6CKseuQY=; b=ZtkzegMJ8xk5tvKsyRcw0X4lSkwwYhvMjrbKX0jJeLdTMT9hq0SOVA41fKmZLHTMkp gNxw9Ahwy1GtIXGYF/C2Tb3l5WD+9tSu/PTQi6quwP56riMalhGpd1m3eVVMGJ5qCkJ9 Z2tvGZ0Z5WlbbFXsMJmtm4Esbcv1JjbQBHenE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=a/aJrK2NMEu9TOn5u3EvUtx9EYPjMUOVhzYZprprEKzOVdNuG76/sqLkuMNv6dED9K eMmAkL+/rzbERlZoE6vuvyEb0eDCSNnc1V/0yM/dxYel0YCNDVWfEWW9x3e8H3HGvjIA ET1rNpWbRIP7nfkHkF7g3Jos9iz9afnHE06Nc=
Received: by 10.204.155.82 with SMTP id r18mr6218059bkw.180.1259686233293; Tue, 01 Dec 2009 08:50:33 -0800 (PST)
Received: from ?172.17.1.16? (216.156.83.78.ptr.us.xo.net [216.156.83.78]) by mx.google.com with ESMTPS id 13sm90745bwz.2.2009.12.01.08.50.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 01 Dec 2009 08:50:32 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Francois Audet <audet.francois@gmail.com>
In-Reply-To: <4B152E3C.8050904@alcatel-lucent.com>
Date: Tue, 01 Dec 2009 08:50:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <16533E3A-6F3C-4D32-9EE8-FBE0368D61A8@gmail.com>
References: <FE127977CE269045BBA7EC732F399FD90370132D@rvil-mail1.RADVISION.com> <4B152E3C.8050904@alcatel-lucent.com>
To: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1077)
Cc: Ofer Goren <oferg@radvision.com>, sipcore@ietf.org
Subject: Re: [sipcore] rfc 5626 and connection-reuse-draft
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: Tue, 01 Dec 2009 16:50:45 -0000
On Dec 1, 2009, at 6:54 , Vijay K. Gurbani wrote: > Ofer Goren wrote: >> Going over RFC 5626, it looks like a superset of rules defined in connection-reuse draft. The RFC enhanced the basic feature for UDP, and added a keep alive mechanism, but all and all It looks like they both describe 2 different features describing means to use an open connection for multiple network-transactions from the server side. > > Ofer: The intersection of sip-outbound (now rfc5626) and > sip-connect-reuse is detailed in Section 2 of the sip-connect-reuse > draft. Another way to view the place under the sun for 5626 vs connect-reuse is that 5626 is typically going to be used between a UA and a proxy/registrar, while connect-reuse is expected to be used between proxies (or with servers such as voicemail servers, conference bridges and so forth where.
- [sipcore] rfc 5626 and connection-reuse-draft Ofer Goren
- Re: [sipcore] rfc 5626 and connection-reuse-draft Vijay K. Gurbani
- Re: [sipcore] rfc 5626 and connection-reuse-draft Francois Audet
- Re: [sipcore] rfc 5626 and connection-reuse-draft Ofer Goren