Re: [rtcweb] JSEP: multiple fingerprints for a certificate

Cullen Jennings <fluffy@iii.ca> Thu, 25 August 2016 15:34 UTC

Return-Path: <fluffy@iii.ca>
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 D106F12D1CB for <rtcweb@ietfa.amsl.com>; Thu, 25 Aug 2016 08:34:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 CIxGn8UNJfSi for <rtcweb@ietfa.amsl.com>; Thu, 25 Aug 2016 08:34:09 -0700 (PDT)
Received: from smtp73.iad3a.emailsrvr.com (smtp73.iad3a.emailsrvr.com [173.203.187.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1732612D1C0 for <rtcweb@ietf.org>; Thu, 25 Aug 2016 08:34:09 -0700 (PDT)
Received: from smtp10.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp10.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 3D3C060143; Thu, 25 Aug 2016 11:34:06 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp10.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id D10B96035B; Thu, 25 Aug 2016 11:34:05 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.100] ([UNAVAILABLE]. [128.107.241.183]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.7); Thu, 25 Aug 2016 11:34:06 -0400
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BC61B43@ESESSMB209.ericsson.se>
Date: Thu, 25 Aug 2016 09:34:04 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <17511AEF-B567-419F-A197-8AB265E0BC79@iii.ca>
References: <CAOW+2dtPN5s6VoccszXo2tY5u7R8hoR5msD_mZ6viOO6akYn2A@mail.gmail.com> <D3E465F7.D952%christer.holmberg@ericsson.com> <CAOW+2dtjn8drrcXxjCcZxeCNkk7HUp9oeTMAE4=3fs6EKPvkVA@mail.gmail.com> <D3E476C0.D99F%christer.holmberg@ericsson.com> <1F054785-35C3-4C78-BA68-9C1FA8C06633@iii.ca> <7594FB04B1934943A5C02806D1A2204B4BC61B43@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/3oFDCy1Jw-j_sn8L_JwakuWTBQU>
Cc: RTCWeb IETF <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP: multiple fingerprints for a certificate
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 25 Aug 2016 15:34:18 -0000

> On Aug 25, 2016, at 9:11 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
> Hi,
> 
>> The JSEP authors have typically tried to have JSEP ref everything that implementers >need to know just to make it easier for them to find it. I will add a ref to draft-ietf->mmusic-4572-update to JSEP.  Given it is an "update" it technical is a dependency >either way. 
> 
> Ok. That means we also need to reference a number of other "update" drafts that affect JSEP, but I think I sent you a list of those already?

I thought I got everything on your list in latest version but pleas have a look and see what else is missing. Greatly appreciate you checking this and helping track down any more updates. 

Here's the list of things I think that WebRTC normatively depends on so if we have "updates" to any of these, I should add them 

draft-ietf-avtcore-multi-media-rtp-session
draft-ietf-avtcore-rtp-circuit-breakers
draft-ietf-avtcore-rtp-multi-stream
draft-ietf-avtcore-rtp-multi-stream-optimisation
draft-ietf-avtext-rid
draft-ietf-avtext-sdes-hdr-ext
draft-ietf-ice-dualstack-fairness
draft-ietf-ice-rfc5245bis
draft-ietf-ice-trickle
draft-ietf-mmusic-ice-sip-sdp
draft-ietf-mmusic-msid
draft-ietf-mmusic-mux-exclusive
draft-ietf-mmusic-rid
draft-ietf-mmusic-sctp-sdp
draft-ietf-mmusic-sdp-bundle-negotiation
draft-ietf-mmusic-sdp-mux-attributes
draft-ietf-mmusic-sdp-simulcast
draft-ietf-payload-flexible-fec-scheme
draft-ietf-rtcweb-alpn
draft-ietf-rtcweb-data-channel
draft-ietf-rtcweb-data-protocol
draft-ietf-rtcweb-fec
draft-ietf-rtcweb-jsep
draft-ietf-rtcweb-overview
draft-ietf-rtcweb-rtp-usage
draft-ietf-rtcweb-security
draft-ietf-rtcweb-security-arch
draft-ietf-rtcweb-transports
draft-ietf-tsvwg-rtcweb-qos
draft-ietf-tsvwg-sctp-dtls-encaps
draft-ietf-tsvwg-sctp-ndata
draft-ietf-ice-trickle
draft-ietf-tram-stunbis
draft-ietf-avtcore-5761-update
draft-ietf-mmusic-4572-update
draft-ietf-mmusic-dtls-sdp
draft-ietf-avtcore-rfc5764-mux-fixes

RFC1889
RFC2198
RFC2327
RFC3264
RFC3388
RFC3389
RFC3489
RFC3550
RFC3551
RFC3555
RFC3556
RFC3605
RFC3611
RFC3711
RFC3758
RFC3890
RFC4145
RFC4566
RFC4570
RFC4571
RFC4572
RFC4585
RFC4588
RFC4733
RFC4756
RFC4820
RFC4895
RFC4961
RFC5052
RFC5053
RFC5061
RFC5104
RFC5109
RFC5124
RFC5245
RFC5285
RFC5389
RFC5506
RFC5576
RFC5583
RFC5705
RFC5761
RFC5763
RFC5764
RFC5766
RFC5768
RFC5888
RFC5928
RFC5956
RFC6051
RFC6062
RFC6096
RFC6156
RFC6184
RFC6188
RFC6236
RFC6263
RFC6330
RFC6363
RFC6364
RFC6464
RFC6465
RFC6520
RFC6525
RFC6544
RFC6555
RFC6562
RFC6681
RFC6682
RFC6716
RFC6749
RFC6904
RFC6951
RFC7022
RFC7053
RFC7064
RFC7065
RFC7104
RFC7160
RFC7164
RFC7301
RFC7496
RFC7587
RFC7635
RFC7639
RFC7657
RFC7667
RFC7675
RFC7728
RFC7741
RFC7742
RFC7850
RFC7874
RFC6336
RFC7350
RFC6365
RFC7564
RFC5198
RFC7564
RFC7613
RFC7345