120 commits

Author	SHA1	Message	Date
Warren Kumari	6de3cb0606	Remove refernce to "PDNSCERTAT" ... We had said that we desribing the format of 4 systems, but then listed 5, so this is an easy change :-)	2024-08-30 13:42:29 -04:00
Warren Kumari	b7fdcf4187	Address Eliot's initial ISE comments, move to RFCv3 XML format.	2024-08-27 13:57:50 -04:00
Alexandre Dulaunoy	a3875a15b4	chg: [I-D] version 12 published ... Ref: https://datatracker.ietf.org/doc/draft-dulaunoy-dnsop-passive-dns-cof/	2024-06-05 07:24:47 +02:00
Warren Kumari	f250a03773	Minor grammer fixes	2024-06-02 19:59:15 -04:00
Warren Kumari	d1ec787c9c	More XML format fixes. ... This is mostly fixing long lines, whitespace, etc. Should be basically jsut editorial, not substantive.	2024-05-10 18:30:20 -04:00
Warren Kumari	14a31f7623	Only xmllint fixes ... Confirmed by running xml2rfc and checking that the resulting .txt matches the prior version.	2024-05-10 18:12:17 -04:00
Alexandre Dulaunoy	8f3b8cf443	chg: [privacy] simplified as at the end the risk is mainly to find out who did the query	2024-05-09 11:35:08 +02:00
Alexandre Dulaunoy	24bf267e05	chg: [pdns] answers might be empty, inconsistent and different across different Passive DNS	2024-05-09 11:31:20 +02:00
Warren Kumari	83a2c5eb23	Initial WK edits ... Mostly grammar and some typos. Also includes 2 questions (in square brackets)	2024-05-08 09:29:32 -04:00
Alexandre Dulaunoy	79eba307f9	new: [pdns-cof] new format added	2024-04-27 09:35:04 +02:00
Alexandre Dulaunoy	eb3aecbc5f	chg: [pdns-cof] Added Warren as co-author and various fixes to avoid warning in xml2rfc	2024-04-27 09:26:13 +02:00
Peder Stray	da3c1c9395	Add clarification of JSON value type to some fields	2022-09-09 13:46:51 +02:00
Peder Stray	c0b4691f0f	Updated ABNF to fix inconsistencies ... - LF (not CR) for entry separators - fix double quotation of futureField	2022-09-09 13:45:22 +02:00
Alexandre Dulaunoy	16d0a10500	fix: [I-D] country code for US/USA	2022-02-11 12:01:15 +01:00
Ben April	59fdf304b7	small grammar fix	2021-05-08 08:49:16 -04:00
Ben April	74be99319e	ABNF grammar was missing new time_*_ms fields	2021-05-08 08:48:55 -04:00
Alexandre Dulaunoy	1a2d911cf7	chg: [ref] D4 project - date fixed	2021-05-05 09:17:35 +02:00
aaronkaplan	be9de2de88	Add a section on MIME types. Closes issue #9.	2021-05-04 16:04:58 +02:00
aaronkaplan	ceaee596ea	Add section on solving issue #17. I think this can be closed now. ... Not elegant, but works and makes the fsio output compatible.	2021-04-27 13:32:51 +02:00
AaronK	b9eb2af3d2	Update pdns-qof.xml ... Update Aaron's contact infos. Not with CERT.at anymore	2021-04-27 12:54:49 +02:00
AaronK	c8571d2628	Update pdns-qof.xml ... be a bit more specific on what JSON data type rrname field is.	2021-04-27 12:54:48 +02:00
Alexandre Dulaunoy	9f07b31e6e	chg: [07] updates	2020-06-25 14:58:23 +02:00
Alexandre Dulaunoy	ffbc74ef9f	new: [millisecond resolution] time_first_ms and time_last_ms added	2020-06-25 14:49:48 +02:00
Paul Vixie	162f90f3cc	finish prior change, thanks djw	2019-07-25 20:46:40 +00:00
paul vixie	25766cb2b2	Update pdns-qof.xml ... origin can't be a URI because the responder has no reason to know the access method (HTTP vs HTTPS for example, or others in the future) that the requestor used to reach the service. what's important is to provide a unique origin name for this row, so as to disambiguate it from other rows which may have the same name and type but a different rrset. for that we need only a domain name, which we might actually prefer to represent in the web's and SNMP's resource style, as in, .info.dnsdb.api rather than api.dnsdb.info. for now i've assumed that we'll use a domain name, which will be the service's understanding of its advertised name, rather than as a URI, which could include a lot of details that the origin server will not know. if a URI is given by some pre-standard server, then only its domain name will be meaningful.	2019-07-24 19:46:13 -06:00
Alexandre Dulaunoy	9fed1e424b	chg: [I-D] house keeping before submission	2019-04-08 14:50:33 +02:00
David Waitzman	545af5573d	Allow single-string result for RDATA to be an Array. ... Clarify that examples do not require that multiple objects be returned by a single query. Clarify that list of rrtypes is not exhaustive. Fix various document lint.	2019-04-08 08:26:12 -04:00
Alexandre Dulaunoy	1e29c28a20	chg: [cof] Updated reference to Passive DNS implementing COF and DNSDBq added	2019-02-10 12:26:55 +01:00
Alexandre Dulaunoy	fe3ee30aa7	fix: CIRCL address	2018-06-20 21:57:14 +02:00
Alexandre Dulaunoy	01778789d6	add: clarification that the document is covering current best practices ... and a simple explanation of the GDPR aspect	2018-06-20 21:54:52 +02:00
Alexandre Dulaunoy	d1d739b7c7	New release updated	2017-06-13 05:59:13 +02:00
Alexandre Dulaunoy	1949ed9487	Added an optional prefix to the sensor_id based on discussion regarding ... public measurement system or/and other public system gathering DNS passively.	2017-04-22 11:08:50 +02:00
Alexandre Dulaunoy	2bc5ece42d	02 updates added	2017-04-16 18:17:45 +02:00
Alexandre Dulaunoy	9e23c318fa	Spaces removed - origin missing added	2015-11-13 21:33:06 +01:00
Alexandre Dulaunoy	40e94f4bf1	New release 01	2015-11-13 09:43:00 +01:00
Alexandre Dulaunoy	8515acb5ee	CIRCL Passive DNS link fixed	2015-11-13 09:25:00 +01:00
Alexandre Dulaunoy	85f76d2658	origin added as an additional field	2015-11-13 09:23:28 +01:00
Alexandre Dulaunoy	06a6673fcd	Update for WG DNSOP	2014-04-04 12:14:30 +02:00
Aaron Kaplan	e3d8f07fbc	clarified sensor_id according to discussion with Tony Finch	2014-02-27 18:52:06 +01:00
Aaron Kaplan	94e89223b5	fixed ABNF, updated TODO.md	2014-02-27 14:45:32 +01:00
Alexandre Dulaunoy	39f6aa6c28	Prepare for 02 (to be published in February)	2014-02-02 08:41:05 +01:00
Alexandre Dulaunoy	d6f34b8f1c	Prepared for 02 publication	2014-02-02 08:40:25 +01:00
Alexandre Dulaunoy	20c869ae7d	Typo fixed	2014-02-02 08:31:00 +01:00
Alexandre Dulaunoy	395ba68c94	Clarification of the sensor_id -> JSON string / note for escaping. ... Aaron: could you check if your implementation is ok?	2014-02-02 08:29:10 +01:00
Alexandre Dulaunoy	5bdbb3ab8f	String value of resource records must be escaped as ... defined in the JSON RFC.	2014-02-02 08:24:59 +01:00
Alexandre Dulaunoy	1f63e5e847	Clarification for JSON output	2014-02-02 08:09:48 +01:00
Alexandre Dulaunoy	43ae01e56e	Clarification for all JSON types. (dnsop feedback)	2014-02-02 07:58:10 +01:00
Alexandre Dulaunoy	195da6bad8	time_first and time_last are JSON numbers. (dnsop feedback)	2014-02-02 07:50:16 +01:00
Alexandre Dulaunoy	ed1ed0a78e	zone file -> master file (dnsop feedback)	2014-02-02 07:46:16 +01:00
Alexandre Dulaunoy	a121fb4e7d	rdata clarification (dnsop feedback) ... If resource records are multiple, an array is returned. Each record from the array is represented as a JSON string. If resource record returned is signle, it's a string.	2014-02-02 07:43:24 +01:00