Re: [Anima-bootstrap] M_FLOOD and mDNS (was Re: Anima bootstrap: discover protocol multicast notes)

Michael Richardson <> Wed, 15 February 2017 16:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0E9BD126579 for <>; Wed, 15 Feb 2017 08:04:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id T9flireS_OZd for <>; Wed, 15 Feb 2017 08:04:41 -0800 (PST)
Received: from ( [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A59F61294B9 for <>; Wed, 15 Feb 2017 07:59:35 -0800 (PST)
Received: from ( [IPv6:2607:f0b0:f:2::247]) by (Postfix) with ESMTP id 46F46E1D4; Wed, 15 Feb 2017 11:21:04 -0500 (EST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 964506381A; Wed, 15 Feb 2017 10:59:34 -0500 (EST)
From: Michael Richardson <>
In-Reply-To: <>
References: <> <> <> <> <> <>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 15 Feb 2017 10:59:34 -0500
Message-ID: <>
Archived-At: <>
Cc:, Toerless Eckert <>
Subject: Re: [Anima-bootstrap] M_FLOOD and mDNS (was Re: Anima bootstrap: discover protocol multicast notes)
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 15 Feb 2017 16:04:42 -0000

peter van der Stok <> wrote:
    > discovery functions may be used.  I like to point out mDNS due to its
    > long-standing existence.

okay.  I also prefer not to re-invent everything.

    > <pvds> The beginning of section 8 says: " Whenever a Multicast DNS
    > responder starts up, wakes up from sleep, receives an indication of a
    > network interface "Link Change" event, or has any other reason to
    > believe that its network connectivity may have changed in some
    > relevant way, it MUST perform the two startup steps below: Probing
    > (Section 8.1) and Announcing (Section 8.3).  " Much of the text of

Yes, that's the case on the first interval.  Once it's none that, it's not
supposed to be proactively announce itself again, from what I understand.
It's a service, so it doesn't to defend it's name.

    > rfc6762 is about suppressing superfluous traffic.  The method relies
    > on repetitive querying and reactive responding, with a response at
    > responder re-activation (see above).  There is a lot of operational
    > experience here, and deserves attention.  </pvds>

Okay, but would this be a valid implementation:
      unsigned char stuff[]={ 0x01,0x02, /* encoded DNS-SD reply */
      while(true) {
                  sendmsg(stuff, multicast-address, port-5353);


    >> It might be that in the end we don't care about the anonimity of the
    >> pledge.

    > <pvds> Did we? IMO, almost impossible in an unsecured bootstrapping
    > network.  Once keys are distributed, pledge looses it identity and
    > starts afresh (I reckoned) </pvds>

Okay, *DO YOU* care about anonimity of the pledge?
Do *YOU* care if the pledge must solicit a Join Proxy by multicasting a query?

    >> If the pledge can ask the network about Join Proxy, then there is
    >> nothing to stop us from using mDNS here.

    > <pvds> Or anything else dependent on the operational environment of
    > the SDO using the bootstrapping protocol.  </pvds>

What would you like to chose here?  Tell us your opinion.
Don't be shy.

Michael Richardson <>, Sandelman Software Works
 -= IPv6 IoT consulting =-