[ietf-dkim] Open Issues at this time

[Eliot Lear <[e-mail]>]

For those keeping score, here are the open issues.


*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

	[e-mail] 	4 weeks ago 	
	4 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

	[e-mail] 	4 weeks ago 	
	4 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

	[e-mail] 	4 weeks ago 	
	4 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

	[e-mail] 	4 weeks ago 	
	4 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

	[e-mail] 	4 weeks ago 	
	4 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

	[e-mail] 	3 weeks ago 	
	3 weeks 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

	[e-mail] 	3 weeks ago 	
	3 weeks 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

	[e-mail] 	3 weeks ago 	
	3 weeks 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

	[e-mail] 	3 weeks ago 	
	3 weeks 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

	[e-mail] 	3 weeks ago 	
	3 weeks 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

	[e-mail] 	3 weeks ago 	
	3 weeks 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

	[e-mail] 	3 weeks ago 	
	3 weeks ago 	0
*1190 <https://rt.psg.com/Ticket/Display.html?id=1190>* 	*base-00 3.5 x=
<https://rt.psg.com/Ticket/Display.html?id=1190>* 	new 	dkim 	Nobody 	0

	[e-mail] 	9 days ago 	
	9 days ago 	0
*1192 <https://rt.psg.com/Ticket/Display.html?id=1192>* 	*TLD key
publication and signing
<https://rt.psg.com/Ticket/Display.html?id=1192>* 	new 	dkim 	Nobody 	0

	[e-mail] 	7 days ago 	
	7 days ago 	0
*1193 <https://rt.psg.com/Ticket/Display.html?id=1193>* 	*base spec:
instead of signing the message, sign the hash
<https://rt.psg.com/Ticket/Display.html?id=1193>* 	new 	dkim 	Nobody 	0

	[e-mail] 	7 days ago 	
	7 days ago 	0
*1194 <https://rt.psg.com/Ticket/Display.html?id=1194>* 	*base spec:
whitespace in signature?
<https://rt.psg.com/Ticket/Display.html?id=1194>* 	new 	dkim 	Nobody 	0

	[e-mail] 	7 days ago 	
	7 days ago 	0
*1195 <https://rt.psg.com/Ticket/Display.html?id=1195>*
*draft-ietf-dkim-base-00 - 3.4.6 Example (Canonicalization)
<https://rt.psg.com/Ticket/Display.html?id=1195>* 	new 	dkim 	Nobody 	0

	[e-mail] 	6 days ago 	
	6 days ago 	0
*1196 <https://rt.psg.com/Ticket/Display.html?id=1196>* 	*Base: Upgrade
indication and protection against downgrade attacks
<https://rt.psg.com/Ticket/Display.html?id=1196>* 	new 	dkim 	Nobody 	0

	[e-mail] 	6 days ago 	
	6 days ago 	0
*1200 <https://rt.psg.com/Ticket/Display.html?id=1200>* 	*MUST vs SHOULD
in Verifier Actions section (-base)
<https://rt.psg.com/Ticket/Display.html?id=1200>* 	new 	dkim 	Nobody 	0

	[e-mail] 	4 days ago 	
	4 days ago 	0
*1201 <https://rt.psg.com/Ticket/Display.html?id=1201>* 	*change the
syntax from SPF compat to human compat
<https://rt.psg.com/Ticket/Display.html?id=1201>* 	new 	dkim 	Nobody 	0

	[e-mail] 	4 days ago 	
	4 days ago 	0
*1203 <https://rt.psg.com/Ticket/Display.html?id=1203>* 	*extendable RR
records? <https://rt.psg.com/Ticket/Display.html?id=1203>* 	new 	dkim
Nobody 	0

	[e-mail] 	24 hours ago 	
	24 hours ago 	0
*1204 <https://rt.psg.com/Ticket/Display.html?id=1204>* 	*issue with
DKIM simple header algorithm and milter-based implementations
<https://rt.psg.com/Ticket/Display.html?id=1204>* 	new 	dkim 	Nobody 	0

	[e-mail] 	1 min ago 	
	1 min ago 	0

_______________________________________________
NOTE WELL: This list operates according to 
http://dkim.org/ietf-list-rules.html