
From jon.peterson@neustar.biz  Wed Nov  2 11:00:03 2011
Return-Path: <jon.peterson@neustar.biz>
X-Original-To: vipr@ietfa.amsl.com
Delivered-To: vipr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1833A1F0C4B for <vipr@ietfa.amsl.com>; Wed,  2 Nov 2011 11:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.098
X-Spam-Level: 
X-Spam-Status: No, score=-106.098 tagged_above=-999 required=5 tests=[AWL=0.501, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYefhiv5uB0D for <vipr@ietfa.amsl.com>; Wed,  2 Nov 2011 11:00:02 -0700 (PDT)
Received: from neustar.com (smartmail.neustar.com [156.154.17.104]) by ietfa.amsl.com (Postfix) with ESMTP id 3B43D1F0C35 for <vipr@ietf.org>; Wed,  2 Nov 2011 11:00:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neustar.biz; s=neustarbiz; t=1320256883; x=1635610762; q=dns/txt; h=From:Date:Subject:Message-ID:Content-Language: Content-Type:Content-Transfer-Encoding; bh=JbNmlqzKmf2UT17+BTDFQ yfg3ypwQ0PSzXDJobFSdRI=; b=eFhuSpcQyacIt/fG5czqootwq3eJPRqgngm/V IpuZixj9Vu3drg/K9KY6zbqudYsciPrcL5I0Pcj9tbi+ZRhVw==
Received: from ([10.31.13.229]) by stihiron1.va.neustar.com with ESMTP with TLS id J041124052.1805464;  Wed, 02 Nov 2011 14:01:22 -0400
Received: from STNTEXCH01.cis.neustar.com ([fe80::31b6:4d09:2ada:e6c0]) by STNTEXCHHT02.cis.neustar.com ([::1]) with mapi; Wed, 2 Nov 2011 13:59:59 -0400
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "vipr@ietf.org" <vipr@ietf.org>
Date: Wed, 2 Nov 2011 13:59:53 -0400
Thread-Topic: vipr draft agenda for taipei
Thread-Index: AcyZiTxLm0AlJnL5Rh2zx/+9hkK5AA==
Message-ID: <7E05C9F3-C396-4F45-8806-FDCF7BE2E9E2@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-ems-proccessed: R64IxjzeHPwwd+efoj3ZcA==
x-ems-stamp: jLzJbSm3sMfmCvRZZH64VQ==
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [VIPR] vipr draft agenda for taipei
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 18:00:03 -0000

Here's the current thinking for a Taipei agenda - please let us chairs know=
 ASAP if you'd like to do anything different (as usual, we're right up agai=
nst the deadline). The huge block of time we've given to Marc without much =
differentiation reflects that we'll narrow those topics down after the desi=
gn team call this Friday.

Jon Peterson
NeuStar, Inc.
-----

VIPR WG -- IETF 82, Taipei, Taiwan
Thursday, November 17, 17:40-19:40

Mailing list: vipr@ietf.org
Status page: https://tools.ietf.org/wg/vipr/

Chairs: Daryl Malas <Daryl Malas <D.Malas@cablelabs.com>
        Jon Peterson <jon.peterson@neustar.biz>
Agenda:
17:40 - Administrivia (Note Well, Blue Sheets) [Chairs]
17:45 - Status Update, -overview draft adoption? [Chairs]
17:50 - Open Issues in -reload-usage, -pvp, and -antispam etc (details to f=
ollow) [Petit-Huguenin]
19:30 - Other issues, open mic


From petithug@acm.org  Wed Nov  2 16:49:58 2011
Return-Path: <petithug@acm.org>
X-Original-To: vipr@ietfa.amsl.com
Delivered-To: vipr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBE2311E8094 for <vipr@ietfa.amsl.com>; Wed,  2 Nov 2011 16:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IkNCY0AJKj7S for <vipr@ietfa.amsl.com>; Wed,  2 Nov 2011 16:49:57 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 6A17811E8073 for <vipr@ietf.org>; Wed,  2 Nov 2011 16:49:57 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "petithug", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 390B520885 for <vipr@ietf.org>; Wed,  2 Nov 2011 23:41:03 +0000 (UTC)
Message-ID: <4EB1D720.3040704@acm.org>
Date: Wed, 02 Nov 2011 16:49:52 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20111010 Iceowl/1.0b2 Icedove/3.1.15
MIME-Version: 1.0
To: "vipr@ietf.org" <vipr@ietf.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [VIPR] Minutes for 2011/10/28 conference call
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 23:49:58 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

