Re: [rtcweb] Request for status update

Sean Turner <sean@sn3rd.com> Wed, 03 July 2019 23:13 UTC

Return-Path: <sean@sn3rd.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 BBA811200D7 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2019 16:13:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=sn3rd.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 xcQsIjmpr7Pt for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2019 16:13:29 -0700 (PDT)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (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 0036D120096 for <rtcweb@ietf.org>; Wed, 3 Jul 2019 16:13:28 -0700 (PDT)
Received: by mail-qk1-x72e.google.com with SMTP id r21so3950177qke.2 for <rtcweb@ietf.org>; Wed, 03 Jul 2019 16:13:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Y/70pNn0j11/ksVtfFZ+koceRqfU2Z8WF36DN/SRRHA=; b=gNlcPQnqNKCsVrgYJzyBlyiLVX9KLKZNjC1/c4Ga/RuT6zUUCseurEd+AZd1MxVov5 ZOk1YSrknrI5mRLY440HcLt3EXjbNdGMZVllepzNFavse8KJldgwxHm1mphs8589srqm Doi/vqEu0OjHVoLC7J5kDyB8XJu/1HkTctOQU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Y/70pNn0j11/ksVtfFZ+koceRqfU2Z8WF36DN/SRRHA=; b=VqPnRHyG5KryacByP4epGljqB/MVQnvyG47Znotlnx5+1YVIxGsG3ousLXdjd2LBpy CYN9dG61Nw7XKtbpBgF923TroAN+2JwRsYX5Ssn1ncTjqrRIJIxIDGRVPdFLTUQ+1ljT WwIvPab783kWdodZ8orxLmHW5FXkwGEobEWK/fof8chiGQ9PMRcUfIss8NbU4fn3sw+m eLdJ+ITAighByfyFn1mHSWvsuMeb1OEK10JrcFmsoY4CZpOoZdr+FrKq5FL8/DXn4fT5 02AiTtp1BULpwivXWTYjX/DbraPf91HF3+HbJXbhYmEjvZsOqSb2HzHZQ+BsWWKf6cRt rHlw==
X-Gm-Message-State: APjAAAVKBzZFPgPbq4voGqI7gQh7wdAIu7pXVU5ENUq86Dm1rW854dNA l5FKIB4AdKeBXCqlfFWXNAfNk/y0WSM=
X-Google-Smtp-Source: APXvYqz6OzMkzacRQRXKwVlfVIB+MZIg26xgvLhMmcefu8li0qZSE2ZOmZi0bU7MmvCbVqizz8LCGQ==
X-Received: by 2002:a37:bd7:: with SMTP id 206mr4264116qkl.440.1562195608121; Wed, 03 Jul 2019 16:13:28 -0700 (PDT)
Received: from sn3rd.lan ([75.102.131.36]) by smtp.gmail.com with ESMTPSA id u18sm1542061qkj.98.2019.07.03.16.13.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jul 2019 16:13:27 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <b03853a4-1006-4da0-d52f-9e7462a2cd0c@alvestrand.no>
Date: Wed, 3 Jul 2019 19:13:26 -0400
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D80CECAF-B520-40A2-BFBB-E39B73BA943D@sn3rd.com>
References: <b03853a4-1006-4da0-d52f-9e7462a2cd0c@alvestrand.no>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/qKdVsZTQ2or7x6ioEcTKnxTjNTI>
Subject: Re: [rtcweb] Request for status update
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: Wed, 03 Jul 2019 23:13:32 -0000

A fair question Harald.  Here’s the status of the WGs as of today:

draft-ietf-rtcweb-ip-handling: New version spun yesterday.  Awaiting Adam’s concurrence on one change, then he will get state moved to approved.

draft-ietf-rtcweb-security and draft-ietf-rtcweb-security-arch: Held a conference call with Ben, Ted, ekr, and myself to address Ben’s discusses and comments.  ekr filed new issues and needs to generate some PRs.  Once a new version is spun, Ben, Adam, and I will review and hopefully we’re done with these two drafts.

draft-ietf-rtcweb-fec: I am getting emails now from GitHub showing Justin is diligently working through the outstanding comments.  I hope a revised draft will hit tonight or no later than Monday’s submission deadline.

draft-ietf-rtcweb-mdns-ice-candidates: It is my understanding that Adam is going to AD sponsor this one, but not until the other four move on.

spt

> On Jul 3, 2019, at 03:23, Harald Alvestrand <harald@alvestrand.no>; wrote:
> 
> WG chairs - can you give the WG a status update on the WG's documents?
> 
> As far as I can tell from
> https://www.rfc-editor.org/cluster_info.php?cid=C238 the critical pieces
> not in the RFC Editor queue are still the security documents and FEC,
> but -4566bis, -clue-protocol, -rmcat-eval-criteria and -ice-sip-sdp are
> also listed.
> 
> What is the status of these documents?
> 
> Are there others?
> 
> At the moment, the responsibility of the chairs is (in my opinion) to
> make sure publication happens. It's been a while.
> 
> Harald
> 
> -- 
> Surveillance is pervasive. Go Dark.
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb