IETF Logo Mail Archive

RE: [dispatch] VIPR - proposed charter version 3

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 30 June 2010 10:43 UTC

Return-Path: <dromasca@avaya.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 B569B3A6A90; Wed, 30 Jun 2010 03:43:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.973
X-Spam-Level:
X-Spam-Status: No, score=-1.973 tagged_above=-999 required=5 tests=[AWL=0.626, 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 HU4M7IWFVXQQ; Wed, 30 Jun 2010 03:43:25 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id B98D23A6818; Wed, 30 Jun 2010 03:43:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,511,1272859200"; d="scan'208";a="23043012"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 30 Jun 2010 06:43:35 -0400
X-IronPort-AV: E=Sophos;i="4.53,511,1272859200"; d="scan'208";a="477304417"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 30 Jun 2010 06:42:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dispatch] VIPR - proposed charter version 3
Date: Wed, 30 Jun 2010 12:42:54 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022F40FB@307622ANEX5.global.avaya.com>
In-Reply-To: <AANLkTintQWiM1BNi1Lz11i4AEUm4vnpFhHNRPRMs6ctG@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dispatch] VIPR - proposed charter version 3
Thread-Index: AcsW6MCmpYN4qtxmRxeuIeMgY1MYMwBV08iw
References: <AANLkTintQWiM1BNi1Lz11i4AEUm4vnpFhHNRPRMs6ctG@mail.gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, DISPATCH <dispatch@ietf.org>
Cc: 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 10:43:26 -0000

> 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
>

v2.23.0 | Report a Bug | By Email