VIPR Design Team conference call on Friday October 28th, from 9:05am to 9:55am PST.

o Attendees:
  Mary Barnes
  Daryl Malas
  Jon Peterson
  Marc Petit-Huguenin
  Michael Procter

o Regrets:
  Hakim Mehmood
  Muthu Arul Mozhi Perumal
  John Ward
  Dean Willis

o Agenda

- - Replacement ticket by client certificate (10 min)
- - PVP privacy (10 min)
- - PVP method entropy (10 min)
- - Ticket renewal (10 min)
- - Infrastructure overlays (10 min)
- - VIPR troubleshooting (10 min)

o Action items

- - Remove method "a" and design method "c" that will hash the Caller-ID.
- - Incorporate some text about ticket renewal.
- - Add more text on ICE, TLS (but no profile).

o Minutes

- - Agenda

Marc: I propose to have one more conference call next week, then to restart the
work on November 28th, after the IETF meeting.

Daryl: No objection.

- - Replacement ticket by client certificate

Marc: The discussion stalled on the certificate vs ticket discussion in the
mailing-list, mostly my fault.

Jon: It's a major change, so we should have a requirement process.  Second
running a CA is really complicated, and requiring all this system to constantly
acting as CA is not optimum.  Created certificates like this really is overkill.
My 3rd point is that binding this with TLS does not seem to fit with SIP.  I
think that putting the signature is an header is a better idea, but there is
thousand of other solutions and this seems disproportionate.

Marc: You have a point that using the ticket as certificate for TLS is a
problem, as it permit people to sell their tickets.  As for the discussion about
CA, the proposal is just to use X.509 as a container for everything that is
already in the ticket.  It's just a format change, and the only difference is
for the developer, where libraries are available for X.509, but not for the
Ticket.  This is not different from what RELOAD is doing.

Jon: [audio garbled]

Marc: Yes in RELOAD you send a key, it send back a certificate, it would be the
same thing.

[audio lost]

- - PVP privacy

[audio lost]

Michael: [...] the data will be significant for someone, so whether it's 48
hours or 2 years, that will be wrong for someone.

Jon: We can design methods to increase the duration.  We just need an argument
that people won't laugh at.  Definitively it can't be two years.

Marc:  What I mean is that it will take 2 years to crack the hash.

Jon: Yes.  We need to say something that we can put defensively in the draft.

Marc: So do we want to keep method "a" as it is and define a method "c" that is
hashing the Caller-ID, or replacing method "a' by hashing the Caller-ID, or do
we want to do sometime else?  My preference is for the first one.

Michael: OK

Mary: OK for method "c".

Jon:  Let's get rid of method "a" and make method "c".

- - PVP method entropy

Marc: We were stuck on the method entropy in the last meeting, so I sent the 3
solutions in the mailing-list.  #1 is we do not care about entropy, #2 we care
but it's done purely on the server side, #3 we care about entropy but the
storage is done in the client side.

Michael: Instead of a cookie, can it be stored in the Ticket?

Marc: This was the plan, and you need this, to authenticate the entropy. The
idea is to add a field that contains the entropy accumulated, and you resent
your ticket for the next PVP transaction.  The server validates, adds entropy
and resends a new ticket.  We need protection against someone using twice the
same call to accumulate entropy.  The easiest way for us is to do everything in
the server, because we do not need text for that.  Or we can make things easier
for deployment, which is to do this on the client side.

Jon: I want to get sufficient entropy, but I am not sure how much we get with
PSTN calls.

Marc:  Yes, that's the first choice, one call, one route.

- - Ticket renewal

Marc: We discussed that in Quebec City, but without conclusion, and I made a
proposal later. The idea is that it is acceptable to have a first call on the
PSTN, but it is not acceptable to have periodical PSTN calls after this to renew
the ticket. My proposal uses a draft which is in last call, and which is named
- -sdp-cs.  This permits to trigger a PSTN call based on an INVITE.  So just
before the expiration of the ticket, one of the call is selected to use PSTN and
Internet in parallel.  The PSTN call is used to trigger a validation.  The
advantage is that you do not switch back to PSTN.  The problem is that you need
to have access to the media, so SIP intermediaries could not use that.

