Re: [Sip] SIP level bundeling
Brett Tate <brett@broadsoft.com> Mon, 30 May 2011 12:36 UTC
Return-Path: <brett@broadsoft.com>
X-Original-To: sip@ietfa.amsl.com
Delivered-To: sip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 787B9E06BB for <sip@ietfa.amsl.com>; Mon, 30 May 2011 05:36:03 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XsV-ADZDDPvh for <sip@ietfa.amsl.com>; Mon, 30 May 2011 05:36:03 -0700 (PDT)
Received: from smtpedge.partnerhosted.com (smtpedge.partnerhosted.com [173.225.22.21]) by ietfa.amsl.com (Postfix) with ESMTP id F1984E0651 for <sip@ietf.org>; Mon, 30 May 2011 05:36:02 -0700 (PDT)
Received: from EXMBXCLUS01.citservers.local ([fe80::a488:d1ec:a706:3a6d]) by CASUMHUB02.citservers.local ([::1]) with mapi; Mon, 30 May 2011 05:36:04 -0700
From: Brett Tate <brett@broadsoft.com>
To: atul garg <shivalk_80@yahoo.co.in>, "sip@ietf.org" <sip@ietf.org>
Date: Mon, 30 May 2011 05:35:57 -0700
Thread-Topic: [Sip] SIP level bundeling
Thread-Index: AcwetVharn4Sbo1KRC2gtfEOyhc/lwAD2eUQ
Message-ID: <7FF1E5E16911C54BB2D57D4C4A2ED35A08CA6CB46D@EXMBXCLUS01.citservers.local>
References: <677679.62685.qm@web94808.mail.in2.yahoo.com> <BANLkTinEqXJyLYw_canwOUkKNiUxoRRRTA@mail.gmail.com>
In-Reply-To: <BANLkTinEqXJyLYw_canwOUkKNiUxoRRRTA@mail.gmail.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
Subject: Re: [Sip] SIP level bundeling
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2011 12:36:03 -0000
> > 2) In case of SIP fregmanmtion, I guess as TCP does not know the > logical intelligence of SIP message, therefore sip message can be > fregmented at any location even in between sip header, before call is > ..... am i correct ... > > Of course. TCP is not message boundary so the receiver must buffer the > received data until it becomes a valid SIP message (it could drop the > connection if it takes so long as it could be an attack). Additionally concerning stream-oriented transports, the Content-Length header value is used to locate the end of the SIP message. See RFC 3261 section 7.5, 18.3, and 20.14.
- [Sip] SIP level bundeling atul garg
- Re: [Sip] SIP level bundeling Iñaki Baz Castillo
- Re: [Sip] SIP level bundeling Brett Tate
- Re: [Sip] SIP level bundeling Worley, Dale R (Dale)