IETF Logo Mail Archive

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

"Max Pritikin (pritikin)" <pritikin@cisco.com> Tue, 08 December 2015 22:09 UTC

Return-Path: <pritikin@cisco.com>
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 8D10A1A9245 for <anima-bootstrap@ietfa.amsl.com>; Tue, 8 Dec 2015 14:09:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 pAvIw3l7nTXb for <anima-bootstrap@ietfa.amsl.com>; Tue, 8 Dec 2015 14:09:25 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29A3A1A916C for <anima-bootstrap@ietf.org>; Tue, 8 Dec 2015 14:09:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2784; q=dns/txt; s=iport; t=1449612565; x=1450822165; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=exDkQ6IauAQTLcNZNtzIop5On2spAawnUVyfXhea7n4=; b=PM87zJhkyfM1ZkzbrB4nByBnzjeBCHANPuPY6J+FJ43snhyvQT0Yrb3+ mnkqLVPVrCV3iMDzm1pYCnl1ZYDvntbb3OgMYflL8E+VBJdDSdi5f7/ld Pa6K/zpWDQOHK0S0By6fiI5HyhrqMohmz3R7vsegoK9H7cISlvAOlMzdQ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BOAwCYVGdW/4ENJK1egzpTbgaCY7pWAQ2BbhcKhW0CHIEjOBQBAQEBAQEBfwuENAEBAQMBAQEBCRcROgsFCwIBBgIYAgImAgICJQsVEAIEDgWIJwgNkH2dNpBsAQEBAQEBAQEBAQEBAQEBAQEBAQEBFASBAYdigm6Hdy+BFQWHTIcQiAUBjTucbAEfAQFChARyhGiBBwEBAQ
X-IronPort-AV: E=Sophos;i="5.20,400,1444694400"; d="scan'208";a="51631781"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Dec 2015 22:09:24 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id tB8M9OD0004477 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 8 Dec 2015 22:09:24 GMT
Received: from xch-aln-013.cisco.com (173.36.7.23) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 8 Dec 2015 16:09:23 -0600
Received: from xch-aln-013.cisco.com ([173.36.7.23]) by XCH-ALN-013.cisco.com ([173.36.7.23]) with mapi id 15.00.1104.009; Tue, 8 Dec 2015 16:09:23 -0600
From: "Max Pritikin (pritikin)" <pritikin@cisco.com>
To: "consultancy@vanderstok.org" <consultancy@vanderstok.org>
Thread-Topic: [Anima-bootstrap] anima-bootstrap: Bootstrap proxy discovery options
Thread-Index: AQHRLjUzUXhNiuqCZk29llWSg8eoaJ6/ogkAgACqeACAARe8AIAArhwA
Date: Tue, 08 Dec 2015 22:09:23 +0000
Message-ID: <B92B1F02-A2A0-45C4-985A-19CAD00D3EAA@cisco.com>
References: <20151204014333.GZ29056@cisco.com> <6471865864850e6c34961f12d45853cd@xs4all.nl> <5665D85C.5010604@gmail.com> <92ddd96dc21275a00aab797656407971@xs4all.nl>
In-Reply-To: <92ddd96dc21275a00aab797656407971@xs4all.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.99.106.4]
Content-Type: text/plain; charset="utf-8"
Content-ID: <07C5A510247ABB489409435851AFC193@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-bootstrap/fnV6PsZwfBbnY8WC7BleMe8bjvo>
Cc: "Toerless Eckert (eckert)" <eckert@cisco.com>, "anima-bootstrap@ietf.org" <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
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: Tue, 08 Dec 2015 22:09:27 -0000

> On Dec 8, 2015, at 4:46 AM, peter van der Stok <stokcons@xs4all.nl> wrote:
> 
> 
>>>> 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.
>> Just remember that in a truly autonomic network built with factory-reset
>> devices, we cannot assume that anything at all has been configured or
>> named.
>>    Brian
> Yes, but there is a minimum set of services on which you rely: e.g. UDP, DNS, ..
> The discovery alternatives cited by toerless impress me as a list of services of which at least one must be present.

Perhaps an interesting path is like so:

An instantiated anima network MUST support “x”. This allows all devices to know the minimal thing they need to support. 
An instantiated anima network MAY support additional methods such as… “w, y and z”. 

> Therefore my consideration that for something as basic as Service discovery, some industries may regret that they need for example mDNS next to their favoured discovery service e.g. Resource Directory.
> Faced with this choice they may decide that mDNS is not wanted but replaced by RD; and the Anima code in their products is adapted for that choice; while maintaining interoperability with ANIMA routers in all other respects.

So long as there is a fallback that new devices can always use to join the anima network — even if it isn’t the most efficient method. 

- max

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

v2.23.0 | Report a Bug | By Email