Michael: On this approach, you run the audio on the PSTN?

Marc:  You need to run the audio on both the PSTN and Internet because if we
invent a new validation method in the future, like fingerprint, we need to
recognize it on the PSTN.  And we still need audio on the Internet side, because
of wideband audio.

Michael: Do we use the normal process, or is it more realtime?

Marc: It is possible to use a method based on call duration, and the calling
side can just use a random duration for the call.  If for example the method is
based on fingerprint, the call can hangup immediately.  And this can provide us
a path to a quicker validation.

Jon: This is probably on the right track.

Marc: I will try to incorporate something like this in the document.

- - Infrastructure overlays

Marc: We have to start thinking how VIPR will be deployed. And for VIPR to work,
we absolutely need to have only one overlay.  So the question is how to achieve
this goal.  So I submitted a draft to DISPATCH about Infrastructure Overlays.
This draft contains only requirements.

Michael: On the subject of having one overlay all around the planet, how does
that square with previous discussions where we said that VIPR is not intended to
be used by service providers or international grannies?  We seems to try to make
one universal thing that is not quite universal.

Marc: I do not agree that this thing is not for everybody.

Jon: The IETF is not in the business of mandating this, it is in the business of
mandating what needs to be implemented in order to make interoperability work.
The discussion we had about VIPR not been for service providers has been about
the fact that VIPR is different from ENUM or SPEERMINT is.  The discussion about
this been for theses people is separate from the administrative problem of
having one overlay.  If there is islands of VIPR, then we made a mistake.

Marc: There is some precedents to this in the IETF, like the DNS, ENUM and all
the arpa stuff.  So if someone want to participate in VIPR, how are we sure that
they are all in the same overlay?  Another related problem is that because VIPR
is automatic, you do not have the possibility to do a interop test between VIPR
domains.  So we need to have a profile to make the calls.

Jon: I would hesitate to say that we need a SIP profile.  SIP has negotiation
mechanism and VIPR should not constraint what VIPR should do.  VIPR permits to
do things that cannot be done today, but it should not require to do those
things.  Do you mean that we should profile codecs, or you should not do VIPR if
you do not support Opus?

Marc: Do we want to let people use G.711 after receiving a VIPR route?

Jon: That would be pointless,  But I see profile as a narrow list of things that
need to be supported, There is a bunch of wideband codecs, or video codecs and
other things that we should not have in the future.  We can say that wideband
should be supported, or what the options are, but mandating would be a mistake.

Marc: I agree, but if you say that you need to support wideband, you still need
a baseline.  Do we want to have a SIP call failing after receiving a route?

Jon: But, for example, having presence alone would be worth it, so I would
really hesitate that we would mandate something.

Daryl: I agree with that.

Michael: I agree also.  But we should specify things like TLS or ICE support and
providing more guidelines to improve the probability of successful calls.

Mary: I agree too.

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk6x1x8ACgkQ9RoMZyVa61fFKwCgja8ClzlLVwcr7nhGtHytAD4N
FiMAn1mAOHbVRq22o8B4Be1kBkAITQ0V
=wz++
-----END PGP SIGNATURE-----

