Re: [AVT] WGLC comments on draft-ietf-avt-ports-for-ucast-mcast-rtp-11: Part 2 Unicast RTP session Termination

Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 19 January 2011 15:51 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 1DD493A6FEF for <avt@core3.amsl.com>; Wed, 19 Jan 2011 07:51:20 -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 YidhgQcOR38S for <avt@core3.amsl.com>; Wed, 19 Jan 2011 07:51:18 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 4CD973A7011 for <avt@ietf.org>; Wed, 19 Jan 2011 07:51:18 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-c6-4d370915b171
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 38.E6.13987.519073D4; Wed, 19 Jan 2011 16:53:58 +0100 (CET)
Received: from [147.214.183.170] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.2.234.1; Wed, 19 Jan 2011 16:53:44 +0100
Message-ID: <4D370908.2050103@ericsson.com>
Date: Wed, 19 Jan 2011 16:53:44 +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: <4D307AE7.9090308@ericsson.com> <04CAD96D4C5A3D48B1919248A8FE0D540E16DA39@xmb-sjc-215.amer.cisco.com> <4D341FDB.2050507@ericsson.com> <04CAD96D4C5A3D48B1919248A8FE0D540E16DCA3@xmb-sjc-215.amer.cisco.com> <4D345C68.5030402@ericsson.com> <04CAD96D4C5A3D48B1919248A8FE0D540E16DD65@xmb-sjc-215.amer.cisco.com> <4D36F366.8090304@ericsson.com> <04CAD96D4C5A3D48B1919248A8FE0D540E16E1C0@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540E16E1C0@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 2 Unicast RTP session Termination
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: Wed, 19 Jan 2011 15:51:20 -0000

Ali C. Begen (abegen) skrev 2011-01-19 16:22:
> OK, let's not describe a specific method, and the following text:
> 
> A specification using the Token-based authentication described in this document is REQUIRED to discuss the methods and rules for terminating/ending the unicast session.
> 
> I propose to add the text above to the 5th parag. of section 3 as follows:
> 
>    Upon successful validation and once the unicast session is
>    established, all the RTP and RTCP rules specified in [RFC3550] and
>    other relevant specifications also apply in this session until it is
>    terminated.  >>>
> 

Well based on this, I wouldn't come to the conclusion that one can stop
sending RTCP as server at all unless there has been some explicit
signalling for termination. this is Probably fine for the general
introduction. And it do leave the question of termination wide open.

So, I don't see other than that you have to discuss the termination in
the draft.

"The Unicast RTP session created using the port mapping method can be
explicitly terminated by procedures specified by the using application
or extension. Any unicast RTP session created using this method may be
terminated by a timeout procedure. If either client or Retransmission
Server has not seen any RTCP from any SSRC used by a peer for 5 regular
transmission intervals, the client or server SHOULD consider the RTP
session as terminated, and in that case not send any RTP or RTCP traffic
in the future. The client will have to establish a new unicast session
if required.

If no procedure for explicit termination exist, the client MAY stop
sending RTCP to the Retransmission Server to accomplish session
termination. The Server SHALL NOT stop sending RTCP until the unicast
RTP session is terminated. If Token Verification is signaled to be
allowed also on in the unicast RTP session, i.e. the RTCP messages sent
from c2 to P4, the client SHOULD prefer to terminate by sending RTCP BYE
on all SSRCs it has used in this unicast RTP session."

I think this works fine, and is way better than having no specification
at all.

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
----------------------------------------------------------------------