IETF Logo Mail Archive

[rtcweb] Clarification on offer/answer in jsep-01

Kaiduan Xie <kaiduanx@gmail.com> Tue, 28 August 2012 01:40 UTC

Return-Path: <kaiduanx@gmail.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 E36D721F8495 for <rtcweb@ietfa.amsl.com>; Mon, 27 Aug 2012 18:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tqghZRFkEJFZ for <rtcweb@ietfa.amsl.com>; Mon, 27 Aug 2012 18:40:53 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 36E2A21F8493 for <rtcweb@ietf.org>; Mon, 27 Aug 2012 18:40:53 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so10772133obb.31 for <rtcweb@ietf.org>; Mon, 27 Aug 2012 18:40:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=RQDComcINKZtDubGj+kEGv2c/RMYl7SRSpEi3MRljM4=; b=EV1a34Zc0j1Qo3NiU1n0rD2E0paZ6H8ifzRRjBbnzuvdR0JFmAI+kWQmslfpN7ZEpv RlcrySm/UpxdjOinZyKd4BTnmGKO4Db5TsiO3KykZjScsCdb4ykOZK+l7y1/Wkpk0jrC xXdf0NfWGxuRsqKjwsvlPfiwQe/Rgle1W4mWiMGHMwwoCZ8y6Ddqyvgx6QeR5rIzPoTq Bh8pS+7mA0Yb0rfmBCF/g1pH0DI7YqzAwclztSPUlM4qBcx2YIbTXV3NGraaebDfDHsW drVu+N1ChbYpMpinXlBYO1xcAcRyaMS7OV2rAnQ/ML9AYyI8gtWJwVM/SuqpOTKS57IV a1Lg==
MIME-Version: 1.0
Received: by 10.60.171.174 with SMTP id av14mr11716566oec.61.1346118052575; Mon, 27 Aug 2012 18:40:52 -0700 (PDT)
Received: by 10.76.23.129 with HTTP; Mon, 27 Aug 2012 18:40:52 -0700 (PDT)
Date: Mon, 27 Aug 2012 21:40:52 -0400
Message-ID: <CACKRbQfXam_QqsUdMif-zR0uuiM6VFwP-VDy0q7f_r6gdV_-VQ@mail.gmail.com>
From: Kaiduan Xie <kaiduanx@gmail.com>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [rtcweb] Clarification on offer/answer in jsep-01
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: Tue, 28 Aug 2012 01:40:54 -0000

Hi all,

I do not understand the statement below from 4.2. Session Descriptions
and State Machine

"As in [RFC3264], an offerer can send an offer, and update it as long
as it has not been answered."

However, per rfc3264 http://tools.ietf.org/html/rfc3264 section 4
Protocol Operation,

"At any time, either agent MAY generate a new offer that updates the
 session. However, it MUST NOT generate a new offer if it has
 received an offer which it has not yet answered or rejected.
 Furthermore, it MUST NOT generate a new offer if it has generated a
 prior offer for which it has not yet received an answer or a
 rejection."

Please look the last sentence. Can anyone explain why JSEP introduces
something different than RFC3264 please?

Best regards,

/Kaiduan

v2.23.0 | Report a Bug | By Email