IETF Logo Mail Archive

Re: [dispatch] VIPR - proposed charter version 2

"WORLEY, Dale R (Dale)" <dworley@avaya.com> Thu, 17 June 2010 19:01 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D02343A6B06 for <dispatch@core3.amsl.com>; Thu, 17 Jun 2010 12:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.222
X-Spam-Level:
X-Spam-Status: No, score=-1.222 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_05=-1.11]
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 fSTgYu+itVj5 for <dispatch@core3.amsl.com>; Thu, 17 Jun 2010 12:01:20 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 4BACA3A6887 for <dispatch@ietf.org>; Thu, 17 Jun 2010 12:01:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,433,1272859200"; d="scan'208";a="193988280"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 17 Jun 2010 15:01:14 -0400
X-IronPort-AV: E=Sophos;i="4.53,433,1272859200"; d="scan'208";a="484329945"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Jun 2010 15:01:14 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.188]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 17 Jun 2010 15:01:13 -0400
From: "WORLEY, Dale R (Dale)" <dworley@avaya.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, Cullen Jennings <fluffy@cisco.com>, DISPATCH list <dispatch@ietf.org>
Date: Thu, 17 Jun 2010 14:59:02 -0400
Thread-Topic: [dispatch] VIPR - proposed charter version 2
Thread-Index: AcsMr60GvMAAZLBqTHKl5gwUKZoQPQBicrhQAAVrmQw=
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FD7361AD@DC-US1MBEX4.global.avaya.com>
References: <DB6CA94F-0EC9-4E27-A190-D12029CA61AE@cisco.com>, <A444A0F8084434499206E78C106220CAE6057737@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CAE6057737@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dispatch] VIPR - proposed charter version 2
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2010 19:01:20 -0000

________________________________________
From: dispatch-bounces@ietf.org [dispatch-bounces@ietf.org] On Behalf Of Elwell, John [john.elwell@siemens-enterprise.com]

Does it necessarily have to be a peer-to-peer based approach?
_______________________________________________

I'd say the essence of VIPR is that it's peer-to-peer.  Or rather, that it enables the originator to succeed without the existence of a central or reliable database.  (A peer-to-peer structure is used as a way for terminators to advertise their claimed addresses.)  If we want to develop a database-centered approach, it would be disjoint from the design effort for VIPR.

Dale

v2.23.0 | Report a Bug | By Email