Attached is the current issues list and the opener. Remember, to open
an issue, put "New Issue" in the header. This list was generated from
rt.psg.com (the roundup stuff isn't yet cooked).
Eliot
*1170 <https://rt.psg.com/Ticket/Display.html?id=1170>* * Introduction
lacks the introduction of SSP
<https://rt.psg.com/Ticket/Display.html?id=1170>* new dkim Nobody 0
hsantos(_at_)santronics(_dot_)com 2 weeks ago
2 weeks ago 0
*1171 <https://rt.psg.com/Ticket/Display.html?id=1171>*
*draft-ietf-dkim-threats-00 Clarification of the DKIM mechanism
<https://rt.psg.com/Ticket/Display.html?id=1171>* new dkim Nobody 0
dotis(_at_)mail-abuse(_dot_)org 2 weeks ago
2 weeks ago 0
*1172 <https://rt.psg.com/Ticket/Display.html?id=1172>* *disagreement
on impact and probability of Attacks Against Message Signatures
<https://rt.psg.com/Ticket/Display.html?id=1172>* new dkim Nobody 0
dotis(_at_)mail-abuse(_dot_)org 2 weeks ago
2 weeks ago 0
*1173 <https://rt.psg.com/Ticket/Display.html?id=1173>* *Does Section
4.1.4 properly address traceability and accountability?
<https://rt.psg.com/Ticket/Display.html?id=1173>* new dkim Nobody 0
dotis(_at_)mail-abuse(_dot_)org 2 weeks ago
2 weeks ago 0
*1174 <https://rt.psg.com/Ticket/Display.html?id=1174>*
*raft-ietf-dkim-threats-00 Limited information in a critical section
<https://rt.psg.com/Ticket/Display.html?id=1174>* new dkim Nobody 0
dotis(_at_)mail-abuse(_dot_)org 2 weeks ago
2 weeks ago 0
*1180 <https://rt.psg.com/Ticket/Display.html?id=1180>*
*draft-ietf-dkim-threats-00 DKIM can be effective within the
Originator's AdmD <https://rt.psg.com/Ticket/Display.html?id=1180>*
open dkim Nobody 0
dotis(_at_)mail-abuse(_dot_)org 10 days ago
10 days ago 0
*1181 <https://rt.psg.com/Ticket/Display.html?id=1181>* *Misleading
figure in 1.1 <https://rt.psg.com/Ticket/Display.html?id=1181>* new
dkim Nobody 0
nobody(_at_)xyzzy(_dot_)claranet(_dot_)de 10 days ago
10 days ago 0
*1182 <https://rt.psg.com/Ticket/Display.html?id=1182>* *Eavesdropping
may permit man-in-the-middle as well
<https://rt.psg.com/Ticket/Display.html?id=1182>* new dkim Nobody 0
dotis(_at_)mail-abuse(_dot_)org 10 days ago
10 days ago 0
*1183 <https://rt.psg.com/Ticket/Display.html?id=1183>* *carryover:
draft-allman-dkim-base-01.txt - Should we have an r= tag in either the
signature or key record
<https://rt.psg.com/Ticket/Display.html?id=1183>* new dkim Nobody 0
lear(_at_)ofcourseimright(_dot_)com 10 days ago
10 days ago 0
*1184 <https://rt.psg.com/Ticket/Display.html?id=1184>* *carryover:
Develop plan for transition of multiple crypto algs (a=)
<https://rt.psg.com/Ticket/Display.html?id=1184>* new dkim Nobody 0
lear(_at_)ofcourseimright(_dot_)com 10 days ago
10 days ago 0
*1185 <https://rt.psg.com/Ticket/Display.html?id=1185>* *carryover:
draft-allman-dkim-base-01.txt Transition sha-1 to sha-256
<https://rt.psg.com/Ticket/Display.html?id=1185>* new dkim Nobody 0
lear(_at_)ofcourseimright(_dot_)com 10 days ago
10 days ago 0
*1186 <https://rt.psg.com/Ticket/Display.html?id=1186>* *4.2 needs new
Attack Item: Inconsistent Signature vs Policy Attacks
<https://rt.psg.com/Ticket/Display.html?id=1186>* new dkim Nobody 0
hsantos(_at_)santronics(_dot_)com 9 days ago
9 days ago 0
_______________________________________________
NOTE WELL: This list operates according to
<http://dkim.org/ietf-list-rules.html>