Re: [Stox] Stox-media: Should XEP-176 translations have Require: ice?

Peter Saint-Andre <stpeter@stpeter.im> Thu, 20 March 2014 03:45 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E99241A0823 for <stox@ietfa.amsl.com>; Wed, 19 Mar 2014 20:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 vRAURYAsXnLY for <stox@ietfa.amsl.com>; Wed, 19 Mar 2014 20:45:40 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B9D0A1A0345 for <stox@ietf.org>; Wed, 19 Mar 2014 20:45:40 -0700 (PDT)
Received: from aither.local (unknown [24.8.184.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DC7EE4032A; Wed, 19 Mar 2014 21:45:31 -0600 (MDT)
Message-ID: <532A645A.3080605@stpeter.im>
Date: Wed, 19 Mar 2014 21:45:30 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Jonathan Lennox <jonathan@vidyo.com>, "stox@ietf.org" <stox@ietf.org>
References: <26E25338-948C-43FA-A0AE-880BD1CB49B0@vidyo.com>
In-Reply-To: <26E25338-948C-43FA-A0AE-880BD1CB49B0@vidyo.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/stox/7XDenhhxGJUOK0DdyiCgTlKJwo0
Subject: Re: [Stox] Stox-media: Should XEP-176 translations have Require: ice?
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox/>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Mar 2014 03:45:42 -0000

Once again, my apologies for the slow reply.

On 1/9/14, 10:31 AM, Jonathan Lennox wrote:
> I was thinking about the issue that unlike RFC 5245, XEP-176's
> definition of ICE doesn't support fallback to a non-ICE mode.

Correct.

> It occurred to me that SIP has a way of saying "do ICE, or fail the
> call": putting a "Require: ice" SIP option tag (from RFC 5768) in the
> SIP INVITE.
>
> Should we recommend this?  It clearly has the right semantics, and
> will prevent interop failure when a non-ICE SIP endpoint answers a
> XEP-176 Jingle call.

Theoretically that makes sense.

> My concern, though, is whether there are a) endpoints that implement
> RFC 5245 but not RFC 5768, or b) non-media-terminating B2BUAs that
> will pass ICE parameters through, but will reject calls with Require
> headers they don't know.  In either of these cases, adding this
> Require header would cause a call that would otherwise have worked to
> fail.

That would be bad.

> Any thoughts, especially from folks who know the state of deployed
> SIP better than I do?

Inquiring minds want to know. :-)

Peter