📅 Original date posted:2011-12-15
🗒️ Summary of this message: Combining DNSSEC TXT record and HTTPS proposal could provide the dynamism of HTTPS without a rigid URL scheme for querying the server.
📝 Original message:Could we combine this proposal and the HTTPS proposal?
The DNSSEC TXT record could give instructions on how to query an HTTPS server to get the address. Then we get the dynamism of HTTPS without having a rigid URL scheme for querying the server along with the advantages of DNSSEC.
--- On Wed, 12/14/11, Rick Wesson <rick at support-intelligence.com> wrote:
> From: Rick Wesson <rick at support-intelligence.com>
> Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases
> To: "Luke-Jr" <luke at dashjr.org>
> Cc: bitcoin-development at lists.sourceforge.net
> Date: Wednesday, December 14, 2011, 8:22 PM
> understand that not *everyone* wants
> or will adhere to that best
> practice and in my NSHO it isn't.
>
> -rick
>
> 2011/12/14 Luke-Jr <luke at dashjr.org>:
> > On Wednesday, December 14, 2011 6:02:25 PM Rick Wesson
> wrote:
> >> I also am largely in favor of using secured zones
> to publish TXT
> >> records to digital currencies. I've been thinking
> mainly about TXT
> >> using the following format for bitcoin.
> >>
> >> _btc.<lhs>.<rhs>
> >
> > Don't confuse BTC (Bitcoin unit) with BC (Bitcoin in
> general / protocol)...
> > The hard part of using DNS will be sticking to the
> standard good practice of
> > using a new address for every transaction.
>
> ------------------------------------------------------------------------------
> 10 Tips for Better Server Consolidation
> Server virtualization is being driven by many needs.
>
> But none more important than the need to reduce IT
> complexity
> while improving strategic productivity. Learn More!
> http://www.accelacomm.com/jaw/sdnl/114/51507609/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
Zell Faze [ARCHIVE] /
npub190…tt9rq
2023-06-07 02:46:56
in reply to nevent1q…0y8v
Author Public Key
npub19063ylrn5yfm7zdqwekeek0sa60lwku4nmvgr4jl95pkvy9dfvtqrtt9rqSeen on
wss://relay.nostr.bandPublished at
2023-06-07 02:46:56Event JSON
{
"id": "5c89c3f03d1edc22e4ac85889d93778725680c8ae0243861e55ff8eb4774c36e",
"pubkey": "2bf5127c73a113bf09a0766d9cd9f0ee9ff75b959ed881d65f2d036610ad4b16",
"created_at": 1686106016,
"kind": 1,
"tags": [
[
"e",
"f45e7ca88e6eb3dd1e645e8e3cbb476c5b24e8003cb71eebe205594bb2a4d152",
"",
"root"
],
[
"e",
"c10d4961e97c342090fa30a54690e02cc1a48811205a35c46c3ecfd9ecbe35e0",
"",
"reply"
],
[
"p",
"308e0d1efb1707ac6b92cd0b19c304882b3919f4bd59336c4a718c159bdcf63b"
]
],
"content": "📅 Original date posted:2011-12-15\n🗒️ Summary of this message: Combining DNSSEC TXT record and HTTPS proposal could provide the dynamism of HTTPS without a rigid URL scheme for querying the server.\n📝 Original message:Could we combine this proposal and the HTTPS proposal?\n\nThe DNSSEC TXT record could give instructions on how to query an HTTPS server to get the address. Then we get the dynamism of HTTPS without having a rigid URL scheme for querying the server along with the advantages of DNSSEC.\n\n\n--- On Wed, 12/14/11, Rick Wesson \u003crick at support-intelligence.com\u003e wrote:\n\n\u003e From: Rick Wesson \u003crick at support-intelligence.com\u003e\n\u003e Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases\n\u003e To: \"Luke-Jr\" \u003cluke at dashjr.org\u003e\n\u003e Cc: bitcoin-development at lists.sourceforge.net\n\u003e Date: Wednesday, December 14, 2011, 8:22 PM\n\u003e understand that not *everyone* wants\n\u003e or will adhere to that best\n\u003e practice and in my NSHO it isn't.\n\u003e \n\u003e -rick\n\u003e \n\u003e 2011/12/14 Luke-Jr \u003cluke at dashjr.org\u003e:\n\u003e \u003e On Wednesday, December 14, 2011 6:02:25 PM Rick Wesson\n\u003e wrote:\n\u003e \u003e\u003e I also am largely in favor of using secured zones\n\u003e to publish TXT\n\u003e \u003e\u003e records to digital currencies. I've been thinking\n\u003e mainly about TXT\n\u003e \u003e\u003e using the following format for bitcoin.\n\u003e \u003e\u003e\n\u003e \u003e\u003e _btc.\u003clhs\u003e.\u003crhs\u003e\n\u003e \u003e\n\u003e \u003e Don't confuse BTC (Bitcoin unit) with BC (Bitcoin in\n\u003e general / protocol)...\n\u003e \u003e The hard part of using DNS will be sticking to the\n\u003e standard good practice of\n\u003e \u003e using a new address for every transaction.\n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e 10 Tips for Better Server Consolidation\n\u003e Server virtualization is being driven by many needs. \n\u003e \n\u003e But none more important than the need to reduce IT\n\u003e complexity \n\u003e while improving strategic productivity. Learn More! \n\u003e http://www.accelacomm.com/jaw/sdnl/114/51507609/\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e",
"sig": "8e659847c024a9b934825647c8072ecde7ec8a767f58c30459575e577ab484103b7169e451ffb3160b9930d6f8a1765bf9ee4dc43b86831ed1212fc95f3c1eb0"
}