Re: [AVT] WGLC comments on draft-ietf-avt-ports-for-ucast-mcast-rtp-11: Part 7 Persistent Errors

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 17 January 2011 10:17 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B271C3A6E48 for <avt@core3.amsl.com>; Mon, 17 Jan 2011 02:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.491
X-Spam-Level:
X-Spam-Status: No, score=-106.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vohzd23dKl3X for <avt@core3.amsl.com>; Mon, 17 Jan 2011 02:17:15 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 921EE3A6D44 for <avt@ietf.org>; Mon, 17 Jan 2011 02:17:15 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-bb-4d3417c4a457
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 1B.F1.13987.4C7143D4; Mon, 17 Jan 2011 11:19:48 +0100 (CET)
Received: from [147.214.183.170] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.2.234.1; Mon, 17 Jan 2011 11:19:48 +0100
Message-ID: <4D3417C3.4090100@ericsson.com>
Date: Mon, 17 Jan 2011 11:19:47 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
References: <4D30844F.8020508@ericsson.com> <04CAD96D4C5A3D48B1919248A8FE0D540E16DA3F@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540E16DA3F@xmb-sjc-215.amer.cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-avt-ports-for-ucast-mcast-rtp@tools.ietf.org" <draft-ietf-avt-ports-for-ucast-mcast-rtp@tools.ietf.org>, IETF AVT WG <avt@ietf.org>
Subject: Re: [AVT] WGLC comments on draft-ietf-avt-ports-for-ucast-mcast-rtp-11: Part 7 Persistent Errors
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2011 10:17:16 -0000

Ali C. Begen (abegen) skrev 2011-01-14 19:34:
> 
> 
>> -----Original Message-----
>> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
>> Sent: Friday, January 14, 2011 6:14 PM
>> To: IETF AVT WG; draft-ietf-avt-ports-for-ucast-mcast-rtp@tools.ietf.org
>> Subject: WGLC comments on draft-ietf-avt-ports-for-ucast-mcast-rtp-11: Part 7 Persistent Errors
>>
>> Hi,
>>
>> This is a continuation of the issue 15A from the 08 review.
>>
>> The issue is when a client should consider an error to be persistent, or
>> at least not short time temporarily or resolvable. If a client continues
>> to get Mapping responses with errors after having tried several times.
>> Maybe it should do exponential back-off. Maybe it should update its
>> session description. Similar for Verification Requests.
>>
>> Some recommendation about such behavior I think has clear benefit and
>> reduced uncertainty in behavior by clients.
> 
> This sounds like a good suggestion. How about adding the following to the end of section 6:
> 
> If a client receives a Port Mapping Response message with an invalid Token (i.e., the relative expiration time is set to zero) two or more times for a particular Port Mapping Request message, or the client receives a Token Verification Failure message two or more times for the same Token Verification Request message, the client SHOULD do the following:
> 1- Check whether the session description has been updated or not. If it was updated, act according to the new session description.
> 2- Exponentially back-off for the third and subsequent attempts.
> 
> Exponential back-off does not apply when the client sends a Port Mapping Request or Token Verification Request message to a new address and/or port.
> 
> Let me know if this text is good or you wanna modify it.

Good enough I think.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------