Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algor

I think I've come around to +1 on keeping "h=" in key records.

-MSK

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

<Prev in Thread]	Current Thread	[Next in Thread>
Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Jon Callas Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Murray S. Kucherawy Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Jon Callas Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Mark Delany Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Douglas Otis Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Murray S. Kucherawy Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Douglas Otis Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Murray S. Kucherawy Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Douglas Otis Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms, Murray S. Kucherawy <=

Re: [ietf-dkim] RFC4871bis - whether to drop -- h: Acceptable hash algorithms