Re: [MMUSIC] UPDATE mechanism for Trickle ICE - Comment on draft-ivov-mmusic-trickle-ice-sip-01
"Parthasarathi R" <partha@parthasarathi.co.in> Tue, 22 October 2013 17:02 UTC
Return-Path: <partha@parthasarathi.co.in>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEFB611E81B3 for <mmusic@ietfa.amsl.com>; Tue, 22 Oct 2013 10:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.226
X-Spam-Level:
X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=0.373, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhCkS02GdiLf for <mmusic@ietfa.amsl.com>; Tue, 22 Oct 2013 10:02:04 -0700 (PDT)
Received: from smtp.mailhostbox.com (outbound-us3.mailhostbox.com [70.87.28.154]) by ietfa.amsl.com (Postfix) with ESMTP id 655A311E81BF for <mmusic@ietf.org>; Tue, 22 Oct 2013 10:02:04 -0700 (PDT)
Received: from userPC (unknown [122.179.44.8]) (Authenticated sender: partha@parthasarathi.co.in) by smtp.mailhostbox.com (Postfix) with ESMTPA id 71D02869236; Tue, 22 Oct 2013 17:01:58 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1382461323; bh=VY9vv13Frj15nA+p2W3iAjJAOFAaq5kjBqhK7WTttXY=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=RKNu3RYC4ksGprarfzUjnHNUs/jKUgkzQ5DVpOmm4Xk2wP50Ay5irKGsgCIhHfJ1b 6ELqWvPTei1LzlUZYGv5T3UqyyqpK8yeYcudODf511kI3UjOfVSm+whUeKG3q3YGw8 nmx3cDjprKSAWWWx7yyoM1mRlNxVoOCnDBZtACjU=
From: Parthasarathi R <partha@parthasarathi.co.in>
To: 'Emil Ivov' <emcho@jitsi.org>
References: <00a401cece8b$7b00f780$7102e680$@co.in> <CAPvvaaK3YOOB-Ta8+eoRcfQ8NrNRDdDf5a3VvOaN0vK=0unf7A@mail.gmail.com>
In-Reply-To: <CAPvvaaK3YOOB-Ta8+eoRcfQ8NrNRDdDf5a3VvOaN0vK=0unf7A@mail.gmail.com>
Date: Tue, 22 Oct 2013 22:31:51 +0530
Message-ID: <00ce01cecf48$6c0b5500$4421ff00$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac7Ow1WTIRfI7ZqFQkWN1nmCTzoWUwAe2y3A
Content-Language: en-us
X-CTCH-RefID: str=0001.0A0C0208.5266AF8B.00F9, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules:
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.154
Cc: 'mmusic' <mmusic@ietf.org>, 'Christer Holmberg' <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] UPDATE mechanism for Trickle ICE - Comment on draft-ivov-mmusic-trickle-ice-sip-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Oct 2013 17:02:09 -0000
Emil, In case of ICE Trickle handling in SIP (based on RFC 3261), glare is unavoidable as per RFC 3264 offer/answer mechanism. The glare handling has to be done by SIP provided mechanism like 491 handling in UPDATE/RE-INVITE. draft-partha-rtcweb-jsep-sip-01 callflow works for UPDATE & ICE compliant SIP UA and no need of extra extension. INFO based mechanism fails to identify the actual glare situation in offer/answer. Of course, it is possible to reduce the trickle ICE glare handling with special SDP handling (enhanced offer/answer) within RE-INVITE/UPDATE in case both endpoints supports the mechanism. Please read inline for more comments. Thanks Partha > -----Original Message----- > From: Emil Ivov [mailto:emcho@jitsi.org] > Sent: Tuesday, October 22, 2013 6:39 AM > To: Parthasarathi R > Cc: Christer Holmberg; Enrico Marocco (TiLab); mmusic > Subject: Re: UPDATE mechanism for Trickle ICE - Comment on draft-ivov- > mmusic-trickle-ice-sip-01 > > On Mon, Oct 21, 2013 at 8:29 PM, Parthasarathi R > <partha@parthasarathi.co.in> wrote: > > Hi all, > > > > I have mailed earlier why SIP INFO is not the right choice for > Trickle ICE > > in > > http://www.ietf.org/mail-archive/web/mmusic/current/msg11964.html. > > I remember. Have you noticed my answer? > > http://www.ietf.org/mail-archive/web/mmusic/current/msg11932.html > <Partha> Please note that my question is after your answer (msg11964 > msg11932). </Partha> > > The main > > reason is the glare handling. I have added the callflow in Sec 6.4 of > > draft-partha-rtcweb-jsep-sip-01 to explain how UPDATE handling will > look for > > Trickle ICE handling in SIP w.r.t JSEP mapping. > > I am confused. You say that your main issue is glare handling and yet > your draft proposes a solution that *introduces* glare (through > crossing UPDATEs) and then doesn't say anything about handling it. Is > this intentional? Am I missing something? > <Partha> 491 is the only known glare handling. We shall work and further enhance glare handling in UPDATE/RE-INVITE as it is obvious glare situation. I wish to confirm that INFO mechanism does not work for this situation before deep diving. </Partha> > > Could you please explain how > > glare with Trickle ICE Info package will be handled. > > That's simple. Glare does NOT occur when trickling through INFO. <Partha> The actual glare situation will be missed in INFO </Partha> > > Emil > > -- > https://jitsi.org
- [MMUSIC] UPDATE mechanism for Trickle ICE - Comme… Parthasarathi R
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Parthasarathi R
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Christer Holmberg
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Jonathan Lennox
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Paul Kyzivat
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Emil Ivov
- Re: [MMUSIC] UPDATE mechanism for Trickle ICE - C… Parthasarathi R