Hello,
On 10/5/18 15:01, Niels ten Oever wrote:
> If this would be a standard in response to a demand, that would be fine.
> But I am rather afraid this is a standard that will create policy and
> practice. Namely the practice of 3rd party identity verification
> providers. Since there is legislation that demand this afaik, I think we
> should be hesitant to standardize such a thing because of the
> potentially severe implications as pointed out by the review.
Not having a standard for this process will not prevent bad actors from
establishing it anyway (they'll simply use proprietary extensions).
However, it will force good actors requiring similar processes to also
implement their own solutions, which hurts interoperability and makes
life harder for everybody. In this respect, this is somewhat similar to
an argument brought forward by opponents of weapon control in the US: "If
weapons become illegal, only illegal people will have weapons".
Generally, technical standards are IMHO not the appropriate place for
fighting political or societal issues. This battle needs to be fought
elsewhere, i.e. in the voting booth or by people walking away from a bad
product.
Best regards,
Thomas
--
____________________________________________________________________
| |
| knipp | Knipp Medien und Kommunikation GmbH
------- Technologiepark
Martin-Schmeißer-Weg 9
44227 Dortmund
Deutschland
Dipl.-Informatiker Tel: +49 231 9703-0
Thomas Corte Fax: +49 231 9703-200
Stellvertretender Leiter SIP: thomas.co...@knipp.de
Software-Entwicklung E-Mail: thomas.co...@knipp.de
Registereintrag:
Amtsgericht Dortmund, HRB 13728
Geschäftsführer:
Dietmar Knipp, Elmar Knipp
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
