Greetings all,
Your chairs have been discussing the agenda for our meeting in Madrid on
22 July. The most important next thing we believe we need to do to move
the work forward is adopt a document with the base protocol for what
goes in the header of messages to accomplish our chartered tasks. There
are currently three proposals on the table:
https://datatracker.ietf.org/doc/draft-crocker-dkim-dkor/
https://datatracker.ietf.org/doc/draft-gondwana-dkim2-header/
https://datatracker.ietf.org/doc/draft-nurpmeso-dkim-access-control-diff-changes/
With that in mind, we'd like the main order of business to be what
changes would be required in order to get any of those documents in
shape to be adoptable as our working group draft. (Note that the word
was "adoptable", not "finished". We're asking, "If we picked this
document as our base spec, what more -- or less -- would it need for you
to consider using it as a starting point for the work.) The Gondwana
draft came out of one of our "starting point" drafts in the charter, so
we'd like to hear specifics about why it is not appropriate for adoption
if you feel that there's nothing that could be added or subtracted to
make it so, but for all of the documents we'd like you to make an effort
to say what would need to change to make you satisfied it could go
forward.
Your chairs would be fine if you started this discussion on the list
this coming week and we can continue it in real time on the 22nd.
So, regarding the agenda: We are expecting you've all read the above
documents at this point, so we're not going to have presentations on the
documents; just discussion about adoptability. We expect that to take up
the bulk of the time. Other than that, we'd like to have some discussion
on what other documents we might want to adopt, and on the status of the
motivation document. For the other documents: There is a bounce
processing draft and a modification algebra draft that seem to be
specific companions to the header draft; there are the Ed25519, hash
adaptivity, and DNS drafts that have to do with using different has
algorithms; and then there's the examples draft that could be part of
the deployment guide, or might simply be folded into some other draft.
We don't need to spend a huge amount of time discussing that, but we
think it will go faster in real-time than on the list. For the
motivations document, we want to get an idea of what it's eventual role
will be: Is it just a place for us to keep track of motivations but
we're not planning on publishing it, or is it going to become the basis
for the deployment guide to give us an overview of the entire system and
how it works, or something else?
So here's what we're thinking of for the agenda:
1. Administrivia [ 10 minutes ]
2. Headers draft adoptability [ 60 minutes ]
3. Motivations draft [ 20 minutes ]
4. Other drafts [ 20 minutes ]
5. AOB [ 10 minutes ]
We expect the chairs will run all of the discussion, but it would be
useful if draft authors were ready at the mic to answer questions as we
go along.
Are there any other specific agenda items needed? We can always
re-adjust the times, and if we get through things surprisingly quickly,
we can add that time to AOB and get into technical details.
We expect that after this meeting, we'll quickly thereafter formally
adopt some protocol document(s) on the list and we'll try to hold an
online interim in the not too distant future to really dive into
technical work.
Looking forward to seeing and/or hearing you, in person or remotely, in
Madrid.
Pete and Murray
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
