[dnstap] creating infromational RFC

[Robert Edmonds]

Merike Kaeo wrote:
> It was decided that we should write an Informational RFC to document current dnstap capabilities and I offered to shepherd the editing of this document.  If you are interested in being a co-author, please send me a note (or reply to this list).  I spoke with Matt Poundsett at NANOG 2 days ago and he kindly sent me info on markdown so I wouldn’t have to revert to ‘vi’ and hand-edit html (yes, I used to edit some rfcs that way) and has offered to create the initial template.  THANK YOU!!

Before we get started on an I-D, I think it would be prudent to get an
answer to whether an RFC (even an informational RFC) can specify
something that depends on an unspecified wire encoding like Protocol
Buffers 2.

E.g., there are plenty of RFCs that specify an XML format and cite a
non-IETF standard (XML is apparently under W3C change control), so it's
no problem to write an I-D that depends on another standards
organization's spec. But TTBOMK there's no actual specification for the
PB2 wire format.

The simplest thing to do would be to find an RFC that specifies
something in terms of Protocol Buffers and use that as precedent, I
guess.

BTW, the closest thing to a PB2 wire format spec is the expired I-D
https://datatracker.ietf.org/doc/draft-rfernando-protocol-buffers/.

-- 
Robert Edmonds