Re: [Aggsrv] Possible agenda bash

"Paul E. Jones" <paulej@packetizer.com> Mon, 11 March 2013 17:40 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: aggsrv@ietfa.amsl.com
Delivered-To: aggsrv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89DFD11E8115 for <aggsrv@ietfa.amsl.com>; Mon, 11 Mar 2013 10:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.264
X-Spam-Level:
X-Spam-Status: No, score=-1.264 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_HEAD=1.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qI2CmejfwJU for <aggsrv@ietfa.amsl.com>; Mon, 11 Mar 2013 10:40:13 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id C48F711E810E for <aggsrv@ietf.org>; Mon, 11 Mar 2013 10:40:13 -0700 (PDT)
Received: from dhcp-15f5.meeting.ietf.org (dhcp-15f5.meeting.ietf.org [130.129.21.245]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r2BHeCks013462 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 11 Mar 2013 13:40:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1363023613; bh=GoJy0VlhUb7rBPpqQ1l03mLxa+a8SDpF6ek3iKLfQiw=; h=In-Reply-To:References:MIME-Version:Content-Type:Subject:From: Date:To:Message-ID; b=VvZi6a0bp/NdMV3hB4HT5JJkPU6kbZ5l1ILOFyPdhPnhKHWAYpQ4oH5R3Xo0nnwHz FIJ8r7s3phi8tyZeP6miA9Cl+yqZB7s0TPZsEATaGUSA7jxWq25ONWhFgNI8MTyTIS ynkr1Pi7F1BESTfb4Um/BaMTLUo4fSVZDpGfxQ+0=
User-Agent: K-9 Mail for Android
In-Reply-To: <513E153D.1080607@qti.qualcomm.com>
References: <513E153D.1080607@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----QVLKPE607YM38O42JHIXBWZ8I6XUJZ"
From: "Paul E. Jones" <paulej@packetizer.com>
Date: Mon, 11 Mar 2013 13:40:09 -0400
To: Pete Resnick <presnick@qti.qualcomm.com>, aggsrv@ietf.org
Message-ID: <69f1ac25-6d62-4e22-bb3d-aa7ee1ab8772@email.android.com>
Subject: Re: [Aggsrv] Possible agenda bash
X-BeenThere: aggsrv@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Aggregated Service Discovery \(aggsrv\)" <aggsrv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aggsrv>, <mailto:aggsrv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aggsrv>
List-Post: <mailto:aggsrv@ietf.org>
List-Help: <mailto:aggsrv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aggsrv>, <mailto:aggsrv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 17:40:14 -0000

Pete,

Yes, I think it's a valid point. When I read the draft, it reminded me of our dialog on WebFinger. There are clear similarities.

Andrew intends to touch on all of these options in his presentation. I intend to talk about how we could use WF.

Paul


-------- Original Message --------
From: Pete Resnick <presnick@qti.qualcomm.com>
Sent: Mon Mar 11 13:32:45 EDT 2013
To: aggsrv@ietf.org
Subject: [Aggsrv] Possible agenda bash

I should have said more about this earlier:

There was *extensive* discussion during our BOF approval call between 
the IESG and IAB regarding why this BOF was proposing new protocol 
rather than using existing things (examples given -- whatever their real 
applicability -- were DNS-SD and DHCP). There's nothing in the current 
agenda or the presentations that attempt to address this. I think we 
probably need to deal with this directly. Do folks think it is 
reasonable to not only be prepared for these questions (with specific 
attention to why DNS-SD and DHCP are or are not appropriate to this 
problem area) but also to maybe have a slide mentioning it?

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

_______________________________________________
aggsrv mailing list
aggsrv@ietf.org
https://www.ietf.org/mailman/listinfo/aggsrv