[rtcweb] The meaning of SDP_PRANSWER
"Henry Lum" <Henry.Lum@genesyslab.com> Mon, 16 April 2012 15:52 UTC
Return-Path: <Henry.Lum@genesyslab.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA2C921F8669 for <rtcweb@ietfa.amsl.com>; Mon, 16 Apr 2012 08:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jeM0qysgQW+L for <rtcweb@ietfa.amsl.com>; Mon, 16 Apr 2012 08:52:58 -0700 (PDT)
Received: from relay-out2.dc.genesyslab.com (relay-out2.dc.genesyslab.com [198.49.180.221]) by ietfa.amsl.com (Postfix) with ESMTP id 2030721F866A for <rtcweb@ietf.org>; Mon, 16 Apr 2012 08:52:58 -0700 (PDT)
Received: from g2.genesyslab.com (g2.genesyslab.com [192.168.20.138]) by relay-out2.dc.genesyslab.com (8.13.8+Sun/8.13.8) with ESMTP id q3GFqvlg003706 for <rtcweb@ietf.org>; Mon, 16 Apr 2012 08:52:57 -0700 (PDT)
Received: from NAHALD.us.int.genesyslab.com ([192.168.20.92]) by g2.genesyslab.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 16 Apr 2012 08:52:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD1BE8.FE4C7434"
Date: Mon, 16 Apr 2012 08:52:56 -0700
Message-ID: <059AF07365DC474393A19A3AF187DF74086657DB@NAHALD.us.int.genesyslab.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: The meaning of SDP_PRANSWER
Thread-Index: Ac0b6P2LYYaJABysS36nnM28Gg2Lzg==
From: Henry Lum <Henry.Lum@genesyslab.com>
To: rtcweb@ietf.org
X-OriginalArrivalTime: 16 Apr 2012 15:52:58.0000 (UTC) FILETIME=[FE836900:01CD1BE8]
Subject: [rtcweb] The meaning of SDP_PRANSWER
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 15:52:59 -0000
It's unclear to me what the purpose of SDP_PRANSWER is really for and why it needs to be there. Originally I thought it was meant for early media, but section 6.1.4 paragraph 3 says that it should not result in starting of media transmission. Is there a reason to provide an answer before media is ready to be transmitted? There are separate handles for processing ICE candidates so I don't see a need to have provisional answers. I am not proposing PRANSWER for handling early media though, since I believe early media is more of an application level issue (it's more like late-billing on the application side) and should be considered as a separate offer/answer if needed. Regards, Henry
- [rtcweb] The meaning of SDP_PRANSWER Henry Lum
- Re: [rtcweb] The meaning of SDP_PRANSWER Justin Uberti
- Re: [rtcweb] The meaning of SDP_PRANSWER Henry Lum