From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/5189 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Remaining tasks on resolver overhaul Date: Mon, 2 Jun 2014 05:18:48 -0400 Message-ID: <20140602091848.GA30569@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1401700754 2627 80.91.229.3 (2 Jun 2014 09:19:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 2 Jun 2014 09:19:14 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-5194-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jun 02 11:19:08 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1WrOOZ-0005SB-Rf for gllmg-musl@plane.gmane.org; Mon, 02 Jun 2014 11:19:07 +0200 Original-Received: (qmail 15433 invoked by uid 550); 2 Jun 2014 09:19:03 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 15425 invoked from network); 2 Jun 2014 09:19:03 -0000 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:5189 Archived-At: The vast majority of what I'd call the resolver overhaul is done now, but a few things remain that don't have an impact on the architecture and design, but which still might be a lot of work: - Sorting results per RFC 3484 or at least a subset of its rules. - AI_ADDRCONFIG -- but maybe the current implementation of it as a nop is actually best; see https://fedoraproject.org/wiki/Networking/NameResolution/ADDRCONFIG - IDN support. - IPv6 scope-id parsing. - One remaining legacy resolver function: dn_comp. - And most importantly: REVIEW AND TESTING. We're behind schedule for the roadmap, so of the above items, the ones I'd really like to focus on for release are those which most impact IPv6 usability. Since we have some resolver items remaining to work on, as well as a lot of secondary targets that don't look like they're going to make it for 1.1.2, I may update the roadmap to insert an extra release cycle before the next one. I'd like comments on what should be prioritized at this point. And of course any bug reports/regressions associated with the recent commits. Rich