From owner-freebsd-current@FreeBSD.ORG Sat Nov 2 17:44:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B7C13267; Sat, 2 Nov 2013 17:44:55 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 83A7A2FEF; Sat, 2 Nov 2013 17:44:55 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7DA9320EE5; Sat, 2 Nov 2013 13:44:53 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Sat, 02 Nov 2013 13:44:53 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=cjdrNcUocEhcZlvA8WOTiFsc4Ys=; b=rH hzWORXlIMjZZQk6oU9rdbssfg6NrhDNC+DXVd2vLy4GDhqfF76YXPoW6RkrSddlV XWgY2KHM/O5NREGKDJjI+zyv2cbV/8s5BHsn/ENf9cnX4qm3R34bY+p0OrRB1RDc YQCty/bpO7IgJyLWWFrvZLJICatojeakDj7osQlWo= X-Sasl-enc: mGnncDkZ22To5Jjnzkmjvpu8Zjxo+zAylqQaFoKpWRvR 1383414293 Received: from [172.16.1.145] (unknown [68.117.126.78]) by mail.messagingengine.com (Postfix) with ESMTPA id 9FA8BC00E84; Sat, 2 Nov 2013 13:44:52 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1811\)) Subject: Re: Official FreeBSD Binary Packages now available for pkgng From: Mark Felder In-Reply-To: Date: Sat, 2 Nov 2013 12:44:51 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <0F068420-0A1C-4605-90A8-0D1C1120F222@FreeBSD.org> References: <5271BC11.1010303@FreeBSD.org> <5272D0DE.4080209@FreeBSD.org> <52745B7F.2080608@vangyzen.net> <5274B947.7030607@FreeBSD.org> <1680682c-dc77-4ee3-8e59-ee7356f307a3@email.android.com> <5274D90D.8040508@FreeBSD.org> <20131102113750.GG2951@home.opsec.eu> <5274EFD6.6030504@FreeBSD.org> To: Adrian Chadd X-Mailer: Apple Mail (2.1811) Cc: Kurt Jaeger , freebsd-current , Matthew Seaman X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Nov 2013 17:44:55 -0000 On Nov 2, 2013, at 11:54 AM, Adrian Chadd wrote: > You're using a DNS feature which > isn't well adopted/supported and you haven't provided a fallback > legacy, well tested path. But SRV has been widely deployed since=85 before 2000? It=92s literally = the backbone of Active Directory deployments. Here=92s a list of things = that his company=92s network design probably breaks: * Office 365 (cloud Exchange hosting by Microsoft; requires you use SRV = records to get your company=92s clients pointed to their cloud = infrastructure) * LDAP * SIP * XMPP * CALDAV / CARDDAV * SMTP, IMAP, and POP clients should also obey published SRV records. = Not sure how many clients really do, though. * Teamspeak 3 doesn=92t force you to use SRV, but you can use only SRV = records * Minecraft * Last I knew IRCv4 specs are slated to include SRV as a core feature I can=92t speak for the caching issues, but SRV is pretty active and = only getting more popular because things like =93round robin DNS=94 are = a horrible, ugly, unreliable hack and things like Anycast or Geo-DNS = isn=92t always feasible. -0.02c=