Re: [mif] Agenda Time?
Ted Lemon <Ted.Lemon@nominum.com> Mon, 21 March 2016 16:29 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E2AE12D5BF for <firstname.lastname@example.org>; Mon, 21 Mar 2016 09:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([18.104.22.168]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ikSwstESmsj for <email@example.com>; Mon, 21 Mar 2016 09:29:18 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [22.214.171.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BE1C12D91C for <firstname.lastname@example.org>; Mon, 21 Mar 2016 09:29:07 -0700 (PDT)
Received: from webmail.nominum.com (cas-03.win.nominum.com [126.96.36.199]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 25C59740057; Mon, 21 Mar 2016 16:29:07 +0000 (UTC)
Received: from mbx-03.WIN.NOMINUM.COM ([169.254.4.19]) by CAS-03.WIN.NOMINUM.COM ([188.8.131.52]) with mapi id 14.03.0224.002; Mon, 21 Mar 2016 09:29:07 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Margaret Cullen <email@example.com>, "firstname.lastname@example.org" <email@example.com>
Thread-Topic: [mif] Agenda Time?
Date: Mon, 21 Mar 2016 16:29:06 +0000
Content-Type: text/plain; charset="us-ascii"
Cc: Hui Deng <firstname.lastname@example.org>
Subject: Re: [mif] Agenda Time?
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:email@example.com?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:firstname.lastname@example.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2016 16:29:25 -0000
It might be worth having a brief (~10 minute) presentation on the homenet naming architecture document, which has a section on the handling of provisioning domains in the homenet. I'll be submitting the document later on today; I think that what I'm putting in it regarding provisioning domains will work well, but it would be good to get feedback. There's also an interesting interaction between DNSSD and MPvD that I hadn't noticed before: if you want services to be able to publish themselves in the local zone, which MPvD is that? Where do they send the updates? My current answer is that although there are different resolvers per PvD on the homenet, all of the resolvers will accept updates, since all updates are by definition intended for the homenet PvD, and all of the resolvers are operated by the homenet, and hence capable of handling updates for the homenet PvD. We don't want services that do updates to have to be smart about PvDs.