Re: [dispatch] VIPR - proposed charter version 3

Mary Barnes <mary.ietf.barnes@gmail.com> Wed, 30 June 2010 16:21 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 B666A28C0D0; Wed, 30 Jun 2010 09:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.339
X-Spam-Level:
X-Spam-Status: No, score=-2.339 tagged_above=-999 required=5 tests=[AWL=0.260, 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 BUWhQF02jeyy; Wed, 30 Jun 2010 09:21:12 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id E23E428B56A; Wed, 30 Jun 2010 09:21:11 -0700 (PDT)
Received: by iwn40 with SMTP id 40so1064328iwn.31 for <multiple recipients>; Wed, 30 Jun 2010 09:21:23 -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 :content-transfer-encoding; bh=Uq/AINrPGcCuNZ5pxBOIcmyL4EbWcMX2L+1ORRfR2jE=; b=Zz9zyVIAAkPy6iEsDy8P9p9aeS4QhlwGcCbOuCAtI4riNeyCytgiqZTAxW3FcIICKb KtC9ZlqqOAQfUVac0HN7pGzo7xoh2IBpwgh5O2qD+ui84gs7+giEsWYaUZnmuIxFvacQ SBvfnB2OiUY4xqXqym50ZD3EK6tkkE9hf3RvA=
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:content-transfer-encoding; b=npehEpwZGAjcXayUJ3WSa/XxA6RXyHTrZ575DSP9B7ItIdMpl53G96MLolj2Tp7Yr9 J6Vlz3tsztTrkfMlPPtHQw1hD6X38iDUQjbMgY3D+1rWWi71OgZ9xUvUnjWOQ+GnTUQU fIvsP55ZCh2goo0wYiY3lVMbpPRFYljGfVVNs=
MIME-Version: 1.0
Received: by 10.231.120.159 with SMTP id d31mr9120949ibr.89.1277914882842; Wed, 30 Jun 2010 09:21:22 -0700 (PDT)
Received: by 10.231.146.206 with HTTP; Wed, 30 Jun 2010 09:21:22 -0700 (PDT)
In-Reply-To: <4c2b6afd.0bf4720a.7381.6c0d@mx.google.com>
References: <AANLkTintQWiM1BNi1Lz11i4AEUm4vnpFhHNRPRMs6ctG@mail.gmail.com> <EDC652A26FB23C4EB6384A4584434A04022F40FB@307622ANEX5.global.avaya.com> <AANLkTinCs4ooaP7qczjOf_CMJB2tZg9XR9Ro5H-WWHK6@mail.gmail.com> <4c2b6afd.0bf4720a.7381.6c0d@mx.google.com>
Date: Wed, 30 Jun 2010 11:21:22 -0500
Message-ID: <AANLkTimwfRjbw8GEWpibHcpDCj9moSOpF2NPp7NCy2MH@mail.gmail.com>
Subject: Re: [dispatch] VIPR - proposed charter version 3
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 01 Jul 2010 11:45:46 -0700
Cc: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, 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 16:21:14 -0000

Hi Roni,

Comments inline below and some snipping of the thread.

Thanks,
Mary.

On Wed, Jun 30, 2010 at 11:03 AM, Roni Even <ron.even.tlv@gmail.com> wrote:
> Mary,
> When I read the charter it is not clear why from the first paragraph you
> deduct the second paragraph.
> If the first paragraph will say
> " The goal of this working group is to enable inter-domain communications
> over the Internet, using protocols such as SIP, while still allowing people
> to use the called person assigned circuit switch phone number for
> identifying the person with whom they wish to communicate. "
> It may look clearer.
[MB] We could change "phone number" to "called person assigned circuit switch
phone number for identifying the person", but I think that "phone
number" is well
understood to be exactly what you want to describe it as.  [/MB]

>
> Still this is based on the assumption that using other ways to assign and
> authenticate SIP phone numbers using central databases is not catching up
> because the carriers object to implement it and not due to any other reason
> like preferences of enterprises IT to use PSTN for calls because of better
> quality of service and manageability.
[MB] I'm not certain (personally) that the latter preferences you note
are as prevalent as you might suggest. I would still contend that the
larger issue is the former. However, if other folks share this
concern, we can certainly add that as well - it reflects equally as
being a non-technical reason for widespread implementation [/MB]
>
> Roni Even
>
>> -----Original Message-----
>> From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On
>> Behalf Of Mary Barnes
>> Sent: Wednesday, June 30, 2010 6:24 PM
>> To: Romascanu, Dan (Dan)
>> Cc: DISPATCH; IETF-Discussion list
>> Subject: Re: [dispatch] VIPR - proposed charter version 3
>>
>> 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
>> >>
>> >
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>
>