[Anima-bootstrap] Brian: GRASP parameter for registrar discovery by proxy

Toerless Eckert <tte@cs.fau.de> Tue, 21 February 2017 15:50 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 423F0129498 for <anima-bootstrap@ietfa.amsl.com>; Tue, 21 Feb 2017 07:50:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
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 IOfoU5FRJIpn for <anima-bootstrap@ietfa.amsl.com>; Tue, 21 Feb 2017 07:50:08 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55D79129507 for <anima-bootstrap@ietf.org>; Tue, 21 Feb 2017 07:50:08 -0800 (PST)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 0379158C4AE; Tue, 21 Feb 2017 16:50:02 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id D24ACB0B7E9; Tue, 21 Feb 2017 16:50:02 +0100 (CET)
Date: Tue, 21 Feb 2017 16:50:02 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20170221155002.GA8168@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-bootstrap/bQsOGE6LdGz9zC5aMN4tEzV2CWg>
Cc: anima-bootstrap <anima-bootstrap@ietf.org>
Subject: [Anima-bootstrap] Brian: GRASP parameter for registrar discovery by proxy
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Feb 2017 15:50:10 -0000

Hi Brian

In the anima bootstrap meeting we tried to figure out the necessary
GRASP message elements for discovery of registrars by proxies. And make
it extensible.

If you check:

http://etherpad.tools.ietf.org:9000/p/anima-boostrapping?useMonospaceFont=true
578 - 608

We may have a bunch of different possible proxy behaviors:

  - TCP circuit proxy in conjunction with HTTPs
  - UDP proxy in conjunction with CoAP
  - IPinIP proxy in conjunction with either HTTPs or CoAP

MichaelR's text was currently suggesting to indicate in the GRASP message
what the registrar supports via the locators:

    locator1  = [O_IPv6_LOCATOR, fe80::1234, 6,  <any,eg:443>]
    locator2  = [O_IPv6_LOCATOR, fe80::1234, 17, <any,eg:5683>]
    locator3  = [O_IPv6_LOCATOR, fe80::1234, 41, nil]

The first line would indicate TCP circuit proxy, the second UDP proxy,
the third one IPinIP proxy.

I am quite uncomfortable to indicate the desired proxy behavior
purely via the IP protocol field in a locator (6, 17, 41). It already
is IMHO underspecified, eg: unclear why the UDP proxy would (only) support
CoAP, and what actually the IPinIP stack supports (CoAP, HTTPs, ...).

So, how/where would we most easily indicate the stack in the GRASP
response ? For example:

    locator1  = [O_IPv6_LOCATOR, fe80::1234, 6,  <any,eg:443>, tcp-circuit]
    locator2  = [O_IPv6_LOCATOR, fe80::1234, 17, <any,eg:5683>, coap-udp]
    locator3  = [O_IPv6_LOCATOR, fe80::1234, 41, nil, tcp-ip-in-ip]
    locator3  = [O_IPv6_LOCATOR, fe80::1234, 41, nil, coap-ip-in-ip]

Thanks!
    Toerless