Re: [MMUSIC] Text proposal resolving the ICE-"unexpected answer" issue

Ari Keränen <ari.keranen@ericsson.com> Thu, 13 November 2014 10:49 UTC

Return-Path: <ari.keranen@ericsson.com>
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 105EA1A6FEE for <mmusic@ietfa.amsl.com>; Thu, 13 Nov 2014 02:49:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.901
X-Spam-Level:
X-Spam-Status: No, score=-3.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, 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 0jK3bT4zoozc for <mmusic@ietfa.amsl.com>; Thu, 13 Nov 2014 02:49:20 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 714101A6FF2 for <mmusic@ietf.org>; Thu, 13 Nov 2014 02:49:18 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-ce-54648cadef6a
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id F3.D0.24955.DAC84645; Thu, 13 Nov 2014 11:49:17 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.32) with Microsoft SMTP Server id 14.3.174.1; Thu, 13 Nov 2014 11:49:16 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id ACF61110207; Thu, 13 Nov 2014 12:49:16 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 01F585F3DE; Thu, 13 Nov 2014 12:49:38 +0200 (EET)
Received: from dhcp-9749.meeting.ietf.org (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id CB4BE5F3A7; Thu, 13 Nov 2014 12:49:36 +0200 (EET)
Message-ID: <54648CB1.6050401@ericsson.com>
Date: Thu, 13 Nov 2014 00:49:21 -1000
From: =?windows-1252?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
References: <F81CEE99482EFE438DAE2A652361EE121E224DF2@MCHP04MSX.global-ad.net>
In-Reply-To: <F81CEE99482EFE438DAE2A652361EE121E224DF2@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUyM+Jvje7anpQQg69/BC2mLn/MYnFy5zZm ByaPJUt+Mnls73nMEsAUxWWTkpqTWZZapG+XwJWxfOlzxoLbChXfF59kamDskOpi5OCQEDCR OH5JrYuRE8gUk7hwbz1bFyMXh5DAEUaJ5cuvs4IkhAQ2MEo0vI+ASOxhlGh/uZQZIrGWUWLH BkWIBJD9YusdRpAEr4C2xL8tG8GKWARUJc4e+cYCYrMJOErcfvgSbKqoQLLEmq2T2CHqBSVO znwCViMiICOxd9NmsF5mAR2JRR83gdnCAoESf7atZIRY7Cextf0dWJxTwF/i+bTfrCDfMAvY SzzYWgbRKi/RvHU2M8RnahJXz22CullV4uq/V4wTGEVnIdk8C6F7FpLuBYzMqxhFi1OLk3LT jYz1Uosyk4uL8/P08lJLNjECo+Hglt+qOxgvv3E8xCjAwajEw7tBLiVEiDWxrLgy9xCjNAeL kjjvwnPzgoUE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwJgnyCh7f2LV2WW1ID8+/aXnhRUGH uwwTXrk63jlx9dLOuwFflBtagio2B/4WXxz5nU3uoYva9+PcZxldlC3cpfMe8jmcuCyU9kq9 79XL5ezG36Tr6ovXHpD5+8FpR9/96aoXT23lfz5HL77HhbPsdpBz/dbltz0n1Amssu73UeXc dEV7QXaGEktxRqKhFnNRcSIAcTaX3mcCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/TDcSxZMMZ0AZ6Zk1ec-3_mAm9K0
Subject: Re: [MMUSIC] Text proposal resolving the ICE-"unexpected answer" issue
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: Thu, 13 Nov 2014 10:49:22 -0000

I think this text proposal is good and would not mind adding it to the 
ICE SDP draft. Does anyone else have comments on this?


Cheers,
Ari (as individual contributor)

On 10/7/14 3:26 AM, Stach, Thomas wrote:
> All,
>
> at the last MMUSIC session I was asked to provide some text resolving
> the "unexpected answer" issue that I brought up on the MMUSIC list.
>
> It took a while, but below is what I propose to include in
> draft-ietf-mmusic-ice-sip-sdp.
>
> Currently there thee section dealing with the initial SDP offer/answer
> exchange.
>
> 3.  Sending the Initial Offer
>
> 4.  Receiving the Initial Offer
>
> 5.  Receipt of the Initial Answer
>
> Now, section 9 deals with  subsequent SDP offer/answer exchanges, where
> the new text needs to go in.
>
> It has subsections (9.1, 9.2) equivalent to 3 and 4 above, however,
> nothing equivalent to 5.
>
> Thus, I think the existing 9.3 should be moved in new subsection 9.4 and
> the following text should be introduced:
>
> 9.3 <#section-9.3>.  Receiving the answer for a subsequent offer
>
> Some deployments of ICE include e.g. SDP-Modifying Signaling-only B2BUAs
> [RFC7092] that modify the SDP body during the subsequent offer/answer
> exchange. With the B2BUA being ICE-unaware a subsequent answer might be
> manipulated and might not include SDP candidates although the initial
> answer did.
>
> An example of a situation where such an “unexpected” answer might be
> experienced appears when such aB2BUA introduces a media server during
> call hold using 3^rd party call-control procedures. Omitting further
> details how this is done this could result in an answer being received
> at the holding UA that was constructed by the B2BUA. With the B2BUA
> being ICE-unaware that answer would not include SDP candidates.
>
> Receiving an answer without ICE attributes in this situation might be
> unexpected, but would not necessarily impair the user experience.
>
> In addition to procedures for the expected answer, the following
> sections give also some advice how to recover from the unexpected situation.
>
> 9.3.1 Procedures for All Implementations
>
> When receiving an answer within an existing session for a subsequent
> offer as specified in 9.1.2.2, an agent MUST verify ICE support as
> specified in Section 5.1.
>
> 9.3.1.1 ICE restarts
>
> If ICE support is indicated in the SDP answer, the agent MUST perform
> ICE restart procedures as specified in section 9.4 (the existing section
> 9.3) below.
>
> If ICE support is no longer indicated in the SDP answer, the agent MUST
> fall-back to RFC 3264 procedures and SHOULD NOT drop the dialog just
> because of missing ICE support. If the agent sends a new offer later on
> it SHOULD perform an ICE restart as specified in 9.1.1.1.
>
> 9.3.1.2 Existing Media Streams with ICE Running
>
> If ICE support is indicated in the SDP answer, the agent MUST continue
> ICE procedures as specified in section 9.4.1.4 (the existing section
> 9.3.1.4) below.
>
> If ICE support is no longer indicated in the SDP answer, the agent MUST
> abort the ongoing ICE processing and fall-back to RFC 3264 procedures.
> The agent SHOULD NOT drop the dialog just because of missing ICE
> support. If the agent sends a new offer later on, it SHOULD perform an
> ICE restart as specified in 9.1.1.1.
>
> 9.3.1.3 Existing Media Streams with ICE Completed
>
> If ICE support is indicated in the SDP answer and if the answer conforms
> to 9.2.2.3, the agent MUST remain in the ICE Completed state.
>
> If ICE support is no longer indicated in the SDP answer, the agent MUST
> fall-back to RFC 3264 procedures and SHOULD NOT drop the dialog just
> because of this unexpected answer. Once the agent sends a new offer
> later on it MUST perform an ICE restart.
>
> Existing 9.3 à*9.4* <#section-9.3>.  Updating the Check and Valid Lists
>
> ….
>
> I’d like to get your feedback, if  that proposal is reasonable.
>
> Regards
>
> Thomas
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>