To:
"Dan Maharry" <dan@mcd.coop>, <ietf-provreg@cafax.se>
From:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Date:
Thu, 18 Jan 2007 08:17:39 -0500
Content-class:
urn:content-classes:message
Sender:
owner-ietf-provreg@cafax.se
Thread-Index:
Acc6/Hu3eh8iKzfyQFaBorQDNOUEZwABhddg
Thread-Topic:
[ietf-provreg] RFC3732 App A missing change?
Subject:
RE: [ietf-provreg] RFC3732 App A missing change?
> -----Original Message----- > From: owner-ietf-provreg@cafax.se > [mailto:owner-ietf-provreg@cafax.se] On Behalf Of Dan Maharry > Sent: Thursday, January 18, 2007 7:31 AM > To: ietf-provreg@cafax.se > Subject: [ietf-provreg] RFC3732 App A missing change? > > Hi, > > Just a quick query. I see in RFC3732-bis04 that RFC3513 has > been updated > to RFC4291 but that this update is not listed in Appendix A. Missed that. The reference was changed because the document needs to cite a version that's already at Draft standard status. > Also, Section 7 contains an unformatted <xref> tag. However, I'm not > sure if this is just on > http://www.ietf.org/internet-drafts/draft-hollenbeck-epp-rfc37 > 32bis-04.t > xt where I'm viewing this document. Minor editorial problem. At worst, it'll be fixed by the RFC Editor. This document is in the IESG's hands now. I've asked Ted Hardie (the shepherding AD) if he wants me to fix them or if they can wait for an IESG note or Auth48 fix. Either way, thanks for catching them. -Scott-