openbsd/src/lib/libc/net, branch OPENBSD_5_3 A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_5_3 2012-12-12T14:48:18+00:00 document RES_USE_DNSSEC; text tweaked by sthen 2012-12-12T14:48:18+00:00 jmc 2012-12-12T14:48:18+00:00 urn:sha1:5390e88e5040ac2e548c6ed2a9a95a922af70ceb ok jakob - put the various options into the same order as those in resolv.h 2012-11-29T21:37:13+00:00 jmc 2012-11-29T21:37:13+00:00 urn:sha1:65ac11cbc13d2fb936e90bc4c3a42f19fd2b69a0 - sync RES_DEBUG with resolv.conf.5 - document RES_PRIMARY, but mark it unsupported (like we already do for RES_AAAONLY) - use the exact same text (about being enabled by default) for RES_RECURSE as for the other two defaults - document RES_INSECURE{1,2} - description lifted from resolv.conf.5 - document RES_NOALIASES - mostly sync the RES_USE_EDNS0 text with resolv.conf.5 - RES_USE_DNSSEC not documented for now. something to come... ok sthen remove some useless Tn and double punctuation; 2012-11-19T16:39:30+00:00 jmc 2012-11-19T16:39:30+00:00 urn:sha1:56871b4a45dddb86ea25cefad97ab0d07b31758d RES_IGNTC is no longer ignored; ok sthen 2012-11-19T16:33:48+00:00 jmc 2012-11-19T16:33:48+00:00 urn:sha1:1b32f1ea0da4dadcec83ed33d98828b8bec36bd1 last stage of rfc changes, using consistent Rs/Re blocks, and moving the 2012-09-27T11:31:58+00:00 jmc 2012-09-27T11:31:58+00:00 urn:sha1:bc685bd401e5657f7fb51b4e1a62a7a5c5ea4098 references into a STANDARDS section; rfc 2553 (not 2533) has been replaced by rfc 3493; 2012-08-22T18:32:47+00:00 jmc 2012-08-22T18:32:47+00:00 urn:sha1:5a5364cf2815efbdd68ffd0e6180da72c076688e - remove inconsistent/obsolete comments 2012-08-21T16:35:16+00:00 jmc 2012-08-21T16:35:16+00:00 urn:sha1:c02396e91c4350facdb9b030e080f7ebe8fc9e10 - update rfc references - make the Rs/Re blocks more consistent flesh out the rfc section; 2012-08-21T06:18:23+00:00 jmc 2012-08-21T06:18:23+00:00 urn:sha1:45afde624cbf6c049af0319df2ff1db4466f730d rfc 5321 replaces 974 and 2821; rfc 4291 replaces rfcs 2373 and 3513; 2012-08-20T19:38:55+00:00 jmc 2012-08-20T19:38:55+00:00 urn:sha1:0852ae3422b0b414e6655de60f314968e3f10cc6 Use same (lame) verbiage to explain ifa_dstaddr as is used for 2012-07-13T09:32:23+00:00 krw 2012-07-13T09:32:23+00:00 urn:sha1:20333a35e7159469107dfd2bb6f664bbd518c4d5 ifa_broadaddr. i.e. make it make clear that this field is only valid for P2P. (Hint: one's a field, and one's a #define giving a new name to said field) ok guenther@