Thank you for your reply Shivan,
Your comment cleared some things up for me:
> The draft surveyed several widely deployed techniques and synthesized best
> current practices. The technique you're proposing is a new technique, and
> worth considering in its own separate document by the DNSOP wor
Hi Elliott,
On Wed, 24 May 2023 at 14:52, wrote:
> --- Original Message ---
> On Tuesday, May 23rd, 2023 at 21:22, Paul Wouters 40aiven...@dmarc.ietf.org> wrote:
>
>
> On Mon, May 22, 2023 at 5:49 PM wrote:
>
>> Dear DNSOP WG,
>>
>> My company has developed a domain verification techni
--- Original Message ---
On Tuesday, May 23rd, 2023 at 21:22, Paul Wouters
wrote:
> On Mon, May 22, 2023 at 5:49 PM wrote:
>
>> Dear DNSOP WG,
>>
>> My company has developed a domain verification technique using DNS, it fits
>> the abstract of draft-ietf-dnsop-domain-verification-techn
On Mon, May 22, 2023 at 5:49 PM wrote:
> Dear DNSOP WG,
>
> My company has developed a domain verification technique using DNS, it
> fits the abstract of draft-ietf-dnsop-domain-verification-techniques.
>
> I am writing to ask the WG's opinion on whether our technique is within
> the scope of the
Dear DNSOP WG,
My company has developed a domain verification technique using DNS, it fits the
abstract of draft-ietf-dnsop-domain-verification-techniques.
I am writing to ask the WG's opinion on whether our technique is within the
scope of the current draft and if so, whether it should be con
