Re: [mdnsext] mDNSext features/requirements rollup
RJ Atkinson <rja.lists@gmail.com> Fri, 15 February 2013 15:26 UTC
Return-Path: <rja.lists@gmail.com>
X-Original-To: mdnsext@ietfa.amsl.com
Delivered-To: mdnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B94C921F8569 for <mdnsext@ietfa.amsl.com>; Fri, 15 Feb 2013 07:26:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.568
X-Spam-Level:
X-Spam-Status: No, score=-3.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-hsUEPifGsP for <mdnsext@ietfa.amsl.com>; Fri, 15 Feb 2013 07:26:21 -0800 (PST)
Received: from mail-vb0-f50.google.com (mail-vb0-f50.google.com [209.85.212.50]) by ietfa.amsl.com (Postfix) with ESMTP id B929821F850F for <mdnsext@ietf.org>; Fri, 15 Feb 2013 07:26:21 -0800 (PST)
Received: by mail-vb0-f50.google.com with SMTP id ft2so2177784vbb.37 for <mdnsext@ietf.org>; Fri, 15 Feb 2013 07:26:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=3f4lsOEXS/ntJLwOazEoEAPfYjfg2WA+HADIIji2tc8=; b=vWGraKNsvGyEfEllTEWiE2TGrUX+GWdwCu4dcsNAd/F6BsZcfyCNRjuCy8g2hDXajR BqLjTEOuFp0Twj28zqBABJHW6xFw0Y1OOA3nLur6Uh6nKmwF86TDIUxJh1Z0g6WC9k/m gsVE953AjcQ8BYy2VVLxLGV99XllTF9VUMfCDhrdxA3UiFB/hl94buXY6H1YDk6DHli8 xavgJ+3Ft+uxFHTitnzBoNLeFza6rjbn4OX/CVTtg5C+6mSSEpgGtokJOMXLZmoyZLMw M9ykyrdnpil+gQXOIxHPq4U3Rd6IWq86QNaGBExulVSNxx3DyBQqUqWSTSPy3Q+1ZdNZ mIXQ==
X-Received: by 10.52.27.138 with SMTP id t10mr3188485vdg.59.1360941981040; Fri, 15 Feb 2013 07:26:21 -0800 (PST)
Received: from [10.30.20.13] (pool-96-255-149-117.washdc.fios.verizon.net. [96.255.149.117]) by mx.google.com with ESMTPS id pa4sm67941893veb.1.2013.02.15.07.26.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Feb 2013 07:26:20 -0800 (PST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Apple Message framework v1283)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <511DD320.7080003@umn.edu>
Date: Fri, 15 Feb 2013 10:26:19 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <EDA5A407-1A85-4F51-877F-23F73732C086@gmail.com>
References: <4D4B5680-EF92-4646-957F-5FF4E588DFEF@gmail.com> <511DD320.7080003@umn.edu>
To: mdnsext@ietf.org
X-Mailer: Apple Mail (2.1283)
Subject: Re: [mdnsext] mDNSext features/requirements rollup
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <mdnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mdnsext>
List-Post: <mailto:mdnsext@ietf.org>
List-Help: <mailto:mdnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 15:26:22 -0000
On 15 Feb 2013, at 01:18 , David Farmer wrote: > So the routers are in the idea location to do this, but I'm > really concerned about the instability adding more network state > into the routers. I have operational experience with large-scale (e.g. campus wide) deployments of AppleTalk over Ethernet that used low-cost (and by today's standards) very very low performance CPUs (e.g. 68K) with tiny amounts of RAM. The AppleTalk service advertisement proxying and zone advertisement proxying did NOT create any sort of instability. Back in those days, the deployed world was multi-protocol with some DECnet, some IP, a lot of IPX, and some other stuff besides, so there was a lot more state that needed to be kept inside the routers. With today's IP-centric world, the state needed in routers is much less, generally just a bridge table, an IPv4 RIB/FIB and an IPv6 RIB/FIB. Further, unlike back then, the actual packet forwarding generally does not involve the switch/router CPU or the RAM associated with the CPU. Instead, commodity or custom packet processing ASICs handle the heavy lifting today, and most of the other state (e.g. bridge table, IPv4 & IPv6 FIBs) is stored separately in commodity TCAM. So modern enterprise switches have tons of spare RAM and A LOT more CPU to spare than those devices did back in the 1990s. > While in large scale enterprise routers we try to make > things as stateless as possible, ideally the routing table only, > and we are supporting 2500 to 7500 devices with a single > large scale router. Back in the day, tiny (68K + smallish RAM) AppleTalk (EtherTalk) routers were supporting 2000+ devices successfully -- without instability. Today's enterprise routers and L3 switches are MUCH more capable, with more spare capacity. So my operational experience says that this is not a real problem, provided we are ordinarily sensible. For one thing, mDNS information ought to be "soft state", that regularly expires in some sensible way, and gets tossed and relearned when someone chooses to reboot (or significantly reconfigure without rebooting) some router or L3 switch. Yours, Ran
- [mdnsext] mDNSext features/requirements rollup Alf Watt
- [mdnsext] mDNSext features/requirements rollup RJ Atkinson
- [mdnsext] mDNSext features/requirements rollup RJ Atkinson
- Re: [mdnsext] mDNSext features/requirements rollup Andrew Sullivan
- Re: [mdnsext] mDNSext features/requirements rollup nudge
- Re: [mdnsext] mDNSext features/requirements rollup Andrew Sullivan
- Re: [mdnsext] mDNSext features/requirements rollup Brian Dickson
- Re: [mdnsext] mDNSext features/requirements rollup Andrew Sullivan
- Re: [mdnsext] mDNSext features/requirements rollup Tim Chown
- Re: [mdnsext] mDNSext features/requirements rollup David Farmer
- Re: [mdnsext] mDNSext features/requirements rollup David Farmer
- Re: [mdnsext] mDNSext features/requirements rollup peter van der Stok
- Re: [mdnsext] mDNSext features/requirements rollup RJ Atkinson
- Re: [mdnsext] mDNSext features/requirements rollup Dan Harkins
- Re: [mdnsext] mDNSext features/requirements rollup Alf Watt
- Re: [mdnsext] mDNSext features/requirements rollup Stephen Orr (sorr)
- Re: [mdnsext] mDNSext features/requirements rollup nudge
- Re: [mdnsext] mDNSext features/requirements rollup David Farmer
- Re: [mdnsext] mDNSext features/requirements rollup vortex
- Re: [mdnsext] mDNSext features/requirements rollup Andrew Sullivan
- Re: [mdnsext] mDNSext features/requirements rollup vortex
- [mdnsext] mDNSext features/requirements rollup Olivier Levon
- Re: [mdnsext] mDNSext features/requirements rollup James Andrewartha
- Re: [mdnsext] mDNSext features/requirements rollup Andrew Sullivan
- Re: [mdnsext] mDNSext features/requirements rollup James Andrewartha
- Re: [mdnsext] mDNSext features/requirements rollup RJ Atkinson
- Re: [mdnsext] mDNSext features/requirements rollup Michael Richardson
- Re: [mdnsext] mDNSext features/requirements rollup Michael Richardson
- Re: [mdnsext] mDNSext features/requirements rollup Andrew Sullivan
- Re: [mdnsext] mDNSext features/requirements rollup David Farmer
- Re: [mdnsext] mDNSext features/requirements rollup David Farmer
- Re: [mdnsext] mDNSext features/requirements rollup David Farmer
- Re: [mdnsext] mDNSext features/requirements rollup RJ Atkinson
- Re: [mdnsext] mDNSext features/requirements rollup RJ Atkinson
- Re: [mdnsext] mDNSext features/requirements rollup RJ Atkinson
- Re: [mdnsext] mDNSext features/requirements rollup Joe Touch
- Re: [mdnsext] mDNSext features/requirements rollup RJ Atkinson
- Re: [mdnsext] mDNSext features/requirements rollup Joe Touch
- Re: [mdnsext] mDNSext features/requirements rollup RJ Atkinson
- Re: [mdnsext] mDNSext features/requirements rollup Johnson, Neil M
- Re: [mdnsext] mDNSext features/requirements rollup Joe Touch