This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/

[dns-wg] What about the last mile, was: getting DNSSEC deployed

• Previous message (by thread): [dns-wg] What about the last mile, was: getting DNSSEC deployed
• Next message (by thread): [dns-wg] What about the last mile, was: getting DNSSEC deployed

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jørgen Hovland jorgen at hovland.cx
Sun Feb 18 22:36:20 CET 2007

----- Original Message ----- 
From: "Max Tulyev" <president at ukraine.su>


> Lutz Donnerhacke wrote:
>
>>> I find those last two statements highly unlikely, but for argument sake,
>>> multiply this by cost(crypto(lastmile))*count(users).
>>
>> I do not see the need for crypto on the last mile.
>
> And what to do with spoofed answers?

256bit nonce/id field instead of 16.

• Previous message (by thread): [dns-wg] What about the last mile, was: getting DNSSEC deployed
• Next message (by thread): [dns-wg] What about the last mile, was: getting DNSSEC deployed

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]