From p2pi-bounces@ietf.org Wed Apr 23 11:52:51 2008 Return-Path: X-Original-To: p2pi-archive@ietf.org Delivered-To: ietfarch-p2pi-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 688783A6CDF; Wed, 23 Apr 2008 11:52:51 -0700 (PDT) X-Original-To: p2pi@core3.amsl.com Delivered-To: p2pi@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 582BF3A6CC3 for ; Wed, 23 Apr 2008 11:52:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 ltjgbSshW3-l for ; Wed, 23 Apr 2008 11:52:49 -0700 (PDT) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 520313A6D66 for ; Wed, 23 Apr 2008 11:52:48 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.25,700,1199682000"; d="scan'208";a="6136150" Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 23 Apr 2008 14:52:53 -0400 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m3NIqqoe029852 for ; Wed, 23 Apr 2008 14:52:52 -0400 Received: from [192.168.1.93] (rtp-vpn3-99.cisco.com [10.82.216.99]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m3NIqq0R023583 for ; Wed, 23 Apr 2008 18:52:52 GMT Message-Id: From: Cullen Jennings To: p2pi@ietf.org Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 23 Apr 2008 14:56:53 -0400 X-Mailer: Apple Mail (2.919.2) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1682; t=1208976772; x=1209840772; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20 |Subject:=20Note=20Well |Sender:=20 |To:=20p2pi@ietf.org; bh=2CHu7Dw7AQVhme9WrwLs27hEu3Vd9Y5Fzca8/I1uf0I=; b=adLCFaV2kXvMyK884Guuw5W0xpW5vkHQP/CyhKtz+PPn/h+OGJgJCOrLAa 6AR6+nc4drgYCxZmIlQsWkGVTUCctYUWMbcarfDvqrdLG49b4R6iFAnY7ygn JtNpTZPD36; Authentication-Results: rtp-dkim-2; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); Subject: [p2pi] Note Well X-BeenThere: p2pi@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: P2P Infrastructure Discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: p2pi-bounces@ietf.org Errors-To: p2pi-bounces@ietf.org When this list got set up, the welcome message did not include the standard IETF Note Well message. I would like to notify people that this list and the workshop will be run under the normal IETF rules below. Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: the IETF plenary session, any IETF working group or portion thereof, the IESG, or any member thereof on behalf of the IESG, the IAB or any member thereof on behalf of the IAB, any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4748) and RFC 3979 (updated by RFC 4879). Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3978 (and RFC 4748) for details. A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public. _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi