Moving DNSSEC Lookaside Validation (DLV) to Historic Status
status-change-dlv-to-historic-02
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2019-11-04
|
02 | Amy Vezza | The following approval message was sent From: The IESG To: IETF-Announce Cc: The IESG , iana@iana.org, mankin@psg.com, … The following approval message was sent From: The IESG To: IETF-Announce Cc: The IESG , iana@iana.org, mankin@psg.com, draft-andrews-dlv-dns-rr@ietf.org, draft-weiler-dnssec-dlv@ietf.org, warren@kumari.net, rfc-editor@rfc-editor.org Subject: Document Action: DNSSEC Lookaside Validation (DLV) to Historic The IESG has approved changing the status of the following document: - DNSSEC Lookaside Validation (DLV) (rfc5074) to Historic This document action is documented at: https://datatracker.ietf.org/doc/status-change-dlv-to-historic/ A URL of the affected document is: https://datatracker.ietf.org/doc/rfc5074/ Status Change Details: DNSSEC Lookaside Validation (DLV) provided a useful transition mechanism to aid in the deployment of DNSSEC. The DNS root is now signed, as are the majority of TLDs, and so DLV can now be retired - this document, supported by [draft-ietf-dnsop-obsolete-dlv] reclassified RFC4431 and RFC 5074 as historic. Personnel Warren Kumari is the responsible Area Director. |
2019-11-04
|
02 | Amy Vezza | The following approval message was sent From: The IESG To: IETF-Announce Cc: The IESG , iana@iana.org, mankin@psg.com, … The following approval message was sent From: The IESG To: IETF-Announce Cc: The IESG , iana@iana.org, mankin@psg.com, draft-andrews-dlv-dns-rr@ietf.org, draft-weiler-dnssec-dlv@ietf.org, warren@kumari.net, rfc-editor@rfc-editor.org Subject: Document Action: The DNSSEC Lookaside Validation (DLV) DNS Resource Record to Historic The IESG has approved changing the status of the following document: - The DNSSEC Lookaside Validation (DLV) DNS Resource Record (rfc4431) to Historic This document action is documented at: https://datatracker.ietf.org/doc/status-change-dlv-to-historic/ A URL of the affected document is: https://datatracker.ietf.org/doc/rfc4431/ Status Change Details: DNSSEC Lookaside Validation (DLV) provided a useful transition mechanism to aid in the deployment of DNSSEC. The DNS root is now signed, as are the majority of TLDs, and so DLV can now be retired - this document, supported by [draft-ietf-dnsop-obsolete-dlv] reclassified RFC4431 and RFC 5074 as historic. Personnel Warren Kumari is the responsible Area Director. |
2019-11-04
|
02 | Amy Vezza | IESG has approved the status change |
2019-11-04
|
02 | Amy Vezza | Closed "Approve" ballot |
2019-11-04
|
02 | Amy Vezza | RFC Status Change state changed to Approved - announcement sent from Approved - announcement to be sent |
2019-10-31
|
02 | Cindy Morgan | RFC Status Change state changed to Approved - announcement to be sent from IESG Evaluation |
2019-10-29
|
02 | Roman Danyliw | [Ballot Position Update] New position, No Objection, has been recorded for Roman Danyliw |
2019-10-29
|
02 | Alvaro Retana | [Ballot Position Update] Position for Alvaro Retana has been changed to Yes from Discuss |
2019-10-28
|
02 | Adam Roach | Ballot comment text updated for Adam Roach |
2019-10-28
|
02 | Ignas Bagdonas | [Ballot Position Update] New position, No Objection, has been recorded for Ignas Bagdonas |
2019-10-28
|
02 | Suresh Krishnan | [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan |
2019-10-28
|
02 | Mirja Kühlewind | [Ballot Position Update] New position, No Objection, has been recorded for Mirja Kühlewind |
2019-10-25
|
02 | Éric Vyncke | [Ballot Position Update] New position, No Objection, has been recorded for Éric Vyncke |
2019-10-25
|
02 | Cindy Morgan | Telechat date has been changed to 2019-10-31 from 2019-10-03 |
2019-10-25
|
02 | Warren Kumari | New version available: status-change-dlv-to-historic-02.txt |
2019-10-03
|
01 | Martin Vigoureux | [Ballot Position Update] New position, No Objection, has been recorded for Martin Vigoureux |
2019-10-02
|
01 | Benjamin Kaduk | [Ballot comment] No objection other than the topics already under discussion |
2019-10-02
|
01 | Benjamin Kaduk | [Ballot Position Update] New position, No Objection, has been recorded for Benjamin Kaduk |
2019-10-02
|
01 | Alissa Cooper | [Ballot Position Update] New position, No Objection, has been recorded for Alissa Cooper |
2019-10-01
|
01 | Adam Roach | [Ballot comment] I support Alvaro's DISCUSS, and would have entered a similar one myself if he hadn't (but I don't see any reason to have … [Ballot comment] I support Alvaro's DISCUSS, and would have entered a similar one myself if he hadn't (but I don't see any reason to have both of us holding identical DISCUSS positions). I don't think we have a means for updating an otherwise in-force RFC using a "change-to-historic" non-RFC document, and suspect that we at least need sections 3.1.2.1 and 3.1.2.2 published as an RFC. |
2019-10-01
|
01 | Adam Roach | [Ballot Position Update] New position, No Objection, has been recorded for Adam Roach |
2019-10-01
|
01 | Deborah Brungard | [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard |
2019-10-01
|
01 | Magnus Westerlund | [Ballot Position Update] New position, No Objection, has been recorded for Magnus Westerlund |
2019-09-27
|
01 | Alvaro Retana | [Ballot discuss] This process for changing the status to Historic seems to be ok given that the justification is not extensive. However, there is one … [Ballot discuss] This process for changing the status to Historic seems to be ok given that the justification is not extensive. However, there is one detail that I would like to DISCUSS: The text (but not the header) in draft-ietf-dnsop-obsolete-dlv says that it Updates rfc6698 and rfc6840. If not published, then how will the Updates be handled? It seems to me that publishing draft-ietf-dnsop-obsolete-dlv becomes necessary in this case. |
2019-09-27
|
01 | Alvaro Retana | [Ballot comment] [Not related to the action itself... Publishing draft-ietf-dnsop-obsolete-dlv brings up a different discussion because both Updated RFCs are in the Standards Track...but that … [Ballot comment] [Not related to the action itself... Publishing draft-ietf-dnsop-obsolete-dlv brings up a different discussion because both Updated RFCs are in the Standards Track...but that is a topic for another time.] |
2019-09-27
|
01 | Alvaro Retana | [Ballot Position Update] New position, Discuss, has been recorded for Alvaro Retana |
2019-09-23
|
01 | Alexey Melnikov | [Ballot Position Update] New position, No Objection, has been recorded for Alexey Melnikov |
2019-09-20
|
01 | Barry Leiba | [Ballot Position Update] New position, No Objection, has been recorded for Barry Leiba |
2019-09-19
|
01 | Cindy Morgan | Placed on agenda for telechat - 2019-10-03 |
2019-09-19
|
01 | Warren Kumari | [Ballot Position Update] New position, Yes, has been recorded for Warren Kumari |
2019-09-19
|
01 | Warren Kumari | Created "Approve" ballot |
2019-09-19
|
01 | Warren Kumari | RFC Status Change state changed to IESG Evaluation from In Last Call |
2019-09-19
|
01 | Warren Kumari | New version available: status-change-dlv-to-historic-01.txt |
2019-09-04
|
00 | Cindy Morgan | The following Last Call announcement was sent out (ends 2019-10-02): From: The IESG To: IETF-Announce Reply-To: ietf@ietf.org Sender: Subject: Last Call: Moving DNSSEC Lookaside Validation … The following Last Call announcement was sent out (ends 2019-10-02): From: The IESG To: IETF-Announce Reply-To: ietf@ietf.org Sender: Subject: Last Call: Moving DNSSEC Lookaside Validation (DLV) to Historic Status The IESG has received a request to make the following status changes: - RFC4431 from Informational to Historic (The DNSSEC Lookaside Validation (DLV) DNS Resource Record) - RFC5074 from Informational to Historic (DNSSEC Lookaside Validation (DLV)) The supporting document for this request can be found here: https://datatracker.ietf.org/doc/status-change-dlv-to-historic/ and https://datatracker.ietf.org/doc/draft-ietf-dnsop-obsolete-dlv/ The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2019-10-02. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The affected documents can be obtained via https://datatracker.ietf.org/doc/rfc4431/ https://datatracker.ietf.org/doc/rfc5074/ IESG discussion of this request can be tracked via https://datatracker.ietf.org/doc/status-change-dlv-to-historic/ballot/ |
2019-09-04
|
00 | Cindy Morgan | RFC Status Change state changed to In Last Call from Last Call Requested |
2019-09-04
|
00 | Warren Kumari | Last call was requested |
2019-09-04
|
00 | Warren Kumari | Ballot approval text was generated |
2019-09-04
|
00 | Warren Kumari | Ballot writeup was generated |
2019-09-04
|
00 | Warren Kumari | RFC Status Change state changed to Last Call Requested from AD Review |
2019-09-04
|
00 | Warren Kumari | Last call announcement was changed |
2019-09-04
|
00 | Warren Kumari | Last call announcement was generated |
2019-09-04
|
00 | Warren Kumari | New version available: status-change-dlv-to-historic-00.txt |