From petithug@acm.org  Thu Nov  3 07:52:33 2011
Return-Path: <petithug@acm.org>
X-Original-To: vipr@ietfa.amsl.com
Delivered-To: vipr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1EE11E80D2 for <vipr@ietfa.amsl.com>; Thu,  3 Nov 2011 07:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.575
X-Spam-Level: 
X-Spam-Status: No, score=-103.575 tagged_above=-999 required=5 tests=[AWL=1.025, BAYES_00=-2.599, GB_I_INVITATION=-2, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFTycMwJPI46 for <vipr@ietfa.amsl.com>; Thu,  3 Nov 2011 07:52:32 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id D59AB11E80B4 for <vipr@ietf.org>; Thu,  3 Nov 2011 07:52:31 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "petithug", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id CBD6020892; Thu,  3 Nov 2011 14:43:33 +0000 (UTC)
Message-ID: <4EB2AAAA.3010202@acm.org>
Date: Thu, 03 Nov 2011 07:52:26 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20111010 Iceowl/1.0b2 Icedove/3.1.15
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>,  "Hakim Mehmood (naim)" <naim@cisco.com>, Michael Procter <michael@voip.co.uk>, John Ward <jward@IntelePeer.com>,  'Mary Barnes' <mary.ietf.barnes@gmail.com>, "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>,  Daryl Malas <D.Malas@cablelabs.com>, Jon Peterson <jon.peterson@neustar.biz>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "vipr@ietf.org" <vipr@ietf.org>
Subject: [VIPR] Agenda & Handout for 2011/11/04
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 14:52:33 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A. Agenda

- - Drafts update
- - Replacement ticket by client certificate
- - PVP Entropy
- - VIPR troubleshooting
- - ICE support in VIPR

Note that the topics that cannot make it to the discussion will be postponed to
the IETF meeting if they are not subsequently decided in the mailing-list.

Because the conference bridge as a limited capacity, an individual invitation to
the conference will be sent shortly after this email to each member of the
design team.  Please send me an email if you are not on this list and want to
receive an invitation.

Note that the design team conference call is not a way to short-circuit the
normal process, but a way to accelerate it by increasing face to face time.  All
decisions made must be confirmed on the mailing-list.

This conference call is subject to the rules of RFC 5378 and RFC 3979 (updated
by RFC 4879).


B. Handout (reading time: 10 min)

B.1. Drafts update

The -overview draft is still waiting for some text in the security section.
The -privacy-concerns draft was not updated.
The -proportional-quota draft was moved back to the VIPR WG, but is still
missing the equation for the probability.
The -reload-usage draft was updated as discussed (removed storage 3 times, and
added methods in registration).
The -pvp draft was updated (method "a" use hashed Caller-ID, perhaps should have
been new draft).
The -sip-antispam was not updated (needs ticket renewal, more text on ICE, etc..)
The -overview draft is empty so far (needs at least method registration template)
The -sip-intermediaries was not updated.
The -infrastructure-overlays draft was not updated.

New draft: Inverting secret/selector?

B.2 Replacement ticket by client certificate

The discussion is still stuck on using X.509 certificate as a container for the
Ticket data.

B.3. PVP Entropy

The discussion at the end of the previous conference call stalled on what to do
about entropy.  There is 3 possibilities:

1. We do not need to manage entropy because we do not want to have the user
making multiple PSTN calls before receiving a SIP route.
2. We need to manage entropy, but it is best managed completely in the PVP server.
3. We need to manage entropy, but it is best managed in both client and server
by using something like a cookie.

B.4. VIPR troubleshooting

One very important point made in draft-jennings-vipr-overview is the
troubleshooting problem (section 2.4).  Because the provisioning of SIP routes
is automatic, there is no possibility to have a interop testing between two
domains before the establishment of the fist call.  This means that we need to
provide help for debugging problems if things go wrong.

The main issue is that it is not always possible to troubleshoot a problem only
by looking on the logs and traces on the sending side - some kind of cooperation
is required by the receiving side.  Having a way to retrieve the logs and traces
automatically would be a good step in this direction, but we now have a security
problem to take care of, as we certainly do not want anybody to be able to
retrieve this information.

B.5. ICE support in VIPR

Section 1.2.1 of draft-procter-vipr-privacy-concerns proposes to use TURN to
anonymise the source of a PVP validation.  This proposal is probably incomplete,
but the main problem is that we still do not know what transports will be used
on the RELOAD overlay used by VIPR.  First here's a list of what we currently
know about this overlay:

- - The algorithm is RELOAD-CHORD
- - The Node-ID size is 16 bytes (128 bits).
- - Clients are not authorized because of the quota algorithm.
- - Self-signed certificates are not authorized.
- - There will be one or more root-certs.
- - There will be one or more bootstrap peers (unicast or anycast - no multicast).
- - Clients are not authorized because of the quota algorithm.
- - Shared secret are not used.
- - The overlay link protocol is TLS.
- - There will be a list of kind and configuration signers.
- - The urn:ietf:params:xml:ns:p2p:config-chord, urn:ietf:params:xml:ns:p2p:quota
and urn:ietf:params:xml:ns:p2p:vipr extensions are mandatory.
- - The Kind VIPR-REGISTRATION will be authorized.

What we do not know yet:

- - Do we need to authorize the CERTIFICATE-BY-NODE and CERTIFICATE-BY-USER Kinds?
- - Will TURN server deployed in the overlay?
- - Will ICE overlay link protocols be used?

The important question for this topic is the support of ICE in the RELOAD overlay:

Pros:  With ICE support the RELOAD nodes, the PVP client and the PVP server can
be installed behind a NAT/Firewall without having to put them on the DMZ or to
open pinholes (the bootstrap servers will still need to be installed in the DMZ
or on the Internet).  TURN servers are required for ICE support, so they would
also be available for anonymising the connections.

Cons:  ICE is complex to implement and debug.

If we decide to exclude ICE, then the TURN servers are no longer available by
default, and the idea of using them for anonymising the connections is moot.

An additional consideration is that the RELOAD transports are currently limited
to UDP and TCP, neither of them being really well suited to carry RELOAD or PVP
messages.  If we decide to exclude ICE support, I will then propose to use
(D)TLS over SCTP instead (and write the I-D for this).

So the initial question is:  Do we need ICE or not?

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk6yqqUACgkQ9RoMZyVa61eOnQCfQlUrSGJiooaF06q/vdluqLP5
6wYAnjj9GqlT+RLmXcdqLCK4OMR7fMbb
=8IC4
-----END PGP SIGNATURE-----

From petithug@acm.org  Sat Nov  5 06:42:54 2011
Return-Path: <petithug@acm.org>
X-Original-To: vipr@ietfa.amsl.com
Delivered-To: vipr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77C1C21F85DB for <vipr@ietfa.amsl.com>; Sat,  5 Nov 2011 06:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.694
X-Spam-Level: 
X-Spam-Status: No, score=-102.694 tagged_above=-999 required=5 tests=[AWL=-0.094, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b4nMLtsKeBdP for <vipr@ietfa.amsl.com>; Sat,  5 Nov 2011 06:42:53 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id BA1C121F8495 for <vipr@ietf.org>; Sat,  5 Nov 2011 06:42:50 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "petithug", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 9F942200D1 for <vipr@ietf.org>; Sat,  5 Nov 2011 13:33:46 +0000 (UTC)
Message-ID: <4EB53D55.8030903@acm.org>
Date: Sat, 05 Nov 2011 06:42:45 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20111010 Iceowl/1.0b2 Icedove/3.1.15
MIME-Version: 1.0
To: "vipr@ietf.org" <vipr@ietf.org>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [VIPR] Minutes for 2011/11/04 conference call
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Nov 2011 13:42:54 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

VIPR Design Team conference call on Friday November 4th, from 9:05am to 9:15am PST.

o Attendees:
  Daryl Malas
  Hakim Mehmood
  Marc Petit-Huguenin
  Dean Willis

o Regrets:
  Mary Barnes
  Muthu Arul Mozhi Perumal
  Jon Peterson
  Michael Procter
  John Ward

o Agenda

- - Drafts update
- - Replacement ticket by client certificate
- - PVP Entropy
- - VIPR troubleshooting
- - ICE support in VIPR

o Action items

- - New version of the drafts.
- - RPS for VIPR meeting in Taipei.

o Minutes

Because there was not enough people in the call, we decided to cancel this
conference call.  A new version of some of the drafts will be released on Monday
15th, and all the pending topics will be presented during the VIPR meeting in
Taipei.  Daryl will make a request to have Remote Participant Support for this
meeting.  Depending on the work done in Taipei, the conference calls will resume
beginning of December, on a better conference bridge.

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk61PVMACgkQ9RoMZyVa61eJHACfbYkH6LclAIDcxGOXl7cNpB4U
dxwAn1JKh1k8koecZbce0sagKu34WmUl
=ik8z
-----END PGP SIGNATURE-----

From ietf@meetecho.com  Wed Nov 16 09:13:25 2011
Return-Path: <ietf@meetecho.com>
X-Original-To: vipr@ietfa.amsl.com
Delivered-To: vipr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3404321F94B9 for <vipr@ietfa.amsl.com>; Wed, 16 Nov 2011 09:13:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZoGJDPd0+zaG for <vipr@ietfa.amsl.com>; Wed, 16 Nov 2011 09:13:24 -0800 (PST)
Received: from smtplq04.aruba.it (smtplq-out19.aruba.it [62.149.158.39]) by ietfa.amsl.com (Postfix) with SMTP id 1D74221F94B1 for <vipr@ietf.org>; Wed, 16 Nov 2011 09:13:23 -0800 (PST)
Received: (qmail 6579 invoked by uid 89); 16 Nov 2011 17:13:19 -0000
Received: from unknown (HELO smtp5.aruba.it) (62.149.158.225) by smtplq04.aruba.it with SMTP; 16 Nov 2011 17:13:19 -0000
Received: (qmail 7738 invoked by uid 89); 16 Nov 2011 17:13:19 -0000
Received: from unknown (HELO ?192.168.15.117?) (ietf@meetecho.com@114.24.8.77) by smtp5.ad.aruba.it with SMTP; 16 Nov 2011 17:13:19 -0000
Message-ID: <4EC3EF27.2030809@meetecho.com>
Date: Wed, 16 Nov 2011 18:13:11 +0100
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: vipr@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtp5.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq04.aruba.it 1.6.2 0/1000/N
Subject: [VIPR] Meetecho support for VIPR WG meeting session
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2011 17:13:25 -0000

Hi all,

a virtual room has been reserved on the Meetecho system for Thursday's 
VIPR WG meeting session.

Access to the on-line session (including audio and video streams) will 
be available from 5:40pm at:
http://www.meetecho.com/ietf82/vipr

The Meetecho session automatically logs you into the standard IETF 
jabber room. So, from there, you can have an integrated experience 
involving all media and allowing you to interact with the room.

A tutorial of interactivity features of the tool can be found at:
http://www.meetecho.com/ietf82/tutorials

For further information you can contact us at ietf-support@meetecho.com.

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

From ietf@meetecho.com  Tue Nov 22 02:11:27 2011
Return-Path: <ietf@meetecho.com>
X-Original-To: vipr@ietfa.amsl.com
Delivered-To: vipr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B918F21F8D8A for <vipr@ietfa.amsl.com>; Tue, 22 Nov 2011 02:11:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.435
X-Spam-Level: 
X-Spam-Status: No, score=-0.435 tagged_above=-999 required=5 tests=[AWL=0.284,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id owvD911-Zopj for <vipr@ietfa.amsl.com>; Tue, 22 Nov 2011 02:11:24 -0800 (PST)
Received: from smtplq02.aruba.it (smtplq-out17.aruba.it [62.149.158.37]) by ietfa.amsl.com (Postfix) with SMTP id 6F25621F8B3E for <vipr@ietf.org>; Tue, 22 Nov 2011 02:11:23 -0800 (PST)
Received: (qmail 13021 invoked by uid 89); 22 Nov 2011 10:11:22 -0000
Received: from unknown (HELO smtp3.aruba.it) (62.149.158.223) by smtplq02.aruba.it with SMTP; 22 Nov 2011 10:11:22 -0000
Received: (qmail 31460 invoked by uid 89); 22 Nov 2011 10:11:18 -0000
Received: from unknown (HELO ?143.225.229.189?) (ietf@meetecho.com@143.225.229.189) by smtp3.ad.aruba.it with SMTP; 22 Nov 2011 10:11:18 -0000
Message-ID: <4ECB7535.40901@meetecho.com>
Date: Tue, 22 Nov 2011 11:11:01 +0100
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: vipr@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtp3.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq02.aruba.it 1.6.2 0/1000/N
Subject: [VIPR] VIPR session recording available
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2011 10:11:27 -0000

Dear all,

the full recording (synchronized video, audio, slides and jabber room)
of VIPR session at IETF-82 is available.

You can watch it by either clicking the proper link on the remote 
participation page 
(http://www.ietf.org/meeting/82/remote-participation.html#Meetecho), or 
by directly accessing the following URL:
http://www.meetecho.com/ietf82/recordings#VIPR

For the chair(s): please feel free to put the link to the recording in 
the minutes, if you think this might be useful.

In case of problems with the playout, just drop an e-mail to
ietf-support@meetecho.com.

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com
