Hi all,
I strongly support the inclusion of text in the draft.
I think the differentiations that are being made here between 'technical' and
'policy', and 'technical' and 'judicial' here are merely rhetorical. No clear
definition of the either terms and/or the difference have been offered thus
far. Thus the argument to not include the text seems unfounded.
Next to that, I have not been able to locate the limitation for the use of MUST
and MAY, as defined by John Levine, in RFC2119.
Best,
Niels
On 1/2/19 12:07 PM, Thomas Corte wrote:
> Hello,
>
> On 12/26/18 15:32, Gould, James wrote:
>
>> Do others in the working group believe that either the verification process
>> of the VSP is in scope based on the current wording of the draft or that a
>> consideration section can cover something that is outside the defined scope
>> of the draft?
>
> No, I agree that it's way out of scope. Gurshabad's proposed additions
> are in my point of view an attempt to address *judicial* issues (ensuring
> people's right to privacy, non-discrimination etc.) by adding wording to
> a *technical* specification. Lawyers and politicians exist to deal with
> such issues; engineers should not be required to waste their time with them.
>
> Plus, even *if* such wording should end up in the draft, it would be
> utterly pointless. Looking at the various implementations of EPP and EPP
> extensions which are out in the open (especially for country code TLDs),
> it's obvious that even the most basic technical requirements (such as
> strict XML schema compliance) and MUST regulations are often ignored or
> violated by many operators. I'd therefore be surprised if anyone who's
> determined to "abuse" the extension for human rights violations would
> care much about the proposed additions anyway.
>
> Best regards,
>
> Thomas
>
--
Niels ten Oever
Researcher and PhD Candidate
Datactive Research Group
University of Amsterdam
PGP fingerprint 2458 0B70 5C4A FD8A 9488
643A 0ED8 3F3A 468A C8B3
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
