IETF Logo Mail Archive

Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 26 March 2014 14:31 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 043FB1A0113 for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 07:31:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pKXozLOfSfRd for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 07:31:25 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id D26701A00E3 for <mmusic@ietf.org>; Wed, 26 Mar 2014 07:31:24 -0700 (PDT)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta08.westchester.pa.mail.comcast.net with comcast id iCqk1n0050EZKEL58EXPx5; Wed, 26 Mar 2014 14:31:23 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta01.westchester.pa.mail.comcast.net with comcast id iEXN1n00y3ZTu2S3MEXPeZ; Wed, 26 Mar 2014 14:31:23 +0000
Message-ID: <5332E4BA.40203@alum.mit.edu>
Date: Wed, 26 Mar 2014 10:31:22 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Emil Ivov <emcho@jitsi.org>, Parthasarathi R <partha@parthasarathi.co.in>
References: <01e601cf423c$57255890$057009b0$@co.in> <00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com> <532F216E.7090400@alum.mit.edu> <532F2D8C.2010104@jitsi.org> <01b701cf4893$afbf0e80$0f3d2b80$@co.in> <CAPvvaaKCxnU=-SAefSDOkwms=Y=g9VoBpq57UPCqvGvYxV1VNw@mail.gmail.com>
In-Reply-To: <CAPvvaaKCxnU=-SAefSDOkwms=Y=g9VoBpq57UPCqvGvYxV1VNw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395844283; bh=0VSlww0/IIcGGQ380lGsyTyH8u/cYEcr3uZgklpxDk4=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ujUfg9HjcKSLaMqwgp1nD/F7xeDcPA6UiJrEZuB+UJZ/JwmpTZ4fZ1f+fLAYb/9iX Q0ku4bCKRwQPy63rJgIiQZc3C/gP9QVbTfZd8AhLSoL2tj7CbMahB8wQ1n1lFGhwJ2 Wgyr02RSBnsbtHOgkGyaaYT4yKQR/+vDHeDzyVJd4UFO92pNm2d/P0OogDGQ8NRXqF ek9YryD7x22USrAC/AkbBhFjlSSkTAAcHrOoVJ82XDjswB6jfqJkya834LrAGPT4so u+PTEjiVz/S0gYmi/f10GjiH6JAxP1GOF1vFtNBThnfXRaS0VIfroKyi/vkaBxm/6h V7dpht3c9agvA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/liqnjAet3NHcdtXR4iUZ47aRuBc
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 26 Mar 2014 14:31:26 -0000

On 3/26/14 1:52 AM, Emil Ivov wrote:
>
> On 26 Mar 2014 2:35 AM, "Parthasarathi R" <partha@parthasarathi.co.in
> <mailto:partha@parthasarathi.co.in>> wrote:
>  >
>  > Hi Emil,
>  >
>  > <snip> > OK, I see. Then the easiest way to tackle this would be to
> mandate
>  > that
>  > > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
>  > > pertaining to.
>  > >
>  > > Does anyone see a problem with that?
>  > </snip>
>  >
>  > I guess that your intention is to pass the corresponding Origin ("o")
> line
>  > in each INFO message by which INFO will be identified for the
> corresponding
>  > SDP by which the ICE candidates are passed.
>
> No, that wasn't my intention but sending the origin line would also work
> indeed. Thanks for pointing it out!
>
> We could actually make that a requirement of the sdpfrag format.

There is a conflict between such rules and defining sipfrag as a generic 
format.  As a generic format, imposing a requirement that it include an 
origin line seems unreasonable. As a requirement for using this for 
trickle ICE it makes sense.

I suggest either:
- leave sipfrag generic, impose presence of origin line as an additional
   requirement when sipfrag is used for trickle ICE
or
- define a content type that is specific to trickle ICE,
   being much more specific about what it contains, and
   with a name appropriate to that usage.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email