Re: [apps-discuss] [IANA #900093] Re: draft-vesely-authmethod-dnswl

[Alessandro Vesely <[e-mail]>]

On Mon 04/Apr/2016 23:11:22 +0200 Murray S. Kucherawy wrote:
> On Mon, Apr 4, 2016 at 9:20 AM, Alessandro Vesely <[e-mail]> wrote:
> 
>> Can people subscribe to iana-prot-param-comment's?
> 
> Not without just starting to Cc: them (i.e., it's not a list or UI I can
> access), but I'm also not sure it's a good idea to burden their ticketing
> system with a lot of traffic; they don't need to be involved at this phase.

The traffic is not so much.  The problem is it doesn't seem to be publicly
accessible.

> If you want to discuss this in a public forum, [e-mail] is
> certainly a valid choice.  If you want to seek publication via the IETF
> stream (which seems a legitimate thing to do), I would eventually move it
> to [e-mail].

Hm... adding CC AppsAWG.  Let's see if anybody is interested.

I still don't think it is worth publishing the I-D, but maybe IETF's list
archives can be considered permanent documents, which can be referenced by
items added after Expert Review, no?

> I had a look at your -04.  Thank you for addressing most of my comments and
> suggestions; it's certainly better.  A few non-editorial issues remain:
> 
> - The original ptype.property list has not been updated as discussed, so
> the main problem remains.

The "dns" ptype has its own table there.  Added a more text.  I don't think
this is a useless ptype, since so much stuff is DNS-based...

> - You might want to include an example of use, perhaps in an appendix or in
> a new Section 2.1, so people can see what's going on.

A bare example was there already.  Fully expanded.

<pissed off>
So delighted of the new text, I managed to screw up policy.txt, which is
exactly what was to be exemplified :-/

It should read:

  Authentication-Results: mta.example.org;
      dnswl=pass dns.zone=list.dnswl.example
      policy.ip=127.0.10.1
      policy.txt="fwd.example http://fwd.example/s?s=100"

</pissed off>

> - You mention the need to "determine the color of x".  Doesn't an MTA
> making a query to a DNSxL know what the color of "x" is already?

Yes.  This is detailed in the last paragraph of the example (A.1).

> - Section 2 changed "fail" to "none", but Table 3 in Section 3 did not.

Thanks.

> - There is now a reference to RFC7719, but no use of that reference
> anywhere in the body of the document.

Dropped.

Ale

-------- Forwarded Message --------
Subject: New Version Notification for draft-vesely-authmethod-dnswl-05.txt
Date: Wed, 13 Apr 2016 10:19:28 -0700
From: [e-mail]
To: Alessandro Vesely <[e-mail]>


A new version of I-D, draft-vesely-authmethod-dnswl-05.txt
has been successfully submitted by Alessandro Vesely and posted to the
IETF repository.

Name:		draft-vesely-authmethod-dnswl
Revision:	05
Title:		DNSWL Email Authentication Method Extension
Document date:	2016-04-13
Group:		Individual Submission
Pages:		7
URL:
https://www.ietf.org/internet-drafts/draft-vesely-authmethod-dnswl-05.txt
Status:         https://datatracker.ietf.org/doc/draft-vesely-authmethod-dnswl/
Htmlized:       https://tools.ietf.org/html/draft-vesely-authmethod-dnswl-05
Diff:           https://www.ietf.org/rfcdiff?url2=draft-vesely-authmethod-dnswl-05

Abstract:
   This document describes an additional Email Authentication Method
   compliant with RFC 7601.  The method consists in looking up the
   sender'IP in a DNS whitelist.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat