Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling - More-coming and final answer (Section 5.2.3)

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 03 November 2011 19:33 UTC

Return-Path: <christer.holmberg@ericsson.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 39FC61F0CAB for <rtcweb@ietfa.amsl.com>; Thu, 3 Nov 2011 12:33:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.305
X-Spam-Level:
X-Spam-Status: No, score=-6.305 tagged_above=-999 required=5 tests=[AWL=0.294, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 pvL3SraLHyx1 for <rtcweb@ietfa.amsl.com>; Thu, 3 Nov 2011 12:33:56 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 3535B1F0C3B for <rtcweb@ietf.org>; Thu, 3 Nov 2011 12:33:56 -0700 (PDT)
X-AuditID: c1b4fb39-b7cb2ae000001bd8-00-4eb2eca25aa3
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 8F.77.07128.2ACE2BE4; Thu, 3 Nov 2011 20:33:55 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.57]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Thu, 3 Nov 2011 20:33:54 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: 'Cullen Jennings' <fluffy@cisco.com>
Date: Thu, 3 Nov 2011 20:33:54 +0100
Thread-Topic: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling - More-coming and final answer (Section 5.2.3)
Thread-Index: AcyOwQK8yjsjgFbmTVywWcPfVlw13QLnF5kg
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852235789602@ESESSCMS0356.eemea.ericsson.se>
References: <15B0E3AD-3086-499A-8E79-7AE58B3376C4@cisco.com> <7F2072F1E0DE894DA4B517B93C6A058522341F4AB9@ESESSCMS0356.eemea.ericsson.se> <E08E5E86-56BE-417D-A5C0-03AAA4A375CB@cisco.com>
In-Reply-To: <E08E5E86-56BE-417D-A5C0-03AAA4A375CB@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: Jonathan Rosenberg <jonathan.rosenberg@skype.net>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling - More-coming and final answer (Section 5.2.3)
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: Thu, 03 Nov 2011 19:33:57 -0000

Hi, 

>> Q2. Are there restrictions when it comes to changing information in a non-final 
>> answer and a final answer? Or, can the final answer be completely different from 
>> previously sent non-final ANSWERS? In "legacy" O/A there are restrictions.
>
> Any answer has to be a valid answer for the offer but other than that, no restrictions, 
> so the final answer can change everything from an earlier one. 

Is there a reason/use-case/requirement why we need to allow that? As far as I know, the reason behind this is ICE.

Regards,

Christer



>> -----Original Message-----
>> From: rtcweb-bounces@ietf.org
>> [mailto:rtcweb-bounces@ietf.org] On Behalf Of Cullen Jennings
>> Sent: 15. lokakuuta 2011 6:09
>> To: rtcweb@ietf.org; public-webrtc@w3.org
>> Cc: Jonathan Rosenberg
>> Subject: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling
>> 
>> 
>> Jonathan and I submitted a new draft on setting up media based on the 
>> SDP Offer/Answer model. The ASCII flows are a bit hard to read so 
>> until I update them, I recommend reading the PDF version at
>> 
>> http://tools.ietf.org/pdf/draft-jennings-rtcweb-signaling-00.pdf
>> 
>> Clearly the draft is an early stage but we plan to revise it before 
>> the deadline for the IETF 82. Love to get input - particularly on if 
>> this looks like generally the right direction to go.
>> 
>> 
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb