Re: [dispatch] (VIPR) - VAP in or out?
Peter Musgrave <peter.musgrave@magorcorp.com> Tue, 15 June 2010 19:38 UTC
Return-Path: <peter.musgrave@magorcorp.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 81E5B3A6927 for <dispatch@core3.amsl.com>; Tue, 15 Jun 2010 12:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.927
X-Spam-Level:
X-Spam-Status: No, score=-0.927 tagged_above=-999 required=5 tests=[AWL=1.050, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 RlZeDDhoVpS9 for <dispatch@core3.amsl.com>; Tue, 15 Jun 2010 12:38:57 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 978203A68DA for <dispatch@ietf.org>; Tue, 15 Jun 2010 12:38:48 -0700 (PDT)
Received: by qyk8 with SMTP id 8so856679qyk.31 for <dispatch@ietf.org>; Tue, 15 Jun 2010 12:38:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.8.80 with SMTP id g16mr3359420qag.274.1276630727893; Tue, 15 Jun 2010 12:38:47 -0700 (PDT)
Received: by 10.229.217.16 with HTTP; Tue, 15 Jun 2010 12:38:47 -0700 (PDT)
In-Reply-To: <E3FD94DC-61AA-411A-A4EF-5303C1D1DD97@cisco.com>
References: <D92721E4-36AC-4B75-BCDF-E90A9242A286@cisco.com> <4C06A36B.3090103@acm.org> <E3FD94DC-61AA-411A-A4EF-5303C1D1DD97@cisco.com>
Date: Tue, 15 Jun 2010 15:38:47 -0400
Message-ID: <AANLkTinnZjKGNkfh1CR9vdvCf8r58slnmXWne2r72p1k@mail.gmail.com>
From: Peter Musgrave <peter.musgrave@magorcorp.com>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: DISPATCH list <dispatch@ietf.org>
Subject: Re: [dispatch] (VIPR) - VAP in or out?
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: Tue, 15 Jun 2010 19:38:59 -0000
Since the charter is just pointing to these as starting points I vote to include VAP. I see it as a reasonable starting point. Peter Musgrave On Tue, Jun 15, 2010 at 1:23 PM, Cullen Jennings <fluffy@cisco.com> wrote: > > On Jun 2, 2010, at 12:31 PM, Marc Petit-Huguenin wrote: > >>> >>> The problem statement and some possible starting points for solutions are further desired in the following internet drafts which shall form the bases of the WG documents: >>> draft-rosenberg-dispatch-vipr-overview >>> draft-rosenberg-dispatch-vipr-reload-usage >>> draft-rosenberg-dispatch-vipr-pvp >>> draft-rosenberg-dispatch-vipr-sip-antispam >> >> VAP is not listed here. Is it an oversight or is it because the WG will work >> only on interoperability between ViPR servers? > > I could go either way on VAP. On one hand, the minimal thing we need to standardize to have interoperability between domain is just the above stuff without VAP. On the other hand, VAP is a very simple way to modularize what is happening inside a domain. VAP allows information about PSTN call to be given to the server doing the VIPR stuff and allows the VIPR server to tell routing engines and PBX inside the domain about new routes. > > I'd be interested in hearing what other thing. It's easy to add something like VAP to the charter. > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch >
- [dispatch] Charter Proposal: Verification Involvi… Cullen Jennings
- Re: [dispatch] Charter Proposal: Verification Inv… Muthu ArulMozhi Perumal (mperumal)
- Re: [dispatch] Charter Proposal: Verification Inv… Peter Musgrave
- Re: [dispatch] Charter Proposal: Verification Inv… Paul Kyzivat
- Re: [dispatch] Charter Proposal: Verification Inv… Deepanshu Gautam
- Re: [dispatch] Charter Proposal: Verification Inv… Cullen Jennings
- Re: [dispatch] Charter Proposal: Verification Inv… Marc Petit-Huguenin
- Re: [dispatch] Charter Proposal: Verification Inv… Cullen Jennings
- Re: [dispatch] Charter Proposal: Verification Inv… Peter Musgrave
- Re: [dispatch] Charter Proposal: Verification Inv… Jean-Francois Mule
- Re: [dispatch] Charter Proposal: Verification Inv… Jean-Francois Mule
- Re: [dispatch] Charter Proposal: Verification Inv… Peter Musgrave
- Re: [dispatch] Charter Proposal: Verification Inv… Jean-Francois Mule
- Re: [dispatch] Charter Proposal: Verification Inv… Paul Kyzivat
- Re: [dispatch] Charter Proposal: Verification Inv… WORLEY, Dale R (Dale)
- Re: [dispatch] Charter Proposal: Verification Inv… Jean-Francois Mule
- Re: [dispatch] Charter Proposal: Verification Inv… Marc Petit-Huguenin
- [dispatch] VIPR - relation to public ENUM text Cullen Jennings
- [dispatch] (VIPR) - VAP in or out? Cullen Jennings
- Re: [dispatch] Charter Proposal: Verification Inv… Cullen Jennings
- Re: [dispatch] (VIPR) - VAP in or out? Peter Musgrave
- Re: [dispatch] Charter Proposal: Verification Inv… Roni Even
- Re: [dispatch] (VIPR) - VAP in or out? Marc Petit-Huguenin
- Re: [dispatch] Charter Proposal: Verification Inv… Cullen Jennings
- Re: [dispatch] Charter Proposal: Verification Inv… Roni Even
- Re: [dispatch] Charter Proposal: Verification Inv… Mohammad Al-Taraireh (maltarai)
- Re: [dispatch] Charter Proposal: Verification Inv… Cullen Jennings
- Re: [dispatch] Charter Proposal: Verification Inv… Roni Even