IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 14 September 2016 18:50 UTC

Return-Path: <christer.holmberg@ericsson.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 BFB4412B447 for <rtcweb@ietfa.amsl.com>; Wed, 14 Sep 2016 11:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 tsEnl2gCjgkF for <rtcweb@ietfa.amsl.com>; Wed, 14 Sep 2016 11:50:22 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 704B212B43F for <rtcweb@ietf.org>; Wed, 14 Sep 2016 11:50:22 -0700 (PDT)
X-AuditID: c1b4fb2d-903ff700000019a3-d9-57d99be95a58
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by (Symantec Mail Security) with SMTP id 36.C0.06563.9EB99D75; Wed, 14 Sep 2016 20:50:20 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.211]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0301.000; Wed, 14 Sep 2016 20:50:17 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [rtcweb] JSEP: multiple fingerprints for a certificate
Thread-Index: AQHR/k1N4obaEB6UGkSI2f8MWO5rr6BZQxsA///eOwCAADWZAIAATs8AgB+ogYCAACUc4A==
Date: Wed, 14 Sep 2016 18:50:17 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BCA17F6@ESESSMB209.ericsson.se>
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> <54db5214-75b8-939b-d1f7-9512bd40554a@alvestrand.no>
In-Reply-To: <54db5214-75b8-939b-d1f7-9512bd40554a@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZGbHdVffN7JvhBg+ui1t8WP+D0eJYXxeb xdp/7ewOzB5XJlxh9Viy5CeTx+XzHxkDmKO4bFJSczLLUov07RK4MvZ9n8da8Juv4m33RfYG xjk8XYycHBICJhJzN3xk7mLk4hASWM8ocWTNPEYIZwmjxK7bzWxdjBwcbAIWEt3/tEEaRAR8 JSZObGYEsZkFFCW+LJ/PBmILCzhLTNn7jQWixkXi5ewDTCCtIgJhEvuehYGYLAKqElfWFYJU 8AJN6Zj9lwli0wMmiUsPHjCD1HAKOErcmyEMUsMoICbx/dQaJohN4hK3nsxngjhZQGLJnvPM ELaoxMvH/1ghbCWJxiVPWCHqdSQW7P7EBmFrSyxb+JoZYq+gxMmZT1gmMIrOQjJ2FpKWWUha ZiFpWcDIsopRtDi1uDg33chYL7UoM7m4OD9PLy+1ZBMjMG4Obvmtu4Nx9WvHQ4wCHIxKPLwP wm+GC7EmlhVX5h5ilOBgVhLhPTcVKMSbklhZlVqUH19UmpNafIhRmoNFSZz339nr4UIC6Ykl qdmpqQWpRTBZJg5OqQZGj7prHj7/fbc4B1gcmS2VWM61MWPzvSRFFYG8FVdTshymhJtcFSj5 mdXtvu7gF9FK/baLtwuUr7p8zWnfulDjjReblOa3Y4wP3gs/LDO/nr1rJav28wfvkoSlJjPM /pBW/8S+tqK7wG/jrQf7DsY1XGuyYk970HPTsd2wyzCjfI1XsNCvTdxKLMUZiYZazEXFiQB5 4PQLlwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/l7qcmns74zx2vA19QFq1apvWjx8>
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: Wed, 14 Sep 2016 18:50:25 -0000

Hi,

Just a minor correction: there is no 4572-bis. draft-4572-update updates/clarifies parts of RFC 4572.

4572-update does not fix anything that is "illegal" in RFC 4572. However, 4572-update is also a little more than "advice for the implementer".

So, I definitely think we should normatively reference 4572-update in JSEP. RTCWEB is what triggered 4572-update to begin with...

Regards,

Christer


-----Original Message-----
From: Harald Alvestrand [mailto:harald@alvestrand.no] 
Sent: 14 September 2016 21:31
To: Cullen Jennings <fluffy@iii.ca>; Christer Holmberg <christer.holmberg@ericsson.com>
Cc: RTCWeb IETF <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP: multiple fingerprints for a certificate

Den 25. aug. 2016 17:04, skrev Cullen Jennings:
> 
> 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. 

Speaking in terms of standards theory (and not referencing the particular issue):

If a conformant implementation of X can be made based on only the information in 4572, it is OK to reference 4572 in the specification for X. Any clarifications in -bis drafts can be considered "advice for the implementor", it doesn't change validity.

If a conformant implementation has to do something that is illegal according to 4572, but legal according to 4572-bis, the spec *has* to reference 4572-bis normatively. A reference to 4572 in addition is not needed. Note that this blocks publication until 4572-bis is published.

Note that this applies to optional features too; if an optional feature can't be implemented without reading 4572-bis, it's a normative dependency.

Back to discussing the subject line..

v2.46.0 | Report a Bug | By Email | System Status