Re: [MMUSIC] [tram] FW: New Version Notification for draft-wing-mmusic-ice-mobility-06.txt

Oleg Moskalenko <mom040267@gmail.com> Mon, 10 February 2014 17:57 UTC

Return-Path: <mom040267@gmail.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 1DDB81A0402; Mon, 10 Feb 2014 09:57:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 tPHi2fmkJEKH; Mon, 10 Feb 2014 09:57:19 -0800 (PST)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7EEE11A0326; Mon, 10 Feb 2014 09:57:19 -0800 (PST)
Received: by mail-pd0-f179.google.com with SMTP id fp1so5983231pdb.24 for <multiple recipients>; Mon, 10 Feb 2014 09:57:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OGJYLjCJJ/5iTPNmAQBVdX7Dub/K/s8FqrKXMPX9v5I=; b=fPAo8h2+JTxDEKlNKdIHREyezdxD+bB7gqjNz2V3cmmrNO0HvvWpnGtY8+cxoHW5ij wcxyee1UpeUvrtLPtWqf5YQxBkp/RSOtDSqu4EAmgDAMyZ5oNcxzP2Z06wr9IDtLXOB1 9+cG4nN7f6rLLqcFY5LPcfQdG8RTMwYbOY4R1+gZX2C4j1HNA4soJnwd7PM8oOfJ4R0J 1N+R8vewOW1DrMJTXgB+yhVGXF8DlyaS96FgvapTv9mCAaNtD301nDFDcF83dF63QKA5 zj3WfFjTNSEieTjvq10+WevoGbts4Cp/UGn1QkC8gBIXPjcbvyA8ART8fylbXjDwoRMf ogRg==
MIME-Version: 1.0
X-Received: by 10.68.139.100 with SMTP id qx4mr10528421pbb.144.1392055039260; Mon, 10 Feb 2014 09:57:19 -0800 (PST)
Received: by 10.68.147.131 with HTTP; Mon, 10 Feb 2014 09:57:19 -0800 (PST)
In-Reply-To: <913383AAA69FF945B8F946018B75898A242AB165@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A242AB165@xmb-rcd-x10.cisco.com>
Date: Mon, 10 Feb 2014 09:57:19 -0800
Message-ID: <CALDtMr+edNejRACb3gqtiemtEWEJKmTtT0bmoEjuPt4z8z_nwQ@mail.gmail.com>
From: Oleg Moskalenko <mom040267@gmail.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Content-Type: multipart/alternative; boundary="001a11c361d21f7f0a04f21112d9"
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Subject: Re: [MMUSIC] [tram] FW: New Version Notification for draft-wing-mmusic-ice-mobility-06.txt
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: Mon, 10 Feb 2014 17:57:21 -0000

Hi Tiru

I agree.

Thanks
Oleg

On Mon, Feb 10, 2014 at 4:09 AM, Tirumaleswar Reddy (tireddy) <
tireddy@cisco.com> wrote:

>   Comment: I am not sure that 501 is the right code to be used. In SIP
> and HTTP, 5xx errors are usually about a server code problem of some sort;
> 501 means "not implemented". That may be not exactly accurate. A
> mobility-aware TURN server may reject the request simply because the
> administrator does not allow it., and the server did not encounter an
> error. The reason why the server reject the request is rather "not allowed"
> (which is the error code 405).
>
> [TR] we can replace 501 error code with 403
>
> May be be, the right approach would be to introduce two separate error
> codes here: 405 "not allowed" (the server implements mobility but the
> administrator forbade it) or 501 "not implemented" (the server knows about
> mobility but it has no implementation for that).
>
> [TR] Not sure if "not implemented" error will be of any help. TURN server
> if it knows about mobility but has not implemented the functionality then
> it can continue to ignore MOBILITY-TICKET in the request and not send
> MOBILITY-TICKET in the response.
>
>