From nobody@host.caracashosting.net Tue Aug 5 08:28:05 2008 Return-Path: X-Original-To: ietfarch-ldapext-archive@core3.amsl.com Delivered-To: ietfarch-ldapext-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBFB03A6C27 for ; Tue, 5 Aug 2008 08:28:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.584 X-Spam-Level: *** X-Spam-Status: No, score=3.584 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.097, HTML_OBFUSCATE_30_40=1.362, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666] 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 ZGo+W5wcpzDG for ; Tue, 5 Aug 2008 08:28:04 -0700 (PDT) Received: from host.caracashosting.net (mail.caracashosting.net [213.218.137.36]) by core3.amsl.com (Postfix) with ESMTP id 4D9E73A6CDE for ; Tue, 5 Aug 2008 08:28:03 -0700 (PDT) Received: from nobody by host.caracashosting.net with local (Exim 4.69) (envelope-from ) id 1KQOSb-00014f-Mx for ldapext-archive@ietf.org; Tue, 05 Aug 2008 11:28:29 -0400 To: ldapext-archive@ietf.org Subject: ID#3102 Important Information Regarding Your Account From: Abbey National plc Reply-To: userdept@abbeyplc.com MIME-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: 8bit Message-Id: Date: Tue, 05 Aug 2008 11:28:29 -0400 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.caracashosting.net X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [99 99] / [47 12] X-AntiAbuse: Sender Address Domain - host.caracashosting.net
Dear ldapext-archive@ietf.org
,

We recently reviewed your account, and we suspect an unauthorized ATM based transaction. Therefore as
a preventive measure we will temporary limit your access to sensitive Abbey features. To ensure that
your account is not compromised, please login to your Abbey Online Banking and verify your identity to
prevent deactivation.

SERVICE: Abbey Online Banking.

What you need to do:

- Go to: Abbey Online Banking

https://myonlineaccounts.abbeynational.co.uk/CentralLogonWeb/

- Login to Online Banking.

Thanks for your patience.

Sincerely,
Abbey National Centre

**************************************************************************** For any inquiries, contact Customer Service. ****************************************************************************

From lastcall4@webtv.net Tue Aug 5 19:46:28 2008 Return-Path: X-Original-To: ietfarch-ldapext-archive@core3.amsl.com Delivered-To: ietfarch-ldapext-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBBB33A67D0 for ; Tue, 5 Aug 2008 19:46:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -47.841 X-Spam-Level: X-Spam-Status: No, score=-47.841 tagged_above=-999 required=5 tests=[BAYES_80=2, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_VERIZON_P=2.144, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_VERIZON_POOL=1.495, HTML_EXTRA_CLOSE=2.809, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, URIBL_BLACK=20, URIBL_OB_SURBL=10, USER_IN_WHITELIST=-100] 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 K3gCNmx9--Tn for ; Tue, 5 Aug 2008 19:46:27 -0700 (PDT) Received: from pool-96-238-48-223.prvdri.fios.verizon.net (pool-96-238-48-223.prvdri.fios.verizon.net [96.238.48.223]) by core3.amsl.com (Postfix) with SMTP id 1EC4B3A67B0 for ; Tue, 5 Aug 2008 19:46:26 -0700 (PDT) Content-Return: allowed X-Mailer: CME-V6.5.4.3; MSN Message-Id: <20080805054705.227787.qmail@pool-96-238-48-223.prvdri.fios.verizon.net> To: Subject: Angelina Jolie Free Video. From: MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 7bit Date: Tue, 5 Aug 2008 19:46:26 -0700 (PDT)
Free Video Nude Anjelina Jolie

