IETF Logo Mail Archive

Re: [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-rfc8829bis-00.txt

Roman Shpount <roman@telurix.com> Sun, 11 July 2021 02:17 UTC

Return-Path: <roman@telurix.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 BB1263A02BD for <rtcweb@ietfa.amsl.com>; Sat, 10 Jul 2021 19:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telurix.com
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 hHe4Q_zSiiAB for <rtcweb@ietfa.amsl.com>; Sat, 10 Jul 2021 19:17:23 -0700 (PDT)
Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FA303A02BB for <rtcweb@ietf.org>; Sat, 10 Jul 2021 19:17:23 -0700 (PDT)
Received: by mail-qv1-xf2f.google.com with SMTP id o9so428376qvu.5 for <rtcweb@ietf.org>; Sat, 10 Jul 2021 19:17:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qgh0nY1FDtT7zx2riRAV9TT3hjIdW9Tcp274hG91jjU=; b=j7vFcJURJItmtdSo01nzUQbf4tVSjNV0OX1/y+E1KdjpJpkz7kctdjwPm+x4buL81N nasBFlDu+1Gk6C2dQnw2Owf8aX2A9sht1c+62HTgB/gvEOybHeHIpP6idCC6qcnt1bX0 NpsiXLBqAlqfGn+h9TX4V7jUzqSmKcwPVlHzI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qgh0nY1FDtT7zx2riRAV9TT3hjIdW9Tcp274hG91jjU=; b=DCZXmszZAtHz0cFd0UlqiqodJE1qcf/ENq2/kQuBMHR2xi5GtM29H0Et+I15YHjakG yE9NZ5QtNtgDTTx++dJDSCbTl5KwiME2TCM+di4e7fh8MO3xCTa+pnhZJmhe4uTf9nLp Q7vk3H9kpmLpC/2lZ7sbnGR85UBuXhGpN1fHsv3prt33cn6Jcz97YWVtLE1dudsMuh/l LER0SqzVUpFWnNzG9Ilp6wg/9IKLPmL1Bq2g7dEBc/IAmdWuzMsHM/3VgiMk9UyEYf0e ov62VXCojplJs1SHQDXFvW6q5OqHPq1JyYmztIGCQdQnGNaR5RyhL+koUBTrisld3dvU ckZg==
X-Gm-Message-State: AOAM5324BmhQdRm7qcbslA7F1A5IA7uGGXmXMQ4J8hiC01Mp2TFZ6HqH vk3LXxCf3N7Tr89CoT5/QG3wxHLwlxEI7g==
X-Google-Smtp-Source: ABdhPJwpumVJAKMeFPHyYQke3i3WR8SajpGaLFJhHnmjaKajjhTkyXtT1ogw3jbtclTGdN4W/SYnSQ==
X-Received: by 2002:a0c:d68f:: with SMTP id k15mr44586492qvi.14.1625969841609; Sat, 10 Jul 2021 19:17:21 -0700 (PDT)
Received: from mail-yb1-f177.google.com (mail-yb1-f177.google.com. [209.85.219.177]) by smtp.gmail.com with ESMTPSA id o123sm4730946qkd.6.2021.07.10.19.17.20 for <rtcweb@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 10 Jul 2021 19:17:20 -0700 (PDT)
Received: by mail-yb1-f177.google.com with SMTP id r132so21849060yba.5 for <rtcweb@ietf.org>; Sat, 10 Jul 2021 19:17:20 -0700 (PDT)
X-Received: by 2002:a25:487:: with SMTP id 129mr56183382ybe.0.1625969840139; Sat, 10 Jul 2021 19:17:20 -0700 (PDT)
MIME-Version: 1.0
References: <162596540685.23062.11654727411981880816@ietfa.amsl.com> <CALe60zArqmDB1SVkEna_h9gZ7MC=fsio==-Wsb5aJN5Oi-xUdQ@mail.gmail.com>
In-Reply-To: <CALe60zArqmDB1SVkEna_h9gZ7MC=fsio==-Wsb5aJN5Oi-xUdQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Sat, 10 Jul 2021 22:17:08 -0400
X-Gmail-Original-Message-ID: <CAD5OKxswQysOL2SCSKkYvzqWfD9v=mH=dzuYtJkXcU=kRovGHw@mail.gmail.com>
Message-ID: <CAD5OKxswQysOL2SCSKkYvzqWfD9v=mH=dzuYtJkXcU=kRovGHw@mail.gmail.com>
To: justin@uberti.name
Cc: RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bcb19705c6cf9af8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/A3dA63TjznRPqidE76sjFQ1UwO4>
Subject: Re: [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-rfc8829bis-00.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 11 Jul 2021 02:17:29 -0000

I have a question regarding max-compat in subsequent offers with iceRestart:

Should new candidates be gathered for all m= lines or only for the m=lines
which are not bundled after the previous offer/answer exchange?

I would suggest that new candidates should be gathered for all m=lines to
be compatible with 3PCC.

Thank You,
_____________
Roman Shpount


On Sat, Jul 10, 2021 at 9:11 PM Justin Uberti <justin@uberti.name> wrote:

> As discussed at IETF 110. Diff from RFC8829:
> https://tools.ietf.org/rfcdiff?url1=https://www.rfc-editor.org/rfc/rfc8829.txt&url2=https://www.ietf.org/archive/id/draft-uberti-rtcweb-rfc8829bis-00.txt
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Sat, Jul 10, 2021 at 6:03 PM
> Subject: New Version Notification for draft-uberti-rtcweb-rfc8829bis-00.txt
> To: Cullen Jennings <fluffy@iii.ca>ca>, Eric Rescorla <ekr@rtfm.com>om>, Justin
> Uberti <justin@uberti.name>
>
>
>
> A new version of I-D, draft-uberti-rtcweb-rfc8829bis-00.txt
> has been successfully submitted by Justin Uberti and posted to the
> IETF repository.
>
> Name:           draft-uberti-rtcweb-rfc8829bis
> Revision:       00
> Title:          JavaScript Session Establishment Protocol (JSEP)
> Document date:  2021-07-10
> Group:          Individual Submission
> Pages:          106
> URL:
> https://www.ietf.org/archive/id/draft-uberti-rtcweb-rfc8829bis-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-uberti-rtcweb-rfc8829bis/
> Html:
> https://www.ietf.org/archive/id/draft-uberti-rtcweb-rfc8829bis-00.html
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-uberti-rtcweb-rfc8829bis
>
>
> Abstract:
>    This document describes the mechanisms for allowing a JavaScript
>    application to control the signaling plane of a multimedia session
>    via the interface specified in the W3C RTCPeerConnection API and
>    discusses how this relates to existing signaling protocols.
>
>    This specification obsoletes RFC 8829.
>
>
>
>
> The IETF Secretariat
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.8.7 | Report a Bug | By Email