IETF Logo Mail Archive

Re: [Roll] Multi-Link Subnets via /128

Carsten Bormann <cabo@tzi.org> Thu, 25 July 2013 21:33 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0356721F859A; Thu, 25 Jul 2013 14:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyU71SimJYpx; Thu, 25 Jul 2013 14:33:21 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB5321F8528; Thu, 25 Jul 2013 14:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r6PLXE7K028674; Thu, 25 Jul 2013 23:33:14 +0200 (CEST)
Received: from [192.168.217.105] (p54890BA4.dip0.t-ipconnect.de [84.137.11.164]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4B1E34F7; Thu, 25 Jul 2013 23:33:14 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CE16D142.225DC%d.sturek@att.net>
Date: Thu, 25 Jul 2013 23:33:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C27A5ED-8104-49DB-8320-E9D76FBF8834@tzi.org>
References: <CE16D142.225DC%d.sturek@att.net>
To: Don Sturek <d.sturek@att.net>
X-Mailer: Apple Mail (2.1508)
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Subject: Re: [Roll] Multi-Link Subnets via /128
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2013 21:33:26 -0000

On Jul 25, 2013, at 22:09, Don Sturek <d.sturek@att.net> wrote:

> My problem with RFC 5889 (http://tools.ietf.org/html/rfc5889) is that it
> solves the problem simply by saying "don't allocate link locals".   The
> issue I have is that it precludes the use of mDNS (which operate off of
> link locals).

It would be easy to run mDNS in a larger multicast scope than link-local.
(I'm ignoring scaling limitations here, which are not that relevant in a home as long as you have enough power for everyone.  If you don't, mDNS wasn't the right answer in the first place.)

But first, you would need to run a multicast routing protocol.
That appears to be the larger problem with running mDNS in a multi-subnet network domain.

I happen to believe that running a DNS-SD style service discovery protocol across subnets is significantly easier than running multicast routing across subnets and then running mDNS on that multicast routing.

I'm not sure the RFC 5889 model is creating any problem here that we didn't already have as soon as we started to do routing.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email