Re: [dane] Payment association records

[Falcon Darkstar Momot <[e-mail]>]

I lightly draw attention to an ancient failed internet draft for storing
substantive payment processing information in the DNS:
https://tools.ietf.org/html/draft-eastlake-card-map-08

I also draw attention for a different reason to the yet-reserved HTTP
status code 402 (https://tools.ietf.org/html/rfc7231#page-59).

--Falcon Darkstar Momot
--Shadytel

On 10/03/2015 15:21, Wiley, Glen wrote:
> A few of us have put some work into an 00 draft describing a DANE
> like RR that would provide an association for payment information via
> the DNS. The abstract from the draft reads:
>
> There is no standard, interoperable method for associating
> Internet service identifiers with payment information.  This
> document  specifies a means for retrieving information sufficient for
> a party to render payment using various payment networks given
> the recipient's email address by leveraging the DNS to securely
> publish payment information in a payment association record.  A
> payment association record associates an Internet service identifier
> such as an email address with payment information such as an account
> number or Bitcoin address.
>
> Our draft is in the tracker:
>   https://tools.ietf.org/html/draft-wiley-paymentassoc-00
> And I’d like to get some feedback from folks on this to see what we
> can do to make this an effective tool.
>
> There are a number of elements that need to be fleshed out and we have
> more content in the works to address specific use cases.
>
> Looking forward to hearing from folks.
> -- 
> Glen Wiley
> Principal Engineer
> Verisign, Inc.
> [phone]
>
> A5E5 E373 3C75 5B3E 2E24  
> 6A0F DC65 2354 9946 C63A
>
>
> _______________________________________________
> dane mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dane