@techreport{mglt-homenet-dnssec-validator-dhc-options-02,
    number =    {draft-mglt-homenet-dnssec-validator-dhc-options-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-mglt-homenet-dnssec-validator-dhc-options/02/},
    author =    {Daniel Migault},
    title =     {{DNSSEC Validators DHCP Options}},
    pagetotal = 12,
    year =      2013,
    month =     oct,
    day =       21,
    abstract =  {DNSSEC provides data integrity and authentication for DNSSEC validators. However, without valid trust anchor(s) and an acceptable value for the current time, DNSSEC validation cannot be performed. As a result, there are multiple cases where DNSSEC validation MUST NOT be performed. In addition, this list of exceptions is expected to become larger over time. Considering an increasing number of cases where DNSSEC is disabled adds complexity to the DNSSEC validator implementations and increases the vectors that disable security. This document assumes that DNSSEC adoption by end devices requires that end devices MUST be able to support a DNSSEC validation always set. This MUST be valid today as well as in the future. This document describes DHCP Options to provision the DHCP Client with valid trust anchors and time so DNSSEC validation can be performed.},
}