Re: [MMUSIC] Offer/Answer PT Questions

"DOLLY, MARTIN C" <md3135@att.com> Mon, 22 February 2016 22:43 UTC

Return-Path: <md3135@att.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 2EF361AC416 for <mmusic@ietfa.amsl.com>; Mon, 22 Feb 2016 14:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.266
X-Spam-Level:
X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7] 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 52Hm_PApdx1I for <mmusic@ietfa.amsl.com>; Mon, 22 Feb 2016 14:43:22 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A13A1AC415 for <mmusic@ietf.org>; Mon, 22 Feb 2016 14:43:22 -0800 (PST)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.15.0.59/8.15.0.59) with SMTP id u1MMY8Ac044146; Mon, 22 Feb 2016 17:43:18 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049295.ppops.net-00191d01. with ESMTP id 216n07p5km-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 22 Feb 2016 17:43:17 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u1MMhGxt009133; Mon, 22 Feb 2016 17:43:16 -0500
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u1MMhAEh009050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 22 Feb 2016 17:43:13 -0500
Received: from MISOUT7MSGHUBAD.ITServices.sbc.com (MISOUT7MSGHUBAD.itservices.sbc.com [130.9.129.148]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Mon, 22 Feb 2016 22:43:05 GMT
Received: from MISOUT7MSGUSRDB.ITServices.sbc.com ([169.254.2.77]) by MISOUT7MSGHUBAD.ITServices.sbc.com ([130.9.129.148]) with mapi id 14.03.0248.002; Mon, 22 Feb 2016 17:43:05 -0500
From: "DOLLY, MARTIN C" <md3135@att.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Offer/Answer PT Questions
Thread-Index: AdFrl0kuiZ+JG67LRQCl2lgEejcpMAAlR48AAGjC9oAAAUJQAAAA/2gAAAC+cAAABlmFYA==
Date: Mon, 22 Feb 2016 22:43:04 +0000
Message-ID: <E42CCDDA6722744CB241677169E8365615E45C92@MISOUT7MSGUSRDB.ITServices.sbc.com>
References: <E42CCDDA6722744CB241677169E8365615E419C0@MISOUT7MSGUSRDB.ITServices.sbc.com> <56C89F86.7020401@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E35E33@ESESSMB209.ericsson.se> <CAD5OKxsDGhSA1WpzVVEvdd0CQdbnFn+ST+ZP_=aYVWBVdKKs4g@mail.gmail.com> <56CB6DB6.30802@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E36086@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37E36086@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.225.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-02-22_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1601100000 definitions=main-1602220249
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/anww7KhjgKm_AQZVZ_nyJ7UrfBY>
Subject: Re: [MMUSIC] Offer/Answer PT Questions
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: <https://mailarchive.ietf.org/arch/browse/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, 22 Feb 2016 22:43:24 -0000

Paul,

I agree with Christer, this needs to be fixed. We are doing interop testing with other carriers for VoIP interconnection, and this is  a major issue.

Fixing this would help accelerate VoIP interconnection.

Regards,

Martin

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Monday, February 22, 2016 3:42 PM
To: Paul Kyzivat <pkyzivat@alum.mit.edu>; mmusic@ietf.org
Subject: Re: [MMUSIC] Offer/Answer PT Questions

Hi,

>> One thing that bothered me here is that PT cannot be reused for the 
>> duration of the session. It is probably safe to reuse the PT after 
>> session modification if PT is no longer used. I always felt that 
>> dynamic PT reuse criteria were much stricter then realistically possible or needed.
>...
>> I think the most important criteria here is that there should be no 
>> ambiguity regarding how an RTP packet with particular PT should be 
>> decoded. If it is guaranteed that there are no packets sent between 
>> Alice and Bob with PT 111 over some reasonable time interval (couple 
>> of network round trip times), then PT 111 can be safely reused. If, 
>> in this scenario Bob's end point knows that it was not sending 
>> anything with payload 111 recently, then it can safely reuse this payload.
>> Alice could not be sending anything with payload 111 since Bob did 
>> not accept it previously. On the other hand, Bob must not reuse PT 
>> 100 for, let's say, CN, since there are packets with this payload in 
>> flight and this will create decoding ambiguity. To conclude, an end 
>> point should be able to safely reuse any PT that it is not currently 
>> accepting or was not sending or accepting for at least a few network round trip intervals.
>
> I agree that this is how it *should* be. I don't know if we can change 
> this safely or not. It seems likely to me that some implementations might be freaked out by this. It is worth discussion.
>
> There are cases where it really isn't feasible to meet the current 
> requirement. In particular, when a transfer is done via 3pcc the transferee won't know the history of past PT usage. So I expect in cases such cases the rule is commonly broken.
>
> Coming up with clear rules for when PTs can be recycled could be a challenge.

Well, I think we have to try, because these kind of issues keep causing problems.

The fact that something may freak about because we fix it is not a reason for not fixing it :)

Regards,

Christer

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic