Re: [Anima-bootstrap] anima-bootstrap: Bootstrap proxy discovery options

peter van der Stok <stokcons@xs4all.nl> Mon, 07 December 2015 08:54 UTC

Return-Path: <stokcons@xs4all.nl>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBB31B355C for <anima-bootstrap@ietfa.amsl.com>; Mon, 7 Dec 2015 00:54:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ea8s8qnMCE0d for <anima-bootstrap@ietfa.amsl.com>; Mon, 7 Dec 2015 00:54:55 -0800 (PST)
Received: from lb1-smtp-cloud6.xs4all.net (lb1-smtp-cloud6.xs4all.net [194.109.24.24]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D5861B3559 for <anima-bootstrap@ietf.org>; Mon, 7 Dec 2015 00:54:54 -0800 (PST)
Received: from webmail.xs4all.nl ([194.109.20.199]) by smtp-cloud6.xs4all.net with ESMTP id qYus1r0094Hiz6i01Yus4Z; Mon, 07 Dec 2015 09:54:52 +0100
Received: from 2001:983:a264:1:3cbe:4ecd:8c20:6c6d by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Mon, 07 Dec 2015 09:54:52 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Mon, 07 Dec 2015 09:54:52 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: Toerless Eckert <eckert@cisco.com>
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <20151204014333.GZ29056@cisco.com>
References: <20151204014333.GZ29056@cisco.com>
Message-ID: <6471865864850e6c34961f12d45853cd@xs4all.nl>
X-Sender: stokcons@xs4all.nl (232ClssbWmMdZhw+2cS4CjUzU8f9SYRB)
User-Agent: XS4ALL Webmail
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-bootstrap/uYeHD1ZFoDQ3uL7f2_752l1HrEc>
Cc: anima-bootstrap@ietf.org
Subject: Re: [Anima-bootstrap] anima-bootstrap: Bootstrap proxy discovery options
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: consultancy@vanderstok.org
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <anima-bootstrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-bootstrap/>
List-Post: <mailto:anima-bootstrap@ietf.org>
List-Help: <mailto:anima-bootstrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2015 08:54:58 -0000

Hi Toerless,

A few remarks to your extensive e_mail


>    Also comparison with mDNS as we discussed it:
>      - code size: We need GRASP for more functions in AN beside 
> discovery,
>        we do not need mDNS for anything in AN, so on IoT devices we 
> would save
>        code size. TBD: Size of an mDNS stack (note: We MAY want 
> "normal" DNS,
>        so the code size for mDNS may not be that large as a delta on 
> top of
>        "normal" DNS).
>      - Number of packet exchanges (TBD: not clear how much this is a 
> real
>        problem, mDNS may optimize here): mDNS exchange is logical three 
> step:
>        PTR RR lookup -> SRV, TXT RR lookup, AAAA lookup
>      - mDNS being a query/reply exchange wouldn't have the security 
> properties
>        i described above. Unless you abuse it and engineer an MDNS 
> unsolicited
>        announce periodically with all the four RRs included. And i 
> guess
>        one could define a TXT RR with the signed timestamp. Aka: I
> could probably
>        do the same thing i was describing above also with mDNS. Not 
> sure if
>        mDNS people would like that...

I checked mDNS-SD (it is not too complex),
It is sufficient to send a query for the SRV RR containing the required 
service.
(Knowing that your service must exist removes the need for checking its 
existence, so no PTR query).
mDNS should also return the AAAA RR defined by the contents of the SRV 
RR in the same message.
The DNS encoding of the messages is pretty concise. (for example, name 
strings occur only once)

> 
> 2. If 1. failed:  OPTIONAL Discovery of bootstrap proxy via L3
> 
Many installations will have their own brand of service discovery (SD).
Inter-operability of SD is the first objective; we can safely assume 
that if a given brand of SD is used,
the whole installation uses this brand as specified by a SDO that is 
active in this particular market.

I think it is sufficient to state that the proxy service needs to be 
discovered
and how this can be done with DNS-SD (mDNS) or DHCP, the IETF standards.

Greetings,

Peter
> 
> 
> _______________________________________________
> Anima-bootstrap mailing list
> Anima-bootstrap@ietf.org
> https://www.ietf.org/mailman/listinfo/anima-bootstrap