Ok, it is a nit, as is much of what idnits produces ;-). I have no problem ignoring idnits on this one ... Thanks, --David > -----Original Message----- > From: barryleiba.mailing.lists@xxxxxxxxx > [mailto:barryleiba.mailing.lists@xxxxxxxxx] On Behalf Of Barry Leiba > Sent: Friday, December 05, 2014 5:39 PM > To: Black, David > Cc: nico@xxxxxxxxxxxxxxxx; General Area Review Team (gen-art@xxxxxxxx); ops- > dir@xxxxxxxx; ietf@xxxxxxxx; json@xxxxxxxx > Subject: Re: Gen-ART and OPS-Dir review of draft-ietf-json-text-sequence-09 > > Hi, David. One note on your review: > > > idnits didn't like the reference to RFC 20 for ASCII: > > > > ** Downref: Normative reference to an Unknown state RFC: RFC 20 > > > > RFC 5234 (ABNF) uses this, which looks like a better reference: > > > > [US-ASCII] American National Standards Institute, "Coded Character > > Set -- 7-bit American Standard Code for Information > > Interchange", ANSI X3.4, 1986. > > Except that (1) many IETF documents do use RFC 20 and (2) the RFC 20 > reference is not for ASCII: it's for RS, the Record Separator > character, which is explained in RFC 20, Section 5.2. > > Barry