From ldapext-bounces@ietf.org Fri Aug 29 14:48:39 2008 Return-Path: X-Original-To: ldapext-archive@optimus.ietf.org Delivered-To: ietfarch-ldapext-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1065F28C15F; Fri, 29 Aug 2008 14:48:39 -0700 (PDT) X-Original-To: ldapext@core3.amsl.com Delivered-To: ldapext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D62A528C158 for ; Fri, 29 Aug 2008 14:48:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.449 X-Spam-Level: X-Spam-Status: No, score=-4.449 tagged_above=-999 required=5 tests=[AWL=-1.850, BAYES_00=-2.599] 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 gVWXbf88m5WL for ; Fri, 29 Aug 2008 14:48:37 -0700 (PDT) Received: from boole.openldap.org (boole.openldap.org [IPv6:2001:4f8:3:ba:2e0:18ff:fe02:efec]) by core3.amsl.com (Postfix) with ESMTP id C454328C153 for ; Fri, 29 Aug 2008 14:48:36 -0700 (PDT) Received: from [192.168.1.102] (75-141-233-128.dhcp.nv.charter.com [75.141.233.128] (may be forged)) (authenticated bits=0) by boole.openldap.org (8.13.8/8.13.8) with ESMTP id m7TLmT7e009228 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 29 Aug 2008 21:48:38 GMT (envelope-from Kurt.Zeilenga@Isode.com) Message-Id: <6B4DC086-C4AF-49CA-B31F-2794FBBCD8B6@Isode.com> From: Kurt Zeilenga To: Ldapext list Mime-Version: 1.0 (Apple Message framework v928.1) Date: Fri, 29 Aug 2008 14:48:28 -0700 X-Mailer: Apple Mail (2.928.1) Cc: ietf-ldapbis@openldap.org Subject: [ldapext] IETF#73 LDAP BOF Proposal X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ldapext-bounces@ietf.org Errors-To: ldapext-bounces@ietf.org I intend to send a BOF proposal for IETF#73 for the purpose of forming a new working group to undertake LDAP standards work. Below is a rough proposal for your consideration and comments. (I am surely biased as what new engineering efforts the proposed WG ought take on, please do feel free to offer other possible work items.) -- Kurt Lightweight Directory Access Protocol (LDAP) BOF Chair(s): TBD The purpose of this BOF is to discuss the formation of a working group to undertake LDAP standards work. It is conceived that the proposed WG would undertake both the revision of existing technical specifications for LDAP extensions and the engineering of new LDAP extensions. There are numerous existing technical specifications for LDAP extensions. Most of the Standard Track specifications were published prior to the current LDAP "core" specification [RFC 4510] and are in the need of revision. In some cases, it may be more appropriate to move the extension off the Standards Track. While the work of determining which RFC should be revised (or moved off to a different track), and prioritization of the work, could be deferred to the WG, it is hoped that the BOF will reach some conclusions as to which revision work is of the highest priority. There are also numerous extensions to LDAP which seem worthy of standardization. It is hoped that the BOF will reach some conclusion as to short list of new extension work items to be undertaken (at least initially) by the proposed WG. That short list might include, for instance, in LDAP Transactions and Extensions for X.500 Alignment. By including both revision and new engineering work items in a single working group it is hoped that the sufficient participation levels will be maintained to make reasonable progress in both revision and new engineering work. _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www.ietf.org/mailman/listinfo/ldapext From ldapext-bounces@ietf.org Sat Aug 30 09:06:28 2008 Return-Path: X-Original-To: ldapext-archive@optimus.ietf.org Delivered-To: ietfarch-ldapext-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 350803A68D0; Sat, 30 Aug 2008 09:06:28 -0700 (PDT) X-Original-To: ldapext@core3.amsl.com Delivered-To: ldapext@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AFDB3A68D0 for ; Sat, 30 Aug 2008 09:06:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.079 X-Spam-Level: X-Spam-Status: No, score=-4.079 tagged_above=-999 required=5 tests=[AWL=-1.480, BAYES_00=-2.599] 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 XLg0qo7r2ekX for ; Sat, 30 Aug 2008 09:06:26 -0700 (PDT) Received: from boole.openldap.org (boole.openldap.org [IPv6:2001:4f8:3:ba:2e0:18ff:fe02:efec]) by core3.amsl.com (Postfix) with ESMTP id 149883A6359 for ; Sat, 30 Aug 2008 09:06:25 -0700 (PDT) Received: from [192.168.1.102] (75-141-233-128.dhcp.nv.charter.com [75.141.233.128] (may be forged)) (authenticated bits=0) by boole.openldap.org (8.13.8/8.13.8) with ESMTP id m7UG6PJx069932 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 30 Aug 2008 16:06:26 GMT (envelope-from Kurt.Zeilenga@isode.com) Message-Id: From: Kurt Zeilenga To: Alexey Melnikov In-Reply-To: <64f4b53b0808300747p6acf6ef1r1a6d16bc80686919@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v928.1) Date: Sat, 30 Aug 2008 09:06:25 -0700 References: <6B4DC086-C4AF-49CA-B31F-2794FBBCD8B6@Isode.com> <64f4b53b0808300747p6acf6ef1r1a6d16bc80686919@mail.gmail.com> X-Mailer: Apple Mail (2.928.1) Cc: ietf-ldapbis@openldap.org, Ldapext list Subject: Re: [ldapext] IETF#73 LDAP BOF Proposal X-BeenThere: ldapext@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: LDAP Extension Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ldapext-bounces@ietf.org Errors-To: ldapext-bounces@ietf.org On Aug 30, 2008, at 7:47 AM, Alexey Melnikov wrote: > Kurt, > Can you be more specific about which documents you have in mind for > both groups of documents you proposed to work on? For revision work, I think each LDAP extension specified as an RFC is a possible work candidate, especially those published pre-RFC4510. Obviously the working group cannot take on all at once, or even all ever. So there needs to be some prioritization done here. I have a few thoughts here, but have yet to attempt to put together my own top- few list. Pre-BOF it would be good for each person willing to do work in this area to post their top-few candidates. We can then see if there is any consensus on what the proposed WG should be chartered to do first, put that into the proposed WG charter. (My own top-few list would likely include updating LDIF [RFC2849].) For new engineering, LDAP Transaction [draft-zeilenga-ldap-txn] and LDAP Relax Rules [draft-zeilenga-ldap-relax] tops my personal list. In the next few weeks I'll try to put a draft a proposed WG charter for list discussion, and likely at BOF discussion. -- Kurt > > On Fri, Aug 29, 2008 at 10:48 PM, Kurt Zeilenga > wrote: > I intend to send a BOF proposal for IETF#73 for the purpose of forming > a new working group to undertake LDAP standards work. Below is a > rough proposal for your consideration and comments. (I am surely > biased as what new engineering efforts the proposed WG ought take on, > please do feel free to offer other possible work items.) > > -- Kurt > > > Lightweight Directory Access Protocol (LDAP) BOF > > Chair(s): TBD > > The purpose of this BOF is to discuss the formation of a working group > to undertake LDAP standards work. It is conceived that the proposed > WG would undertake both the revision of existing technical > specifications for LDAP extensions and the engineering of new LDAP > extensions. > > There are numerous existing technical specifications for LDAP > extensions. Most of the Standard Track specifications were published > prior to the current LDAP "core" specification [RFC 4510] and are in > the need of revision. In some cases, it may be more appropriate to > move the extension off the Standards Track. While the work of > determining which RFC should be revised (or moved off to a different > track), and prioritization of the work, could be deferred to the WG, > it is hoped that the BOF will reach some conclusions as to which > revision work is of the highest priority. > > There are also numerous extensions to LDAP which seem worthy of > standardization. It is hoped that the BOF will reach some conclusion > as to short list of new extension work items to be undertaken (at > least initially) by the proposed WG. That short list might include, > for instance, in LDAP Transactions and Extensions for X.500 Alignment. > > By including both revision and new engineering work items in a single > working group it is hoped that the sufficient participation levels > will be maintained to make reasonable progress in both revision and > new engineering work. > > > _______________________________________________ > Ldapext mailing list > Ldapext@ietf.org > https://www.ietf.org/mailman/listinfo/ldapext > _______________________________________________ Ldapext mailing list Ldapext@ietf.org https://www.ietf.org/mailman/listinfo/ldapext