Re: [dispatch] VIPR - proposed charter version 3

Mary Barnes <mary.ietf.barnes@gmail.com> Wed, 30 June 2010 15:23 UTC

Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EBC83A684A; Wed, 30 Jun 2010 08:23:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level:
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UzdYQJmC947n; Wed, 30 Jun 2010 08:23:57 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 98EF23A6A3B; Wed, 30 Jun 2010 08:23:54 -0700 (PDT)
Received: by gyh3 with SMTP id 3so515714gyh.31 for <multiple recipients>; Wed, 30 Jun 2010 08:24:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=0dzUnI6Grc07SuxGRSrHXCrZseTsfsVYcy/rMjYS6Vc=; b=mcf84Y+Sg+hTwmkt7OZe3IZmAya+YIfeReTbfcL2ukf9VsLmTkUZ5tu778XGcdtNNN YbhwinUCsAvrYaVoEg9svSChgr5h/vl6poSQho4mb9jSxQgnsAyMknZm5Hr3lPATPa+7 lTsiUU2USMp3tuLG4As4o75my/33y2IW9hz0s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kccaWG8771zs92CRgHbaNQiszfpHUCR6w7LV9jOLlz7xad+KszHR3I7BbasPAzjEs9 wTxejFK7xV9dISYUupHzHreOUmodsG1FZCcL+XFlrj4cMobBUVdPnJbTozDhiXNX7mGN NmHyZnSRI+tW3jJDMi4dIPJlWddT7FqeZvpuA=
MIME-Version: 1.0
Received: by 10.102.226.11 with SMTP id y11mr3154865mug.54.1277911441796; Wed, 30 Jun 2010 08:24:01 -0700 (PDT)
Received: by 10.231.146.206 with HTTP; Wed, 30 Jun 2010 08:24:01 -0700 (PDT)
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04022F40FB@307622ANEX5.global.avaya.com>
References: <AANLkTintQWiM1BNi1Lz11i4AEUm4vnpFhHNRPRMs6ctG@mail.gmail.com> <EDC652A26FB23C4EB6384A4584434A04022F40FB@307622ANEX5.global.avaya.com>
Date: Wed, 30 Jun 2010 10:24:01 -0500
Message-ID: <AANLkTinCs4ooaP7qczjOf_CMJB2tZg9XR9Ro5H-WWHK6@mail.gmail.com>
Subject: Re: [dispatch] VIPR - proposed charter version 3
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailman-Approved-At: Thu, 01 Jul 2010 11:45:46 -0700
Cc: DISPATCH <dispatch@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2010 15:23:58 -0000

Hi Dan,

The term peer to peer is intended to exclude mechanisms that would use
a central repository for the information:  This was discussed in an
earlier thread:
http://www.ietf.org/mail-archive/web/dispatch/current/msg02027.html

In one sense it is a solution, however, in another sense it is reusing
SIP related functionality defined in RAI and thus is in a similar vein
as specifying the use of SIP in a charter.

Thanks,
Mary.

On Wed, Jun 30, 2010 at 5:42 AM, Romascanu, Dan (Dan)
<dromasca@avaya.com> wrote:
>> The VIPR WG will address this problem by developing a peer to
>> peer based approach to finding domains that claim to be
>> responsible for a given phone number and validation protocols
>> to ensure a reasonable likelihood that a given domain
>> actually is responsible for the phone number.
>
> Hi,
>
> Clarification question. What exactly means 'peer to peer based approach'
> and what kind of approaches are excluded by having this in the charter.
> Does 'approach' mean solution? If so why does a specific type of
> solution need to be agreed in the charter, while all we have at hand at
> this point are individual contribution I-Ds that describe the 'problem
> statement and some possible starting points for solutions'?
>
> Thanks and Regards,
>
> Dan
>
>
>> -----Original Message-----
>> From: dispatch-bounces@ietf.org
>> [mailto:dispatch-bounces@ietf.org] On Behalf Of Mary Barnes
>> Sent: Monday, June 28, 2010 8:38 PM
>> To: DISPATCH
>> Subject: [dispatch] VIPR - proposed charter version 3
>>
>