IETF Logo Mail Archive

Re: [mdnsext] Hierarchical (host) domain names in mDNS?

"Albrecht, Harald" <harald.albrecht@siemens.com> Wed, 17 July 2013 07:39 UTC

Return-Path: <harald.albrecht@siemens.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 7CCA121F9C86 for <mdnsext@ietfa.amsl.com>; Wed, 17 Jul 2013 00:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.799
X-Spam-Level:
X-Spam-Status: No, score=-9.799 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 K9ceazXH4NgW for <mdnsext@ietfa.amsl.com>; Wed, 17 Jul 2013 00:39:12 -0700 (PDT)
Received: from lizzard.sbs.de (lizzard.sbs.de [194.138.37.39]) by ietfa.amsl.com (Postfix) with ESMTP id AEDFA21F8C71 for <mdnsext@ietf.org>; Wed, 17 Jul 2013 00:39:11 -0700 (PDT)
Received: from mail1.sbs.de (localhost [127.0.0.1]) by lizzard.sbs.de (8.13.6/8.13.6) with ESMTP id r6H7dAwn011953 for <mdnsext@ietf.org>; Wed, 17 Jul 2013 09:39:10 +0200
Received: from defthw99et6msx.ww902.siemens.net ([157.163.148.61]) by mail1.sbs.de (8.13.6/8.13.6) with ESMTP id r6H7dAvs031195 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mdnsext@ietf.org>; Wed, 17 Jul 2013 09:39:10 +0200
Received: from DEFTHW99ER8MSX.ww902.siemens.net (139.22.70.73) by DEFTHW99ET6MSX.ww902.siemens.net (157.163.148.61) with Microsoft SMTP Server (TLS) id 8.3.298.1; Wed, 17 Jul 2013 09:39:10 +0200
Received: from DEFTHW99EK5MSX.ww902.siemens.net ([169.254.6.109]) by DEFTHW99ER8MSX.ww902.siemens.net ([139.22.70.73]) with mapi id 14.03.0146.000; Wed, 17 Jul 2013 09:39:10 +0200
From: "Albrecht, Harald" <harald.albrecht@siemens.com>
To: "mdnsext@ietf.org" <mdnsext@ietf.org>
Thread-Topic: [mdnsext] Hierarchical (host) domain names in mDNS?
Thread-Index: Ac6CGBuBlctNJJX5QF6LGwWoRFhvmQACsLGAAADkbwAAJZRPwP//4wgA///c6PA=
Date: Wed, 17 Jul 2013 07:39:09 +0000
Message-ID: <E36F274013087B4EA05E08EB5037503902C30F@DEFTHW99EK5MSX.ww902.siemens.net>
References: <E36F274013087B4EA05E08EB5037503902C1DC@DEFTHW99EK5MSX.ww902.siemens.net> <CABOxzu27u5BMTZq2WKFk5O4nmLG87BXCdG6+M7+MeB-ZugDN9Q@mail.gmail.com> <20130716151444.GE23286@mx1.yitter.info> <E36F274013087B4EA05E08EB5037503902C2BA@DEFTHW99EK5MSX.ww902.siemens.net> <CAAedzxr8jQOCq9f4gwCLyL32iua0WzhRUbYdeN6u8BWfb35=FQ@mail.gmail.com>
In-Reply-To: <CAAedzxr8jQOCq9f4gwCLyL32iua0WzhRUbYdeN6u8BWfb35=FQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [139.22.70.37]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [mdnsext] Hierarchical (host) domain names in mDNS?
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: Wed, 17 Jul 2013 07:39:18 -0000

Hi Erik,

unfortunately not; I need "full A/AAAA connectivity", that is, we're not talking about a particular "transport" HTTP, but I need support for all transports that sit on top of IP, either directly or indirectly. Also, there is nothing such as a central "portal", that is, a web server that acts as the entrance to the individual systems.

For instance, our S7 controllers allow our customers to programmatically use TCP connections right from their control programs ... and there's a great demand of that. So, customers need to be able to either address within the same domain level, such as the "hmi" connecting to the "controller". But there's also need for inter-machine synchronization (or inter-cell), that is, "controller.machine1...." to "controller.machine2....".

At these levels, our customers only accept decentralized and administration-free technologies for name resolution. Only at much higher levels DNS is acceptable, such as when having to loosely connect different plants, et cetera.

With best regards,
Harald Albrecht

--- I have to add the following due to local law; let's hope that there are no other places with a law forbidding to add the following ---
Siemens AG
Industry Sector
Industry Automation Division
Industrial Automation Systems
I IA AS CTO DH 1
Gleiwitzer Str. 555
90475 Nürnberg, Deutschland
Tel: +49 911 895-3847
Fax: +49 911 895-2105
mailto:harald.albrecht@siemens.com

Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme; Vorstand: Peter Löscher, Vorsitzender; Roland Busch, Brigitte Ederer, Klaus Helmrich, Joe Kaeser, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen, Michael Süß; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322 




> -----Ursprüngliche Nachricht-----
> Von: Erik Kline [mailto:ek@google.com]
> Gesendet: Mittwoch, 17. Juli 2013 09:27
> An: Albrecht, Harald
> Cc: mdnsext@ietf.org
> Betreff: Re: [mdnsext] Hierarchical (host) domain names in mDNS?
> 
> Would you be able to suffice with having the smaller nodes (“hmi”,
> “controller”, “stamper”, “former”, “cooler”) be identifiable as services
> offered via machine1 and machine2?  If all that any external elements are
> doing is trying to talk to some specific service on those nodes (REST-ful HTTP
> server, etc), could machine1 advertise _hdmi, _controller, _stamper, ...
> services?

v2.23.0 | Report a Bug | By Email