Re: [ppsp] #17: How to formulate behaviour of Peer-Exchange messages?

"ppsp issue tracker" <trac+ppsp@trac.tools.ietf.org> Wed, 20 June 2012 07:27 UTC

Return-Path: <trac+ppsp@trac.tools.ietf.org>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A11621F8707 for <ppsp@ietfa.amsl.com>; Wed, 20 Jun 2012 00:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 FmoZ-PNDswwc for <ppsp@ietfa.amsl.com>; Wed, 20 Jun 2012 00:27:59 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 022C721F8705 for <ppsp@ietf.org>; Wed, 20 Jun 2012 00:27:59 -0700 (PDT)
Received: from localhost ([127.0.0.1]:54768 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+ppsp@trac.tools.ietf.org>) id 1ShFKW-0001yN-P3; Wed, 20 Jun 2012 09:27:56 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: ppsp issue tracker <trac+ppsp@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: draft-ietf-ppsp-peer-protocol@tools.ietf.org, arno@cs.vu.nl
X-Trac-Project: ppsp
Date: Wed, 20 Jun 2012 07:27:56 -0000
X-URL: http://tools.ietf.org/ppsp/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/ppsp/trac/ticket/17#comment:1
Message-ID: <067.ea7ff762669066e26c72ef9090d75fd4@trac.tools.ietf.org>
References: <052.00142fc93bf68c33bab6a98e02a7eb3f@trac.tools.ietf.org>
X-Trac-Ticket-ID: 17
In-Reply-To: <052.00142fc93bf68c33bab6a98e02a7eb3f@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-ppsp-peer-protocol@tools.ietf.org, arno@cs.vu.nl, ppsp@ietf.org
X-SA-Exim-Mail-From: trac+ppsp@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To:
Resent-Message-Id: <20120620072759.022C721F8705@ietfa.amsl.com>
Resent-Date: Wed, 20 Jun 2012 00:27:59 -0700
Resent-From: trac+ppsp@trac.tools.ietf.org
X-Mailman-Approved-At: Wed, 20 Jun 2012 00:29:16 -0700
Cc: ppsp@ietf.org
Subject: Re: [ppsp] #17: How to formulate behaviour of Peer-Exchange messages?
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2012 07:27:59 -0000

#17: How to formulate behaviour of Peer-Exchange messages?

Changes (by arno@…):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Recent has been defined as "in the last 60 seconds".

-- 
---------------------------+----------------------------------------------
 Reporter:  arno@…         |       Owner:  draft-ietf-ppsp-peer-protocol@…
     Type:  enhancement    |      Status:  closed
 Priority:  major          |   Milestone:
Component:  peer-protocol  |     Version:
 Severity:  -              |  Resolution:  fixed
 Keywords:                 |
---------------------------+----------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/ppsp/trac/ticket/17#comment:1>
ppsp <http://tools.ietf.org/ppsp/>