qvcimnfiqkwxudxmipassocorg send ietfdkim mailing list submissions gfkyhddlmipassocorg subscribe unsubscribe via world wide web visit httpmipassocorgmailmanlistinfoietfdkim via email send message subject body help qvcimnfiqkwxudxmipassocorg reach person managing list qghtrnrqbhlpvmipassocorg replying please edit subject line specific contents ietfdkim digest todays topics 1 issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages douglas otis 2 issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages hector santos 3 issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages douglas otis 4 issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages hector santos udcatmailabuseorg sat apr 26 154959 2008 message 1 date sun 17 feb 2008 125151 0800 douglas otis subject ietfdkim issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages hector santos cc dkim list messageid contenttype textplain charsetusascii formatflowed delspyes feb 17 2008 932 hector santos wrote douglas otis wrote really dont see matters sent preferred type burglar knocking door many different doors could helped dkim might expectation knocking front door validate affiliation may different expectations back door difference might simply buying wares back door someone escorts front door might asked validate affiliation although likely unprepared moving everyone common doorway may seem ideal creates significant problem front door carries greater obligation different doors need different policies different levels trust based upon door used distant point future perhaps doors treated time arrived doug time came long ago remember predominately anonymous vs nonanonymous transactions systems always treaty anonymous non anonymous transactions differently anonymous back door last thing want although strongly appears asp model promoting dkim identifying individual sense anonymity dkim establishes affiliation domain identification individuals depends upon domain handles marks messages fully determined messages domain signs sp policy allows purported authors domain establish domain affiliation requirements suggest sp includes identification requirements declared outofscope wg charter formed remains good recommendation establishing domain affiliation requirements question identification depends _completely_ upon messages domain signs pointless dkim policy impose requirements signature validate header identity rfc 4871 indicates signatures valid associated _any_ header even remain ambiguous respect introduced message identification clearly decision signing domain made signature applied role verifiers second guess whether domain made proper choice choice fully within prerogative signing domain nonetheless dkim implemented across message protocols practical reasons time domains policy states messages signed practicality currently means smtp messages signed time would wrong assume dkim policy pertains smtp however far protocol gateways smtp concerned messages treated transport smtp may become problematic cases sense agreement dkim policy structured permit message protocols related smtp means separately announce dkim policy applied one solution suggested jim introduce transport scoping parameter within policy record unlike service parameter within key policy scoping also indicate protocols used support dkim would unreasonable assume protocols implemented dkim policy published would unreasonable policy record change dkim protocol adoption wild changes would safer less work policy scoping list domains supported protocols protocols domain implemented dkim listing could allow abuse blocked might introduced protocol gateways listing also prevent undesired blocking messages intended nonsmtp infrastructure known domain implemented dkim protocol policy scoping would permit message protocols ability introduce dkim policy independently smtp improve protections asap doug mwbfbflsantronicscom sat apr 26 154959 2008 message 2 date sun 17 feb 2008 162409 0500 hector santos subject ietfdkim issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages dkim list messageid 47b8a5f92030803santronicscom contenttype textplain charsetiso88591 formatflowed douglas otis wrote would safer less work policy scoping list domains supported protocols sorry dont see help see less work see complexity little benefit value behind sincerely hector santos cto httpwwwsantronicscom httpsantronicsblogspotcom udcatmailabuseorg sat apr 26 154959 2008 message 3 date sun 17 feb 2008 190947 0800 douglas otis subject ietfdkim issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages hector santos cc dkim list messageid 1975b75a7f184e1bb7ff4516e81ea92cmailabuseorg contenttype textplain charsetusascii formatflowed delspyes feb 17 2008 124 pm hector santos wrote douglas otis wrote would safer less work policy scoping list domains supported protocols sorry dont see help see less work see complexity little benefit value behind many feel sp limited transport protocols delivering messages smtp related repositories including messages bridged smtp words sp governs smtp message compliance several may balk suggestion insist dkim policy extends protocols categorization messages permitted sp could occur transport protocols without messages delivered location would smtp email number message transport protocols might eventually use dkim sizeable assertion messages dkim signed means exactly listing protocols dkim policy applies well listing protocols domain support would beneficial messages received nonsmtp related protocols 1 message delivered smtp related repository 2 messages delivered nonsmtp related repository cases list permits detection fraudulent sources without reliance upon invalid dkim signatures b makes expectation dkim signature explicit nonsmtp related protocols ensure proper message categorization including scope within policy record verifier free assume policy applies smtp ignore ii detect noncomplaint transport protocols iii assured dkim implemented transport protocol question really different able determine whether messages signed doug mwbfbflsantronicscom sat apr 26 154959 2008 message 4 date mon 18 feb 2008 122902 0500 hector santos subject ietfdkim issue 1547 ssp02 mx record publishing mandateto reduce dns overhead ssp discovery detectfraudulent messages douglas otis cc dkim list messageid 47b9c05e80608santronicscom contenttype textplain charsetiso88591 formatflowed douglas otis wrote feb 17 2008 124 pm hector santos wrote douglas otis wrote would safer less work policy scoping list domains supported protocols sorry dont see help see less work see complexity little benefit value behind many feel sp limited transport protocols delivering messages smtp related repositories including messages bridged smtp words sp governs smtp message compliance well didnt say practically speaking dkim x822 design issue delivering messages originally created transmitted gated wish protocol management creation transportation transformations said believe charles also alluded difficult accurately determine high reliability message originally created transported andor gated may transparent operations really different able determine whether messages signed another complex data point reliably confirmed wont able cant compare straight forward ssp dns lookup truefalse explicit policy declaration easily confirmed imo youre asking bit much practically speaking worth effort besides whats point important part policy question brushed aside poison pill aspssp02 sincerely hector santos cto httpwwwsantronicscom httpsantronicsblogspotcom _______________________________________________ note well list operates according end ietfdkim digest vol 108 issue 1 wed 06 aug 2008 163933 0800 ietfdkim digest vol 108 issue 1