On 3/13/15, 1:04 PM, "John R Levine" <[email protected]> wrote:
>> In the PMTA draft I offered the same locator approach as SMIMEA, >>however >> also mention that that is one of many possible means for locating the >> record. It is not hard to image use cases in which a recipient would >> want to expose multiple payment associations that don't necessarily >> correspond to a mailbox. > >There's two separate questions here -- one is what name to use in the >DNS, >and the other is what sort of RR to put there. My point is that if the >name corresponds to a hashed mailbox, the sensible name is ><hash>._mailbox.domain, regardless of what RRs one uses. If you want to >publish PMTA records that don't correspond to a mailbox, that's no >problem, use the same record with different names. For obvious reasons, >it would not be great to have some _pmta names being mailboxes and some >being something else. I see what you are driving at. Locating records becomes more uniform in the case of identifiers that map directly to email. One of the points we made in the draft was that hashed email user names is a Possible but not exclusive means for locating the payment association. It Certainly helps reduce friction between parties but I would like to not Constrain future use cases, I can imagine other locating mechanisms that are Tied to something other than an email address. One question for the WG then is whether it makes sense to take your suggestion To the other records under discussion (SMIME, OPENPGPKEY). > >> Do you feel IBAN should be an exemplar? > >Yes, both because it's very widely used, and it brings in the important >issue of payment systems that handle multiple currencies. I think you'll >find that ACH and Bitcoin are fairly unusual in that they are each single >currency. Thanks for highlighting that issue. We¹ll probably use that in a future Version of the draft. > >Regards, >John Levine, [email protected], Taughannock Networks, Trumansburg NY >Please consider the environment before reading this e-mail. _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
