Re: [rtcweb] "pranswer" be applied as an update to a previously sent "answer"?

Justin Uberti <juberti@google.com> Thu, 21 November 2013 20:26 UTC

Return-Path: <juberti@google.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84FF01AE2D0 for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 12:26:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001] 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 w84wFppv-520 for <rtcweb@ietfa.amsl.com>; Thu, 21 Nov 2013 12:26:52 -0800 (PST)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 654951AE1BC for <rtcweb@ietf.org>; Thu, 21 Nov 2013 12:26:52 -0800 (PST)
Received: by mail-vc0-f171.google.com with SMTP id ik5so203946vcb.16 for <rtcweb@ietf.org>; Thu, 21 Nov 2013 12:26:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=PBKKglmGu62Vw8MtP/D8E5Xjwdf9N6wGrRAAEJxtNp4=; b=a6YoS+oKmRBnmkEkmIY06FfJgowRt1Otdr45TcdSSv8pwqOTyWBduZJ1dGf0A5q+qn yMVsVnpyfxUrx+frbdsQ+SpHszbAJkUetRr6AlDQMFmnMUavUO40Fk66bK/tPtFQn/0c yXH617+u2FuGEVS2MDClIt/zDtB8N1R95ZuoSTBnpWqJiqJX5TQl+Ym4hjsuBOV/w39P LkBjAYC5/cZmsNo+fYgaZe/FgAaz83DKxUFuHj9yoTLmjVPpryLcHhnUuHX8KSGs3EcQ 44EG5RHOjucXzg28Ca1DPYKGbSZQSNIZAKf5v294QuzhHO8dI+tys8LfbrggqdtNQ2Ed NzWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=PBKKglmGu62Vw8MtP/D8E5Xjwdf9N6wGrRAAEJxtNp4=; b=nHXBVX2J9Jx34djK3iyjQCw2Y9PpfxfFbZRqF5y41Wbe9I99zivMlzm4HEg0xDK49u D88NDGUiLzVYYWXNxd7e1u8J6rSpxR/EDA7WThqZtf/kTLiEerlUiHIflFviCIrfouxj 2eFGp34uyjNazf1YjXBcjLdVtcNmvkgJkmTRyLisqv49EXI4i4/2PHLERqhT7gYbwKSk fKzwtvfCwM+qALLOsNMxXQR5wHz7Fn9Q1WgQNLx3zK0+0FT4pG2zEQIOQ87bpQ3r5b8D Vhk+E/msXfT96fVnxHfWdNzK3c+s8wodevYIPcHUKyNp7XfEXCz1ku22kr9IrqP6s4UL sZZg==
X-Gm-Message-State: ALoCoQnD6PvHSPqCoIh42n3bQFgvgCkisYGV78wyVrl8Ye6lxLgtjQJU7U9gNsKPNRRZtle/RBcPTJwxW9TEBFQt5dEx9SUCAhPwAKGHXwfJENrJ48944IY0ZXaf8a/vm/MnwdCKSg83heUjxepjFuFzcbVDZcQjF6RpLD8ZiuNJopEUjX9b3yoE0wX6kfSyMuntKu0qmMa6
X-Received: by 10.221.39.195 with SMTP id tn3mr7474075vcb.2.1385065605298; Thu, 21 Nov 2013 12:26:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.110.101 with HTTP; Thu, 21 Nov 2013 12:26:25 -0800 (PST)
In-Reply-To: <BF2AE1F2-6BBD-4200-9F57-6B8EFF2A1C90@iii.ca>
References: <A3045C90BB645147BC99159AA47ABAC748C3DACB@szxeml558-mbs.china.huawei.com> <528DFA63.6030404@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1C54AE8D@ESESSMB209.ericsson.se> <BF2AE1F2-6BBD-4200-9F57-6B8EFF2A1C90@iii.ca>
From: Justin Uberti <juberti@google.com>
Date: Thu, 21 Nov 2013 12:26:25 -0800
Message-ID: <CAOJ7v-3aM3qn+hbnvssPo6iXvC2BWxXV73oxSXOUYcatsz0Ciw@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=001a113375c265285404ebb5b734
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] "pranswer" be applied as an update to a previously sent "answer"?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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, 21 Nov 2013 20:26:54 -0000

Yes, it is an error. Someone else pointed it out to me right after I
submitted -05; will be fixed in the next rev.


On Thu, Nov 21, 2013 at 10:17 AM, Cullen Jennings <fluffy@iii.ca>; wrote:

>
> On Nov 21, 2013, at 5:05 AM, Christer Holmberg <
> christer.holmberg@ericsson.com>; wrote:
>
> > Hi,
> >
> > I would assume that the text should say “update to a previously applied
> “pranswer”.
> >
> > Regards,
>
> +1
>
> >
> > Christer
> >
> > From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Harald
> Alvestrand
> > Sent: 21. marraskuuta 2013 14:20
> > To: rtcweb@ietf.org
> > Subject: Re: [rtcweb] "pranswer" be applied as an update to a previously
> sent "answer"?
> >
> > On 11/20/2013 12:22 PM, Lijing (Jessie) wrote:
> > draft-ietf-rtcweb-jsep-05 -----Section 4.1.3 says:
> >
> > "pranswer" indicates that a description should be parsed as an
> >    answer, but not a final answer, and so should not result in the
> >    freeing of allocated resources.  It may result in the start of media
> >    transmission, if the answer does not specify an inactive media
> >    direction.  A description used as a "pranswer" may be applied as a
> >    response to an "offer", or an update to a previously sent "answer".
> >
> > How can a pranswer be applied as an update to a previously sent answer?
>  I am not sure what’s the corresponding scenario.
> > From the state machine perspective, when answer is received, it enters
> the stable state. At this point, the state machine can not directly jump to
> local pranswer or remote pranswer state.
> >
> > My two cents: May be it needs more description or correction here.
> >
> > This makes sense, and is consistent with the state diagrams, if the last
> "answer" is changed to "pranswer".
> >
> > Justin, is this an error in the draft?
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>