W3C home > Mailing lists > Public > public-webauthn@w3.org > June 2016

AW: Extensions PR

From: Rolf Lindemann <rlindemann@noknok.com>
Date: Wed, 15 Jun 2016 19:09:02 +0200
To: "'Vijay Bharadwaj'" <vijaybh@microsoft.com>, <public-webauthn@w3.org>
Message-ID: <02a901d1c728$9dc27080$d9475180$@noknok.com>
Hi,

Here is an alternative proposal.
See branch "rolf-extension-opt" in github.  It uses Vijay's proposal as starting point.

Kind regards,
   Rolf

-----Urspr√ľngliche Nachricht-----
Von: Vijay Bharadwaj [mailto:vijaybh@microsoft.com] 
Gesendet: Mittwoch, 15. Juni 2016 17:51
An: public-webauthn@w3.org
Betreff: Extensions PR

Hi folks,

Apologies for the delay on this - I had a few urgent things intervene in the past week.

I just send out the PR below for extensions, and would like to walk through it on today's call. I was surprised at how little change was involved, and how much of it was simply resolving conflicts between text that said one thing and other text in the same section that said the opposite. In general, I tried to remove uncertainty where possible (e.g. by being explicit that clients passing through extensions is a valid choice).

Here is a PDF of the updated document for ease of review. All changes are in Sections 6 and 7, but I think it may be better to simply read through those sections for consistency rather than only look for changes since the latter may overlook internal contradictions in the text.

-----Original Message-----
From: noreply@github.com [mailto:noreply@github.com] 
Sent: Wednesday, June 15, 2016 8:40 AM
To: public-webauthn@w3.org
Subject: [w3c/webauthn] c05d78: Clean up extensions section

  Branch: refs/heads/vgb-extension-opt
  Home:   https://github.com/w3c/webauthn
  Commit: c05d78629156b9b99faedcd03151cc8cefa7ce91
      https://github.com/w3c/webauthn/commit/c05d78629156b9b99faedcd03151cc8cefa7ce91
  Author: Vijay Bharadwaj <vijaybh@users.noreply.github.com>
  Date:   2016-06-15 (Wed, 15 Jun 2016)

  Changed paths:
    M index.src.html

  Log Message:
  -----------
  Clean up extensions section

- Resolve inconsistent wording in different parts of the section: fix places that incorrectly suggested extensions cannot be used with makeCredential, and resolve conflict between wording that said client arguments are required vs. not.
- Treat implementations that choose to pass through extensions as a first-class citizen by requiring that extensions be defined to allow for this. Fixes #97.
- Fix all the predefined extensions to conform to the updated guidelines.
- Minor issues: AAGUID should be binary not string (see #61, fixes #51) and encode true as Boolean in CBOR instead of forcing it to integer value 1.



Received on Wednesday, 15 June 2016 17:09:39 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:21 UTC