IETF Logo Mail Archive

Re: [MMUSIC] Offer/Answer PT Questions - text proposal

"DOLLY, MARTIN C" <md3135@att.com> Wed, 02 March 2016 22:47 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 4E7041B3369 for <mmusic@ietfa.amsl.com>; Wed, 2 Mar 2016 14:47:11 -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 NphnHqHpLHjJ for <mmusic@ietfa.amsl.com>; Wed, 2 Mar 2016 14:47:09 -0800 (PST)
Received: from mx0b-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 86E8E1B3362 for <mmusic@ietf.org>; Wed, 2 Mar 2016 14:47:09 -0800 (PST)
Received: from pps.filterd (m0049458.ppops.net [127.0.0.1]) by m0049458.ppops.net-00191d01. (8.15.0.59/8.15.0.59) with SMTP id u22MiKRA036865; Wed, 2 Mar 2016 17:46:58 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049458.ppops.net-00191d01. with ESMTP id 21b84y9pjh-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 02 Mar 2016 17:46:58 -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 u22Mkv3I023294; Wed, 2 Mar 2016 17:46:58 -0500
Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u22Mkos1023213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 2 Mar 2016 17:46:52 -0500
Received: from MISOUT7MSGHUBAB.ITServices.sbc.com (MISOUT7MSGHUBAB.itservices.sbc.com [130.9.129.146]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Wed, 2 Mar 2016 22:46:38 GMT
Received: from MISOUT7MSGUSRDB.ITServices.sbc.com ([169.254.2.77]) by MISOUT7MSGHUBAB.ITServices.sbc.com ([130.9.129.146]) with mapi id 14.03.0248.002; Wed, 2 Mar 2016 17:46:37 -0500
From: "DOLLY, MARTIN C" <md3135@att.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] Offer/Answer PT Questions - text proposal
Thread-Index: AdFv1i1li4hZHAkDRvW27hH21f813wARGIiAAAEzHQAAFHhLgAANDP0AAABf9wAAANkcgAABPnAAAACT0gAAARuRgAAArliAACAJAYAADgPBAABONv0AABK4WIAAAjCagAAJzjpQAGq7knAACx9ugAAAKd8A//+xN30=
Date: Wed, 02 Mar 2016 22:46:37 +0000
Message-ID: <29D2D9FC-C1C0-4E99-89C0-521D85972974@att.com>
References: <7594FB04B1934943A5C02806D1A2204B37E425AB@ESESSMB209.ericsson.se> <56D09563.9040509@alum.mit.edu> <CAD5OKxvwJwKoaaMHDDA8AKYdd2Rc8vOK_dnOftvozX+FbfqHOQ@mail.gmail.com> <56D1CA6C.70700@alum.mit.edu> <CAD5OKxt5jp44Saop+ssdPENBsRBNbkFUXFphZHMwqYDFLNWFpg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37E4BD38@ESESSMB209.ericsson.se> <56D463A3.8070007@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E4D5E9@ESESSMB209.ericsson.se> <56D4B1F1.2070706@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E4D951@ESESSMB209.ericsson.se> <66F2264B-3CA3-4650-88B6-89FC64D5FD29@csperkins.org> <7594FB04B1934943A5C02806D1A2204B37E4DB7C@ESESSMB209.ericsson.se> <56D4C0F5.50901@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37E4EAD1@ESESSMB209.ericsson.se> <56D5CAA0.2060901@alum.mit.edu> <CAD5OKxtdmhW-opmp2TQou5wYbz70FdUvftr1PAZb9YiW4crevA@mail.gmail.com> <56D5E81F.2040306@alum.mit.edu> <CAD5OKxtXzhP9L-V6O5NVtCN4aQHy9X8Fpkc0_xKdWmtR03h4KQ@mail.gmail.com> <56D5EE38.2060706@alum.mit.edu> <C57049C8 -BAFE-4FAB-847D-CF3640AACAE3@csperkins.org> <7594FB04B1934943A5C02806D1A2204B37E54995@ESESSMB209.ericsson.se>, <AFCC6C46-B945-4749-B20A-AB7EFBC2345F@csperkins.org>
In-Reply-To: <AFCC6C46-B945-4749-B20A-AB7EFBC2345F@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="Windows-1252"
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-03-02_13:, , 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-1603020411
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/vG2I-mdEMH6Ju0feC3YyQyQwFkk>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Offer/Answer PT Questions - text proposal
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: Wed, 02 Mar 2016 22:47:11 -0000

Now that I see thread of agreement on a few points, who dis agrees

And Paul, no tangents 

Martin C Dolly
Lead Member of Technical Staff
Core & Government/Regulatory Standards 
AT&T
Cell: 609-903-3360
Email: md3135@att.com

> On Mar 2, 2016, at 5:28 PM, Colin Perkins <csp@csperkins.org> wrote:
> 
> 
>> On 2 Mar 2016, at 22:23, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>> 
>> Hi,
>> 
>>>> *If* it is really the case that there is no relationship between O/A and the lifetime of RTP sessions, then we have 
>>>> some work to do to sort out what the relationship is between what is in the O/A and what is in the RTP session.
>>>> 
>>>> IIUC, in the case where the is no RTP session prior an offer, the O/A must at least establish some initial PT bindings for the session-to-be.
>>>> 
>>>> (I have a feeling that what we are discussing is quite fundamental, and I find it shocking if it hasn't been considered in the past.)
>>>> 
>>>> Colin - your insight would be helpful here.
>>> 
>>> I don’t have good insights here. I’ve long had the impression there are conflicts between the o/a rules and the RTP rules, but I’m insufficiently familiar with o/a to identify or resolve them.
>> 
>> What started this discussion was the uncertainty whether the same PT could be used for *different* codecs, per direction. The answer to that seem to be no: you can use different PTs for the same codec, but you cannot use the same PT for different codecs.
> 
> I agree with that answer.
> 
>> Also, I have also heard that a new RTP session does NOT require new PT bindings.
> 
> Again, I agree. The PT binding as per RTP session: if you start a new RTP session, you can use different PT values, but you’re not required to do so (and generally don’t, since the static PT assignments are re-used).
> 
>> So, I may have missed something, but I fail to see any conflicts...
> 
> In that case, good! As I say, I’m insufficiently familiar with o/a to know for sure.
> 
> -- 
> Colin Perkins
> https://csperkins.org/
> 
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email