DNS Extensions to Support IP Version 6
draft-ietf-dnsext-rfc1886bis-03
Revision differences
Document history
Date | Rev. | By | Action |
---|---|---|---|
2003-10-14
|
03 | (System) | Ballot has been issued |
2003-10-14
|
03 | (System) | [Ballot Position Update] New position, Yes, has been recorded for Erik Nordmark |
2003-10-14
|
03 | (System) | Created "Approve" ballot |
2003-10-14
|
03 | (System) | Ballot writeup text was added |
2003-10-14
|
03 | (System) | Ballot approval text was added |
2003-07-22
|
03 | Natalia Syracuse | State Changes to RFC Ed Queue from Approved-announcement sent by Syracuse, Natalia |
2003-07-16
|
03 | Michael Lee | State Changes to Approved-announcement sent from Approved-announcement to be sent :: Point Raised - writeup needed by Lee, Michael |
2003-07-16
|
03 | (System) | IESG has approved the document |
2003-07-10
|
03 | Amy Vezza | State Changes to Approved-announcement to be sent :: Point Raised - writeup needed from IESG Evaluation by Vezza, Amy |
2003-07-01
|
03 | Michael Lee | State Changes to IESG Evaluation from In Last Call by Lee, Michael |
2003-06-05
|
03 | Amy Vezza | Status date has been changed to 2003-06-17 from |
2003-06-05
|
03 | Amy Vezza | State Changes to In Last Call from Last Call Requested by Vezza, Amy |
2003-06-03
|
03 | Erik Nordmark | State Changes to Last Call Requested from AD Evaluation by Nordmark, Erik |
2003-06-03
|
03 | (System) | Last call sent |
2003-05-27
|
03 | (System) | New version available: draft-ietf-dnsext-rfc1886bis-03.txt |
2003-05-26
|
03 | Erik Nordmark | State Changes to AD Evaluation :: AD Followup from AD Evaluation :: Revised ID Needed by Nordmark, Erik |
2003-03-04
|
02 | (System) | New version available: draft-ietf-dnsext-rfc1886bis-02.txt |
2003-02-13
|
03 | Erik Nordmark | The interoperability report identifies some RR types for which AAA additional section processing makes sense that are not explicitly specified in the draft: … The interoperability report identifies some RR types for which AAA additional section processing makes sense that are not explicitly specified in the draft: * CNAME records (not mentioned in RFC1886) * PTR records (mentioned in RFC1886, but not explicitly) * SRV records (not mentioned in RFC1886) * SOA records (not mentioned in RFC1886) Wouldn't it make sense to add explicit mention of those types to section 3 (right now the section says for example NS and MX). > Normative References For this document to become a draft standard all normative references need to be draft standard or higher. > [4] Gilligan, R., and E. Nordmark, "Transition Mechanisms for IPv6 > Hosts and Routers", RFC 2893, FreeGate Corp., Sun Microsystems > Inc., August 2000. > This RFC is being updated. The current draft is > "draft-ietf-ngtrans-mech-v2-00.txt", Gilligan, R., and > E. Nordmark, July 17, 2002 Is this really a normative reference i.e. something that one needs to read and understand in order to implement RFC1886bis? Also, [5] through [8] seems like informative references. (But [3] is normative for the textual representation.) |
2003-02-13
|
03 | Erik Nordmark | Draft Added by Nordmark, Erik |
2002-11-04
|
01 | (System) | New version available: draft-ietf-dnsext-rfc1886bis-01.txt |
2002-09-11
|
00 | (System) | New version available: draft-ietf-dnsext-rfc1886bis-00.txt |