From lemonade-bounces@ietf.org Tue Jul 05 15:13:42 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpsrW-0002JJ-Hq; Tue, 05 Jul 2005 15:13:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpsrN-0002CN-LQ for lemonade@megatron.ietf.org; Tue, 05 Jul 2005 15:13:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09249 for ; Tue, 5 Jul 2005 15:13:32 -0400 (EDT) Received: from warlock.qualcomm.com ([129.46.50.49]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DptHb-0005CT-Qx for lemonade@ietf.org; Tue, 05 Jul 2005 15:40:41 -0400 Received: from [129.46.74.75] (loud.qualcomm.com [129.46.74.75]) by warlock.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j65JCZpK020577; Tue, 5 Jul 2005 12:12:36 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: <2884.1119949051.389333@peirce> References: <54E40201497DF142B06B27255953F79715EDB3A9@il0015exch007u.ih.lucent.co m > <15685.1119638056.665131@peirce> <15685.1119648267.127122@peirce> <15685.1119656062.522145@peirce> <15685.1119658417.662638@peirce> <2884.1119949051.389333@peirce> X-Mailer: Eudora for Mac OS X v7.0a X-message-flag: Using Outlook? Upgrade to Eudora: Date: Tue, 5 Jul 2005 11:35:19 -0700 To: Dave Cridland From: Randall Gellens Subject: RE: [lemonade] Fwd: Appeal of decision to standardize "Mapping Be tween the Multimedia Messaging Service (MMS) and Internet Mail" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 1.0 (+) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org At 9:57 AM +0100 6/28/05, Dave Cridland wrote: > I'm fine with a "SHOULD be dropped" for MMS->Internet, but I'd like > a "MUST be dropped" for Internet->MMS. I've been thinking about this for a few days. I'm not sure we can justify MUST here; instead we can say SHOULD along with an explanation of why such headers should not be trusted, and hence should be dropped in the absence of specific knowledge in a specific environment. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Justify my text? I'm sorry but it has no excuse. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 05 15:52:28 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DptO2-0001E2-69; Tue, 05 Jul 2005 15:47:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DptNo-000128-6n for lemonade@megatron.ietf.org; Tue, 05 Jul 2005 15:47:05 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13975 for ; Tue, 5 Jul 2005 15:47:01 -0400 (EDT) Received: from carrierpigeon.cs.umd.edu ([128.8.129.58]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DptjX-0003li-OX for lemonade@ietf.org; Tue, 05 Jul 2005 16:09:32 -0400 Received: from MINDLAP2 (mindlap2.cs.umd.edu [172.16.0.37]) (authenticated bits=0) by carrierpigeon.cs.umd.edu (8.12.10/8.12.5) with ESMTP id j65JfWtT017067 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 5 Jul 2005 15:41:34 -0400 (EDT) Message-Id: <200507051941.j65JfWtT017067@carrierpigeon.cs.umd.edu> From: "Moustafa Youssef" To: Date: Tue, 5 Jul 2005 15:41:14 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab Content-Transfer-Encoding: quoted-printable Subject: [lemonade] 1st CFP: 2nd IEEE Workshop on Dependability and Security in Sensor Networks and Systems X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org (Our apologies if you receive multiple copies of this CFP) ------------------------------------------------------------- First Call for Papers Second IEEE Workshop on Dependability and Security in Sensor Networks and Systems (DSSNS=922006) http://www.dssns.org In conjunction with 2nd NASA/IEEE Systems and Software Week 30th NASA/IEEE Software Engineering Workshop (SEW=922006) April 24-28, 2006 Recently, there has been a growing interest in the potential use of networked sensors in applications such as smart environments,=20 disaster management, combat field reconnaissance, and security=20 surveillance. While the initial view of the community was that=20 networked sensors will play a complementary role that enhances=20 the quality of these applications, recent research results have=20 encouraged practitioners to envision an increased reliance on sensor=20 networks and systems (SN&S) in such critical and sensitive applications. Therefore to realize their potential, necessary dependability and=20 security (D&S) measures have to be incorporated in the design and=20 during the operation of SN&S. Dependability is usually specified=20 using attributes like reliability, survivability, safety, maintainability,=20 and availability in presence of failure, while security is specified by=20 attributes like integrity, authenticity, confidentiality, and availability=20 in presence of attacks. D&S services accomplish tasks for attack and failure prevention, detection and response. The scope of D&S services may span the deployed sensors to command nodes and likely beyond. It also=20 involves D&S support at, and cross-cutting, the protocol stack layers=20 from physical to application. Achieving dependability and security in SN&S will require non-conventional=20 mechanisms due to many factors including: (1) sensors are significantly constrained in the amount of available resources such as energy, storage and computation; (2) sensors are expected to be deployed in very large numbers in normal as well as harsh/hostile environments; (3) sensor networks suffer from structural weakness and limited physical protection, and (4) localization of impact is complicated due to the un-tethered nature of SN&S and of the potential attackers. In addition, D&S requirements may vary according to mission defined over a multi-dimensional context, such as field of deployment (e.g., hostile versus friendly), type of application (e.g., monitoring, tracking, data collection), mode of operation (e.g., normal, exception, post-event recovery), and time. This workshop will foster a forum for discussing and presenting recent research results on dependability and security in SN&S. Topics of interest include, although not limited to, the following: - Fault and intrusion-tolerant architectures, middleware and operational models=20 - Robust routing, storage, and processing of sensed data - D&S architectures, protocols and tools - Vulnerabilities, attacks and countermeasures - Monitoring and evaluation techniques - Robust clustering techniques - Self-awareness and context-awareness=20 - Resilient virtual infrastructures - Autonomic and adaptive D&S support. - Formal representation and verification of D&S properties - Network inference support for D&S - Quality of service provisioning - Models, metrics, and measurements for D&S - Privacy-aware D&S services - Testbeds, simulation and visualization=20 - Agent-based D&S management=20 - SN&S support for D&S in larger information grids - SN&S application development environments Submission Guidelines --------------------- For guidelines regarding paper submission, please refer to the workshop=92s website (http://www.dssns.org). Papers should contain original material and not be previously published, or currently submitted for consideration elsewhere. The manuscript should not exceed 20 single-column double-space pages in PDF format, font size 11 or larger. The first page should include title, authors' contact information, abstract and five keywords.=20 Important Dates ---------------- Submission deadline: November 7, 2004 Decision notification: December 20, 2004 Final manuscript due: January 20, 2005 The best paper will be recognized and selected papers will be invited to a Special Issue of the Journal of Ad Hoc and Sensor Wireless Networks.=20 Workshop Co-Chairs ------------------- Mohamed Eltoweissy Virginia Tech, USA E-mail: toweissy@vt.edu=20 Mohamed Younis University of Maryland Baltimore County, USA E-mail: younis@csee.umbc.edu=20 Publicity Co-Chairs -------------------- Denis Gracanin Virginia Tech, USA E-mail: gracanin@vt.edu Moustafa Youssef University of Maryland at College Park, USA E-mail: moustafa@cs.umd.edu=20 Program Committee ------------------ Farooq Anjum, Telcordia & U of Penn, USA David Carman, Johns Hopkins Univ.=96 Applied Physics Lab, USA Ing-Ray Chen, Virginia Tech, USA M. Nazih Elderini, Alexandria Univ, Egypt Sushil Jajodia, George Mason Univ., USA Shivakant Mishra, Univ, of Colorado, USA Peng Ning, North Carolina State U, USA Stephan Olariu, Old Dominion Univ., USA David Simplot-Ryl, Univ. Lille, INRIA Futurs, France John A. Stankovic, University of Virginia, USA Ivan Stojmenovic, Univ. of Ottawa, Canada Cliff Wang, Army Research Office, USA Stephen D. Wolthusen, Fraunhofer-IGD, Germany Albert Zomaya, Univ. of Sydney, Australia _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 05 18:08:28 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dpvae-0001lf-QA; Tue, 05 Jul 2005 18:08:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dpvaa-0001i3-TQ for lemonade@megatron.ietf.org; Tue, 05 Jul 2005 18:08:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06662 for ; Tue, 5 Jul 2005 18:08:18 -0400 (EDT) Received: from warlock.qualcomm.com ([129.46.50.49]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DpvnP-0004LZ-5H for lemonade@ietf.org; Tue, 05 Jul 2005 18:21:40 -0400 Received: from [129.46.74.75] (loud.qualcomm.com [129.46.74.75]) by warlock.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j65LrZpK000056; Tue, 5 Jul 2005 14:53:37 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: <200504061931.PAA20390@ietf.org> References: <200504061931.PAA20390@ietf.org> X-Mailer: Eudora for Mac OS X v7.0a X-message-flag: Using Outlook? Upgrade to Eudora: Date: Tue, 5 Jul 2005 14:47:51 -0700 To: lemonade@ietf.org, "Stephane H. Maes" , Alexey Melnikov From: Randall Gellens Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: Subject: [lemonade] Comments on draft-ietf-lemonade-profile-02.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org I've made a large number of comments and suggested edits to profile-02. Because of the number and extent of the comments and suggestions, I marked up a copy of the profile draft. Please see and look for lines starting with "]]]". -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- There is no human problem which could not be solved if people would simply do as I advise. -- Gore Vidal _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 05 20:15:26 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpxZW-0000pU-Lo; Tue, 05 Jul 2005 20:15:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpxXV-0007qP-NH for lemonade@megatron.ietf.org; Tue, 05 Jul 2005 20:13:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10549 for ; Tue, 5 Jul 2005 18:40:16 -0400 (EDT) Received: from rgminet04.oracle.com ([148.87.122.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DpwOl-0003ZS-Ny for lemonade@ietf.org; Tue, 05 Jul 2005 19:00:18 -0400 Received: from rgminet04.oracle.com (localhost [127.0.0.1]) by rgminet04.oracle.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id j65MWDvr021572 for ; Tue, 5 Jul 2005 16:32:13 -0600 Received: from web69 (web69.oracle.com [148.87.122.101]) by rgminet04.oracle.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id j65MWCnv021535 for ; Tue, 5 Jul 2005 16:32:12 -0600 Message-ID: <27962166.1120602779890.JavaMail.besadmin@web69> Date: Tue, 5 Jul 2005 16:32:57 -0600 From: Stephane Maes To: randy@qualcomm.com, lemonade@ietf.org, alexey.melnikov@isode.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit content-class: urn:content-classes:message Thread-Topic: Comments on draft-ietf-lemonade-profile-02.txt Thread-Index: AcWBrIDhOdVt+GmWQ/GGxoQgQyKqEwABP1bg X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 7bit Cc: Subject: [lemonade] Re: Comments on draft-ietf-lemonade-profile-02.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org Randy, Thanks We will update accordingly. Stephane _____ Stephane H. Maes, PhD, Director of Architecture - RTCC & Mobile, Oracle Corporation. Ph: +1-203-300-7786 (mobile/SMS); Fax / UM: +1-650-607-6296. e-mail: stephane.maes@oracle.com IM: shmaes (AIM, Y!,Skype) or stephane_maes@hotmail.com (MSN Messenger) -----Original Message----- From: Randall Gellens To: lemonade@ietf.org ; Stephane Maes ; Alexey Melnikov Sent: Tue Jul 05 15:47:51 2005 Subject: Comments on draft-ietf-lemonade-profile-02.txt I've made a large number of comments and suggested edits to profile-02. Because of the number and extent of the comments and suggestions, I marked up a copy of the profile draft. Please see and look for lines starting with "]]]". -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- There is no human problem which could not be solved if people would simply do as I advise. -- Gore Vidal _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Thu Jul 07 01:24:53 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqOsX-0000Wz-2k; Thu, 07 Jul 2005 01:24:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqOsS-0000Ue-Nb for lemonade@megatron.ietf.org; Thu, 07 Jul 2005 01:24:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06043 for ; Thu, 7 Jul 2005 01:24:47 -0400 (EDT) Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqPJZ-0007NV-D3 for lemonade@ietf.org; Thu, 07 Jul 2005 01:52:50 -0400 Received: from [10.0.2.7] (216.43.25.67) by episteme-software.com with ESMTP (EIMS X 3.3d14); Thu, 7 Jul 2005 00:24:33 -0500 Mime-Version: 1.0 X-Sender: resnick@resnick1.qualcomm.com (Unverified) Message-Id: In-Reply-To: References: <200504061931.PAA20390@ietf.org> X-Mailer: Eudora [Macintosh version 7.0a12] Date: Thu, 7 Jul 2005 00:24:30 -0500 To: lemonade@ietf.org From: Pete Resnick Subject: Re: [lemonade] Comments on draft-ietf-lemonade-profile-02.txt Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: Alexey Melnikov , "Stephane H. Maes" X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org On 7/5/05 at 2:47 PM -0700, Randall Gellens wrote: >I've made a large number of comments and suggested edits to profile-02. > > The advent of client/server email using the [RFC3501] and [RFC2821] >]]] ^^^^^^^ >]]] This should be RFC 2476 instead of 2821. I think both 2821 and 2476 should be included. I'm personally not fond of 2.2 or 2.3. 2.2 calls out assembly, which I don't think is necessarily a distinct operation from initiation or editing. We shouldn't imply that there are always four steps. There may be only two or three. 2.3 is a bit muddled, not being clear on the difference between retrieving drafts from the server and retrieving parts of previous messages. > The [CATENATE] extension to [RFC3501] addresses the fcc problem. It > requires making several simplifying assumptions: > (1a) there is one, and only one, fcc destination on a single > server > (2a) the server which holds the fcc is the same as the server > which stages the outgoing message for submission > (3a) it is desired that the fcc be a copy of the complete message > text with all external data inserted in the message I don't understand 1a at all. 2a is certainly true. 3a might be an overstatement depending on the implementation of CATENATE (the external data may not be inserted into the message per se). I'm share Randy's concerns about the quick reconnect section. pr -- Pete Resnick QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Jul 11 18:01:21 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ds6L3-0004LK-Iu; Mon, 11 Jul 2005 18:01:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ds6Ky-0004EA-Uu; Mon, 11 Jul 2005 18:01:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21365; Mon, 11 Jul 2005 18:01:14 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ds6n4-0003VM-5l; Mon, 11 Jul 2005 18:30:18 -0400 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Ds6Ky-0005DU-Ap; Mon, 11 Jul 2005 18:01:16 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 11 Jul 2005 18:01:16 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: lemonade@ietf.org Subject: [lemonade] Last Call: 'Message Submission BURL Extension' to Proposed Standard X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org The IESG has received a request from the Enhancements to Internet email to support diverse service environments WG to consider the following document: - 'Message Submission BURL Extension ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2005-07-25. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-lemonade-burl-01.txt _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Jul 11 18:02:21 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ds6M1-0004g5-UD; Mon, 11 Jul 2005 18:02:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ds6Lx-0004fK-2H; Mon, 11 Jul 2005 18:02:17 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21513; Mon, 11 Jul 2005 18:02:14 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ds6o2-0003Yt-Bw; Mon, 11 Jul 2005 18:31:18 -0400 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Ds6Lw-0005zt-Gg; Mon, 11 Jul 2005 18:02:16 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 11 Jul 2005 18:02:16 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: lemonade@ietf.org Subject: [lemonade] Last Call: 'Internet Message Access Protocol (IMAP) CATENATE Extension' to Proposed Standard X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org The IESG has received a request from the Enhancements to Internet email to support diverse service environments WG to consider the following document: - 'Internet Message Access Protocol (IMAP) CATENATE Extension ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2005-07-25. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-lemonade-catenate-05.txt _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Mon Jul 11 18:15:08 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ds6YO-00039o-M3; Mon, 11 Jul 2005 18:15:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ds6YI-000389-C9; Mon, 11 Jul 2005 18:15:02 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24329; Mon, 11 Jul 2005 18:14:59 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ds70N-0004SP-Oa; Mon, 11 Jul 2005 18:44:03 -0400 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Ds6YH-0007Sm-Pt; Mon, 11 Jul 2005 18:15:01 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 11 Jul 2005 18:15:01 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: lemonade@ietf.org Subject: [lemonade] Last Call: 'Internet Message Access Protocol (IMAP) - URLAUTH Extension' to Proposed Standard X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org The IESG has received a request from the Enhancements to Internet email to support diverse service environments WG to consider the following document: - 'Internet Message Access Protocol (IMAP) - URLAUTH Extension ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2005-07-25. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-lemonade-urlauth-07.txt _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 12 16:17:13 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsRBp-0005yg-CG; Tue, 12 Jul 2005 16:17:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsRBn-0005yG-6j for lemonade@megatron.ietf.org; Tue, 12 Jul 2005 16:17:11 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08819 for ; Tue, 12 Jul 2005 16:17:09 -0400 (EDT) Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsRe2-0007oc-QK for lemonade@ietf.org; Tue, 12 Jul 2005 16:46:24 -0400 Received: from [192.168.0.3] ([62.3.217.253]) by rufus.isode.com via TCP (internal) with ESMTPA; Tue, 12 Jul 2005 21:16:39 +0100 Message-ID: <42D42526.10809@isode.com> Date: Tue, 12 Jul 2005 21:16:38 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en To: Pete Resnick Subject: Re: [lemonade] Comments on draft-ietf-lemonade-profile-02.txt References: <200504061931.PAA20390@ietf.org> In-Reply-To: MIME-version: 1.0 Content-type: text/plain; charset="ISO-8859-1"; format="flowed" Content-transfer-encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 7bit Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org Pete Resnick wrote: > On 7/5/05 at 2:47 PM -0700, Randall Gellens wrote: > >> I've made a large number of comments and suggested edits to profile-02. >> >> The advent of client/server email using the [RFC3501] and [RFC2821] >> ]]] ^^^^^^^ >> ]]] This should be RFC 2476 instead of 2821. > > > I think both 2821 and 2476 should be included. I've added 2476. > [...] > >> The [CATENATE] extension to [RFC3501] addresses the fcc problem. It >> requires making several simplifying assumptions: >> (1a) there is one, and only one, fcc destination on a single >> server >> (2a) the server which holds the fcc is the same as the server >> which stages the outgoing message for submission >> (3a) it is desired that the fcc be a copy of the complete message >> text with all external data inserted in the message > > I don't understand 1a at all. FCC functionality is achieved by catenated APPEND. If the client wants to FCC to multiple locations, it has to copy the constructed message to one or more mailbox on the same or different server. So pure CATENATE can't do FCC to multiple locations. > 2a is certainly true. Yes. > 3a might be an overstatement depending on the implementation of > CATENATE (the external data may not be inserted into the message per se). Right, the catenated message may contain URLs in body parts. Should I just delete 3a? Alexey _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 12 17:45:16 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsSZ2-0003LH-Ua; Tue, 12 Jul 2005 17:45:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsSZ1-0003KA-Cm for lemonade@megatron.ietf.org; Tue, 12 Jul 2005 17:45:15 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20572 for ; Tue, 12 Jul 2005 17:45:13 -0400 (EDT) Received: from salvelinus.brooktrout.com ([204.176.205.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsT1G-0006JI-HP for lemonade@ietf.org; Tue, 12 Jul 2005 18:14:29 -0400 Received: from nhmail2.needham.brooktrout.com (nhmail2.brooktrout.com [204.176.205.242]) by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id j6CLeloa025266 for ; Tue, 12 Jul 2005 17:40:48 -0400 (EDT) Received: by nhmail2.brooktrout.com with Internet Mail Service (5.5.2653.19) id ; Tue, 12 Jul 2005 17:35:43 -0400 Message-ID: From: Eric Burger To: lemonade@ietf.org Date: Tue, 12 Jul 2005 17:35:42 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [lemonade] Tentative Meeting Times X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org The secretariat has floated the first draft of the draft IETF 63 Agenda. The first lemonade session is tentatively scheduled for: Tuesday, 2 August, from 10:30am - 12:30pm. The plan is for this session to be the update / review / education / blah time for the community and work group. The second lemonade session is tentatively scheduled for: Wednesday, 3 August, from 2pm - 4pm. The plan is for this session to be a working session. Everyone is, of course, invited. Even if you are from the OMA :) Read all the drafts and review the mail list. Resources are at the charter page: and supplemental page: . PLEASE do note the use of conditional adverbs above. IETF schedules are notoriously fluid! _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 12 18:45:47 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsTVb-0008Sp-TS; Tue, 12 Jul 2005 18:45:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsTVb-0008Sk-3z for lemonade@megatron.ietf.org; Tue, 12 Jul 2005 18:45:47 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27054 for ; Tue, 12 Jul 2005 18:45:44 -0400 (EDT) Received: from dsl-217-155-137-62.zen.co.uk ([217.155.137.62] helo=gw2.gestalt.entity.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsTxs-0000JS-0t for lemonade@ietf.org; Tue, 12 Jul 2005 19:15:01 -0400 Received: from peirce (dsl-217-155-137-61.zen.co.uk [217.155.137.61]) by gw2.gestalt.entity.net (Postfix) with ESMTP id 104B8154009; Tue, 12 Jul 2005 22:45:15 +0000 (UTC) Date: Tue, 12 Jul 2005 23:45:14 +0100 Subject: Re: [lemonade] Comments on draft-ietf-lemonade-profile-02.txt References: <200504061931.PAA20390@ietf.org> <42D42526.10809@isode.com> In-Reply-To: <42D42526.10809@isode.com> MIME-Version: 1.0 Message-Id: <16372.1121208315.012287@peirce> From: Dave Cridland To: Alexey Melnikov Content-Type: text/plain; charset="us-ascii"; format="flowed" X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Cc: lemonade@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org On Tue Jul 12 21:16:38 2005, Alexey Melnikov wrote: > Pete Resnick wrote: > >> On 7/5/05 at 2:47 PM -0700, Randall Gellens wrote: >> >>> The [CATENATE] extension to [RFC3501] addresses the fcc >>> problem. It >>> requires making several simplifying assumptions: >>> (1a) there is one, and only one, fcc destination on a >>> single >>> server >>> (2a) the server which holds the fcc is the same as the >>> server >>> which stages the outgoing message for submission >>> (3a) it is desired that the fcc be a copy of the complete >>> message >>> text with all external data inserted in the message >> >> I don't understand 1a at all. > > FCC functionality is achieved by catenated APPEND. If the client > wants to FCC to multiple locations, it has to copy the constructed > message to one or more mailbox on the same or different server. So > pure CATENATE can't do FCC to multiple locations. > > Kind of. CATENATE makes for a useful replacement for COPY, since it works in authenticated state. My implementation picks it where the source message is not in the currently selected mailbox, if any. So where CATENATE is supported (and I don't have access to a server implementation as yet), my client would use CATENATE for multiple folder destinations on the same host, most of the time. >> 2a is certainly true. > > Yes. > > Yes, there's no method for assembling a message from multiple servers with CATENATE. (There is with POSTADDRESS + BURL, of course). >> 3a might be an overstatement depending on the implementation of >> CATENATE (the external data may not be inserted into the message >> per se). > > Right, the catenated message may contain URLs in body parts. Should > I just delete 3a? You've lost me. 3a isn't true anyway - you could assemble a temporary message for submission purposes, and extract the text again with CATENATE to a new message which is kept. But more importantly, surely CATENATE acts as if it assembles the message, copying all parts as required, regardless of whether it actually does or not? Thus if I copy sections from another message. and delete/expunge the original, the new message still has the data. Dave. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 12 23:30:53 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsXxV-0006XO-HC; Tue, 12 Jul 2005 23:30:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsXxT-0006W5-1g for lemonade@megatron.ietf.org; Tue, 12 Jul 2005 23:30:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21663 for ; Tue, 12 Jul 2005 23:30:47 -0400 (EDT) Received: from zcars04e.nortelnetworks.com ([47.129.242.56] helo=zcars04e.ca.nortel.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsYPk-0002qc-TV for lemonade@ietf.org; Wed, 13 Jul 2005 00:00:06 -0400 Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com [47.129.230.95]) by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id j6D3T8Q07938 for ; Tue, 12 Jul 2005 23:29:08 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 12 Jul 2005 23:30:26 -0400 Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D055C09D5@zcarhxm0.corp.nortel.com> Thread-Topic: OMA liaison Thread-Index: AcWHKxU3Q3SPjrfuQg6NeSJAMLgJWgAAk1MQ From: "Glenn Parsons" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: quoted-printable Subject: [lemonade] OMA liaison X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org Folks, The IETF LEMONADE WG has received a liaison from the OMA Mobile Email SWG. We have put Word and PDF versions on the supplemental site: http://flyingfox.snowshore.com/i-d/lemonade/OMA-LS_0033-Mobile_email_IET F_Lemonade-V1_0-20050711.pdf They have also included the current version of their Mobile Email Requirements: http://flyingfox.snowshore.com/i-d/lemonade/OMA-RD-MobileEmail-V1_0-2005 0614.pdf I encourage everyone to read these. Cheers, Glenn. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 12 23:49:30 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsYFW-0008Md-Ho; Tue, 12 Jul 2005 23:49:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsYFU-0008MY-IE for lemonade@megatron.ietf.org; Tue, 12 Jul 2005 23:49:28 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22741 for ; Tue, 12 Jul 2005 23:49:25 -0400 (EDT) Received: from zcars04e.nortelnetworks.com ([47.129.242.56] helo=zcars04e.ca.nortel.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsYho-0003UT-Ng for lemonade@ietf.org; Wed, 13 Jul 2005 00:18:45 -0400 Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com [47.129.230.95]) by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id j6D3lmQ08610 for ; Tue, 12 Jul 2005 23:47:49 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 12 Jul 2005 23:49:07 -0400 Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D055C09DB@zcarhxm0.corp.nortel.com> Thread-Topic: OMA liaison requested actions Thread-Index: AcWHXdG11j2MjpzqRXOnlwvh2vhiTg== From: "Glenn Parsons" To: X-Spam-Score: 0.5 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Subject: [lemonade] OMA liaison requested actions X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1642615066==" Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org This is a multi-part message in MIME format. --===============1642615066== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5875D.D245AA0A" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5875D.D245AA0A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, As chair, this is my interpretation of the four requested actions of the LEMONADE WG in the OMA liaison. * Considers the OMA Mobile E-mail RD as input from the mobile community in terms of requirements for mobile e-mail features that may affect the LEMONADE activities. We should consider these requirements as input (or even the basis) of LEMONADE phase 2 goals. Further, we should advise OMA if we see any issues with this document. * Provides feedback on the possible relevance of LEMONADE work We should indicate to OMA that the LEMONADE work is very relevant and is already chartered to work on this. Though we need to review all the specific requirements and potential new work items individually. We need to determine if the work is already underway, not yet underway but in charter, or not underway and we need to recharter. * Provides its view on preferred potential collaboration in order to support one realization the OMA mobile e-mail enabler, if LEMONADE WG considers its activities relevant to the OMA mobile e-mail enabler requirements. We should indicate that not only is our work relevant to the 'enabler', but further that any work to change Internet Mail protocols (IMAP, SMTP, etc.) should only be done in the IETF. We should be clear on what documents are being produced by OMA and IETF. * Encourages its participants who work for OMA member companies to accept the invitation to attend the OMA Mobile E-mail SWG interim meeting This meeting is scheduled Aug 8-9 in Paris. I encourage all who can change their ticket to consider attending this meeting. Cheers, Glenn.. ------_=_NextPart_001_01C5875D.D245AA0A Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable OMA liaison requested actions

Folks,

As chair, this is my = interpretation of the four requested actions of the LEMONADE WG in the = OMA liaison.

* Considers the OMA Mobile E-mail = RD as input from the mobile community in terms of requirements for = mobile e-mail features that may affect the LEMONADE = activities.

We should consider these = requirements as input (or even the basis) of LEMONADE phase 2 = goals.  Further, we should advise OMA if we see any issues with = this document.

* Provides feedback on the = possible relevance of LEMONADE work

We should indicate to OMA that = the LEMONADE work is very relevant and is already chartered to work on = this.  Though we need to review all the specific requirements and = potential new work items individually.  We need to determine if the = work is already underway, not yet underway but in charter, or not = underway and we need to recharter.

* Provides its view on preferred = potential collaboration in order to support one realization the OMA = mobile e-mail enabler, if LEMONADE WG considers its activities relevant = to the OMA mobile e-mail enabler requirements.

We should indicate that not only = is our work relevant to the 'enabler', but further that any work to = change Internet Mail protocols (IMAP, SMTP, etc.) should only be done in = the IETF.  We should be clear on what documents are being produced = by OMA and IETF.

* Encourages its participants who = work for OMA member companies to accept the invitation to attend the OMA = Mobile E-mail SWG interim meeting

This meeting is scheduled Aug 8-9 = in Paris.  I encourage all who can change their ticket to consider = attending this meeting.

Cheers,
Glenn..




------_=_NextPart_001_01C5875D.D245AA0A-- --===============1642615066== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade --===============1642615066==-- From lemonade-bounces@ietf.org Thu Jul 14 09:53:51 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt49v-0003rW-C5; Thu, 14 Jul 2005 09:53:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt49q-0003qv-Vy for lemonade@megatron.ietf.org; Thu, 14 Jul 2005 09:53:49 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09817 for ; Thu, 14 Jul 2005 09:53:45 -0400 (EDT) Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dt4cR-00021M-Q9 for lemonade@ietf.org; Thu, 14 Jul 2005 10:23:22 -0400 Received: from [172.16.2.101] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (internal) with ESMTPA; Thu, 14 Jul 2005 14:53:28 +0100 Message-ID: <42D66E58.7080409@isode.com> Date: Thu, 14 Jul 2005 14:53:28 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en To: Stephane Maes MIME-version: 1.0 Content-type: text/plain; charset="KOI8-R"; format="flowed" Content-transfer-encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Content-Transfer-Encoding: 7bit Cc: Lemonade WG Subject: [lemonade] Persistent UIDs (comments on draft-maes-lemonade-monoincuid-00.txt) X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org After quickly scanning through the draft I have some comments. I list the specific comments first. >2.1. UID > > As specified in RFC 3501, section 2.3.1.1, "The unique identifier of > a message MUST NOT change during the session, and SHOULD NOT change > between sessions." Changing the UID of email messages imposes a very > heavy computational and bandwidth burden on a mobile client. For a > server compliant to MONOINCUID, the UID MUST always monotonically > increase. My understanding of RFC 3501 that any server that violates this MUST requirement is not an IMAP4rev1 server. So this should be dropped. >It MUST remain unchanged between sessions and monotonically > increase. "MUST ... monotonically increase" just repeats the previous sentence. > It MAY also increase without gaps in its sequence. I don't understand the reason for this sentence. If two messages got delivered and the first of them got deleted and expunged, surely there is would be a gap? ========= More general comments about the draft: 1). The document defines a new capability that describes mailstore capabilities. There were some previous discussions about defining an IMAP extension for listing mailstore capabilities. This need further investigation. 2). Some IMAP servers support multiple mailstores that have different characteristics and different mailstores may be accessed at the same time using different namespaces (RFC 2342). Note, that draft-maes-lemonade-monoincuid-00.txt can't support that: it requires that all mailstores are able to have persistent UIDs. 3). Mark Crispin has recently updated UIDPLUS (RFC 2359) in draft-crispin-imap-rfc2359bis-04.txt. The draft adds UIDNOTSTICKY response code, whichi is exactly the opposite of MONOINCUID capability and addresses the problem described in item 2) above. 4). Combining 2) and 3) together, I am thinking that a better approach would be to define an extension to NAMESPACE command that can list if a mailstore under a particular namespace allows for persistent UIDs, something like this: S: * NAMESPACE (("" "/" "PERSISTUID"))(("Other Users/" "/" "PERSISTUID")) (("News/" "/")) (i.e. all personal mailboxes allow for persistent UIDs and "News" don't) Thoughts? Alexey __________________________________________ Isode M-Box Message Store developer http://www.isode.com/products/m-box.html IETF standard related pages: http://www.melnikov.ca/mel/devel/Links.html Personal Home Page: http://www.melnikov.ca __________________________________________ _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Thu Jul 14 16:11:45 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtA3d-00075F-To; Thu, 14 Jul 2005 16:11:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtA3b-00074x-Rg; Thu, 14 Jul 2005 16:11:43 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19223; Thu, 14 Jul 2005 16:11:41 -0400 (EDT) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtAWH-000282-1w; Thu, 14 Jul 2005 16:41:21 -0400 Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com [47.129.230.95]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j6EKBMF17457; Thu, 14 Jul 2005 16:11:22 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C588B0.220609B7" Date: Thu, 14 Jul 2005 16:10:45 -0400 Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D056ACD31@zcarhxm0.corp.nortel.com> X-MS-Has-Attach: yes Thread-Topic: RFC 4024 on Voice Messaging Client Behaviour Thread-Index: AcWH9jFfdDYan3RSRiO2YpFivEl7uQAuMotw From: "Glenn Parsons" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 Cc: lemonade@ietf.org Subject: [lemonade] FW: RFC 4024 on Voice Messaging Client Behaviour X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C588B0.220609B7 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable FYI,=20 Another VPIM RFC has finally published. That leaves three remaining in the RFC Editors Queue: draft-ietf-vpim-ivm draft-ietf-vpim-vpimdir draft-ietf-vpim-routing These should hopefully publish within the next month. Cheers, Glenn. -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org Sent: Wednesday, July 13, 2005 5:58 PM To: ietf-announce@ietf.org Cc: rfc-editor@rfc-editor.org Subject: RFC 4024 on Voice Messaging Client Behaviour A new Request for Comments is now available in online RFC libraries. RFC 4024 Title: Voice Messaging Client Behaviour Author(s): G. Parsons, J. Maruszak Status: Informational Date: July 2005 Mailbox: gparsons@nortel.com, jjmaruszak@sympatico.ca Pages: 9 Characters: 18560 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ema-vpim-cb-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4024.txt This document defines the expected behaviour of a client to various aspects of a Voice Profile for Internet Mail (VPIM) message or any voice and/or fax message. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. ------_=_NextPart_001_01C588B0.220609B7 Content-Type: application/octet-stream; name="ATT4699006.TXT" Content-Description: ATT4699006.TXT Content-Disposition: attachment; filename="ATT4699006.TXT" Content-Transfer-Encoding: base64 Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl cnZlciI7DQoJc2VydmVyPSJSRkMtSU5GT0BSRkMtRURJVE9SLk9SRyINCg0KQ29udGVudC1UeXBl OiB0ZXh0L3BsYWluDQpDb250ZW50LUlEOiA8MDUwNzEzMTQ1NjUxLlJGQ0BSRkMtRURJVE9SLk9S Rz4NCg0KUkVUUklFVkU6IHJmYw0KRE9DLUlEOiByZmM0MDI0DQo= ------_=_NextPart_001_01C588B0.220609B7 Content-Type: application/octet-stream; name="rfc4024.URL" Content-Description: rfc4024.URL Content-Disposition: attachment; filename="rfc4024.URL" Content-Transfer-Encoding: base64 W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlzaS5lZHUvaW4tbm90ZXMvcmZjNDAy NC50eHQNCg== ------_=_NextPart_001_01C588B0.220609B7 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade ------_=_NextPart_001_01C588B0.220609B7-- From lemonade-bounces@ietf.org Mon Jul 18 15:50:21 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dubd7-00081j-A0; Mon, 18 Jul 2005 15:50:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dubcq-0007sn-3L; Mon, 18 Jul 2005 15:50:04 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10334; Mon, 18 Jul 2005 15:50:01 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Duc6I-0006Wm-Fv; Mon, 18 Jul 2005 16:20:31 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dubcn-0002Fl-H8; Mon, 18 Jul 2005 15:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 18 Jul 2005 15:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-reconnect-03.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to support diverse service environments Working Group of the IETF. Title : IMAP4 Extensions for Quick Reconnect Author(s) : C. Wilson, A. Melnikov Filename : draft-ietf-lemonade-reconnect-03.txt Pages : 26 Date : 2005-7-18 This document defines a quick reconnect IMAP4 extension, which gives a mobile client the ability to resume a previously abandoned session, without the need to perform a full synchronization sequence. The goal is to minimize the ammount of data transfered at login after a dropped connection. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-reconnect-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-reconnect-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-reconnect-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-7-18143014.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-reconnect-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-reconnect-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-18143014.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade --NextPart-- From lemonade-bounces@ietf.org Tue Jul 19 07:49:41 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuqbV-00030x-5m; Tue, 19 Jul 2005 07:49:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuqbS-0002yZ-LX; Tue, 19 Jul 2005 07:49:38 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04936; Tue, 19 Jul 2005 07:49:37 -0400 (EDT) Received: from [12.16.56.39] (helo=afir) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dur2w-0002gx-S4; Tue, 19 Jul 2005 08:18:03 -0400 Received: from mail pickup service by afir with Microsoft SMTPSVC; Tue, 19 Jul 2005 07:47:55 -0400 Received: from mail65.messagelabs.com ([216.82.244.83]) by afir with Microsoft SMTPSVC(5.0.2195.6713); Mon, 18 Jul 2005 15:56:11 -0400 X-VirusChecked: Checked X-Env-Sender: i-d-announce-bounces@ietf.org X-Msg-Ref: server-11.tower-65.messagelabs.com!1121716488!59926382!1 X-StarScan-Version: 5.4.15; banners=-,-,anspach.com X-Originating-IP: [132.151.6.71] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, MIME_BOUND_NEXTPART,NO_REAL_NAME Received: (qmail 27355 invoked from network); 18 Jul 2005 19:54:48 -0000 Received: from megatron.ietf.org (132.151.6.71) by server-11.tower-65.messagelabs.com with SMTP; 18 Jul 2005 19:54:48 -0000 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dubd3-00080e-D3; Mon, 18 Jul 2005 15:50:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dubcq-0007sn-3L; Mon, 18 Jul 2005 15:50:04 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10334; Mon, 18 Jul 2005 15:50:01 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Duc6I-0006Wm-Fv; Mon, 18 Jul 2005 16:20:31 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dubcn-0002Fl-H8; Mon, 18 Jul 2005 15:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 18 Jul 2005 15:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-OriginalArrivalTime: 18 Jul 2005 19:56:11.0828 (UTC) FILETIME=[BF44D740:01C58BD2] X-Spam-Score: 0.4 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-reconnect-03.txt X-BeenThere: lemonade@ietf.org Reply-To: internet-drafts@ietf.org List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to support diverse service environments Working Group of the IETF. Title : IMAP4 Extensions for Quick Reconnect Author(s) : C. Wilson, A. Melnikov Filename : draft-ietf-lemonade-reconnect-03.txt Pages : 26 Date : 2005-7-18 This document defines a quick reconnect IMAP4 extension, which gives a mobile client the ability to resume a previously abandoned session, without the need to perform a full synchronization sequence. The goal is to minimize the ammount of data transfered at login after a dropped connection. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-reconnect-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-reconnect-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-reconnect-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ______________________________________________________________________ This e-mail has been scanned by MCI Managed Email Content Service, using Skeptic(tm) technology powered by MessageLabs. For more information on MCI's Managed Email Content Service, visit http://www.mci.com. ______________________________________________________________________ --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-7-18143014.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-reconnect-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-reconnect-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-18143014.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade --NextPart-- From lemonade-bounces@ietf.org Tue Jul 19 15:52:41 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duy8v-0003M8-6Z; Tue, 19 Jul 2005 15:52:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duy6b-0002d0-4M; Tue, 19 Jul 2005 15:50:17 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28062; Tue, 19 Jul 2005 15:50:14 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Duya7-0001ba-Vb; Tue, 19 Jul 2005 16:20:51 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Duy6O-0002Q5-5C; Tue, 19 Jul 2005 15:50:04 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 19 Jul 2005 15:50:04 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-profile-03.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to support diverse service environments Working Group of the IETF. Title : Lemonade Profile Author(s) : S. Maes, A. Melnikov Filename : draft-ietf-lemonade-profile-03.txt Pages : 17 Date : 2005-7-19 This document describes a profile (a set of required extensions, restrictions and usage modes) of the IMAP and mail submission protocols. This profile allows clients (especially those that are constrained in memory, bandwidth, processing power, or other areas) to efficiently use IMAP and Submission to access and submit mail. This includes the ability to forward received mail without needing to download and upload the mail, to schedule future delivery of a message, to optimize submission and to efficiently reconnect in case of loss of connectivity with the server. The Lemonade profile relies upon extensions to IMAP and Mail Submission protocols; specifically URLAUTH and CATENATE IMAP protocol [RFC3501] extensions and BURL extension to the SUBMIT protocol [RFC2476]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-profile-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-lemonade-profile-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-lemonade-profile-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-7-19134830.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-lemonade-profile-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-lemonade-profile-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-19134830.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade --NextPart-- From lemonade-bounces@ietf.org Tue Jul 19 16:57:56 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuzA4-0007HH-5O; Tue, 19 Jul 2005 16:57:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuzA0-0007Gg-7o for lemonade@megatron.ietf.org; Tue, 19 Jul 2005 16:57:52 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25339 for ; Tue, 19 Jul 2005 16:57:50 -0400 (EDT) Received: from 216-43-25-66.ip.mcleodusa.net ([216.43.25.66] helo=episteme-software.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Duzdg-0003M7-58 for lemonade@ietf.org; Tue, 19 Jul 2005 17:28:34 -0400 Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with ESMTP (EIMS X 3.3d14) for ; Tue, 19 Jul 2005 15:57:30 -0500 Mime-Version: 1.0 X-Sender: resnick@resnick1.qualcomm.com (Unverified) Message-Id: X-Mailer: Eudora [Macintosh version 7.0a12] Date: Tue, 19 Jul 2005 15:57:28 -0500 To: lemonade@ietf.org From: Pete Resnick Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [lemonade] Off-topic post: Query on OMA Mobile Email in Paris, Aug 8-9 X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org Apologies for abuse of the list: I know there are people here who might be going to the OMA Mobile Email meeting in Paris on August 8 and 9. Does anybody know if: 1. there is going to be reasonable network connectivity during the meeting; and 2. someone will have an iSight so that I can participate remotely from the states? I've got personal commitments that require me to be back in the states, so I can't attend in person, but I'd like to participate. Drop me a note privately if you have the info. Thanks, pr -- Pete Resnick QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Thu Jul 21 18:40:13 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dvji9-0008Fv-QS; Thu, 21 Jul 2005 18:40:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dvji8-0008Dh-JA; Thu, 21 Jul 2005 18:40:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21927; Thu, 21 Jul 2005 18:40:09 -0400 (EDT) Received: from warlock.qualcomm.com ([129.46.50.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvkCF-0005ZG-3f; Thu, 21 Jul 2005 19:11:20 -0400 Received: from [192.168.1.13] (loud.qualcomm.com [129.46.74.75]) by warlock.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j6LMdtoZ012632; Thu, 21 Jul 2005 15:39:57 -0700 (PDT) Mime-Version: 1.0 Message-Id: X-Mailer: Eudora for Mac OS X v7.0a X-message-flag: Using Outlook? Upgrade to Eudora: Date: Thu, 21 Jul 2005 15:39:32 -0700 To: iesg@ietf.org, Chris Newman From: Randall Gellens Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: Lemonade , John C Klensin Subject: [lemonade] Comments on 'Message Submission BURL Extension' X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org In section 3.4, it is not clear if in the presence of a trust relationship, the Submit server includes both "imap" and "imap://mail.example.com", or if the second implies the first. This should be clarified. (I suspect the answer is that the server should include both, since the "imap" indicates support for URLAUTH, while the "imap://" indicates support for regular IMAP URLs). In section 6, response 554 and 503 could conceivably be used in the absence of PIPELINING (if the client ignored the error responses to RCPT TO commands). This is effectively the same as PIPELINING, of course, but it might be better to say "This response code occurs when BURL is used (for example, with PIPELINING) and all RCPT TOs failed" and similarly for 503. Would it make sense for reference 6 to point to draft-gellens-submit-bis, which is in the RFC Editor's queue and will obsolete 2476? -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Everything is controlled by a small evil group to which, unfortunately, no one we know belongs. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Sat Jul 23 09:11:50 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwJnC-00048p-Ak; Sat, 23 Jul 2005 09:11:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dw5mR-0008Pa-8T; Fri, 22 Jul 2005 18:14:07 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04061; Fri, 22 Jul 2005 18:14:04 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dw6Gl-0002w7-Ar; Fri, 22 Jul 2005 18:45:27 -0400 Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Dw5mQ-0000tR-FL; Fri, 22 Jul 2005 18:14:06 -0400 Content-Type: text/plain Mime-Version: 1.0 To: IETF Announcement list From: IESG Secretary Message-Id: Date: Fri, 22 Jul 2005 18:14:06 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b X-Mailman-Approved-At: Sat, 23 Jul 2005 09:11:49 -0400 Cc: lemonade@ietf.org Subject: [lemonade] IESG response to appeal regarding draft-ietf-lemonade-mms-mapping-04 X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org The IESG has reviewed John Klensin's appeal against the approval of draft-ietf-lemonade-mms-mapping-04.txt (see http://www.ietf.org/IESG/APPEALS/klensin-appeal-lemonade-mms-mapping.txt for the full text of the appeal). Note that the Area Director principally concerned, Ted Hardie, gave technical input during the IESG discussion of the appeal, but recused himself from the approval of this response. After analysis, the IESG withdraws its approval of draft-ietf-lemonade-mms-mapping-04.txt as Proposed Standard and invites the lemonade WG to act on the following points. 1. The IESG agrees that the technical updates between the -02 and -04 versions of draft-ietf-lemonade-mms-mapping were significant enough to warrant re-review by the working group. It therefore asks the working group to review the changes between -02 and -04; if the WG is satisfied that the changes are within its intent, it should so inform the IESG. If not, it should produce a draft that restores its original intent, and so inform the IESG. When the draft is updated, the IESG will restart the review process at IETF Last Call. 2. We note that the Resent-Count header is not mentioned in the IANA Considerations. While RFC 3864 would allow it to be registered independently, based on the OMA documents, it would be valuable to include a note in the IANA Considerations indicating what registration class (Permanent or Provisional) would be sought for and stating that the registration would be accomplished by reference to those documents. Having the registration request be concurrent with or precede the approval of the revised draft would also be valuable. 3. The appeal challenges the legitimacy of a gateway standard mandating certain mappings to and from X- headers. In one place, the draft states: ...Such systems should be aware that X-headers might be removed during transit through Internet MTAs. It is not the IETF's business that the external MMS specification makes use of X- headers in a way that the IETF mail standards do not. Additionally, given the ambiguous status of X- headers due to the discrepancy between RFC 822 and RFC 2822, the WG was placed in a difficult situation. Mail gateways have to satisfy pragmatic as well as formal requirements. The IESG therefore believes that it was within the WG's scope to specify mappings to and from X- headers, as long as it is clear that they are not part of the RFC 2822 standard format and that their treatment by Internet MTAs cannot be relied on. We now believe that the above sentence describing permitted Internet MTA behavior is not sufficiently prominent in the draft, and we request that the working group expand and strengthen it or otherwise remedy the problem, unless the WG decides for other reasons to remove the X- header mappings. If the X- header mappings are retained, they are also candidates for provisional registration under RFC 3864 and should be noted as such in the IANA Considerations. 4. The appeal raises a number of other technical points that were not, as far as we know, raised during WG discussion, WG Last Call, or IETF Last Call. Some of them were raised by John Klensin in a review carried out for the General AD during IESG evaluation. We believe that if they had been raised earlier, they might have affected the document content. But this in itself does not automatically mean the IESG was wrong to approve the document at the Proposed Standard level. However, since the WG will be reconsidering the draft, if the WG wishes to make additional changes based on its review of John's technical concerns, it should do so, and inform the IESG when consensus within the WG has been reached so that a new cycle of IETF review can be initiated. 5. John's appeal raised the question of whether the working group had an adequate opportunity to review the comments raised by his review. The IESG believes that as we continue to encourage cross-area and cross-working-group review, the issue of how to make sure review comments are seen by the right people and handled in an open manner will continue to become more important. We would like to work with the community on guidelines for reviewers, ADs and working groups on how to handle these review comments. In summary, the IESG - withdraws its approval of draft-ietf-lemonade-mms-mapping-04.txt as Proposed Standard - requests the lemonade WG to review and confirm or withdraw the changes between the -02 and -04 versions - notes that the lemonade WG is free to consider other technical comments included in the appeal - requests the lemonade WG to improve the text about MTA treatment of X- headers, if these mappings are retained - requests the lemonade WG to complete the IANA Considerations as necessary, considering RFC 3864 - requests the lemonade WG to provide an updated version of the draft that reflects WG consensus, for renewed IETF Last Call and IESG review. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Sun Jul 24 21:10:29 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwrUC-0003Q6-So; Sun, 24 Jul 2005 21:10:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwrUA-0003Pn-Df for lemonade@megatron.ietf.org; Sun, 24 Jul 2005 21:10:26 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09131 for ; Sun, 24 Jul 2005 21:10:24 -0400 (EDT) Received: from salvelinus.brooktrout.com ([204.176.205.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dwryv-0003si-DM for lemonade@ietf.org; Sun, 24 Jul 2005 21:42:13 -0400 Received: from ATLANTIS.Brooktrout.com (oceans11.brooktrout.com [204.176.75.121]) by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id j6P15gvR008210 for ; Sun, 24 Jul 2005 21:05:42 -0400 (EDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Sun, 24 Jul 2005 21:05:42 -0400 Message-ID: <330A23D8336C0346B5C1A5BB196666476E8FA0@ATLANTIS.Brooktrout.com> Thread-Topic: Status of audio streaming for IETF 63. Thread-Index: AcWHRx3ywkAfDMRLQbaXQ4JNMtn3UgJRRqZw From: "Eric Burger" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: quoted-printable Subject: [lemonade] FW: Status of audio streaming for IETF 63. X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org -----Original Message----- From: ietf-bounces@ietf.org [mailto:joelja@darkwing.uoregon.edu]=20 Sent: Tuesday, July 12, 2005 9:05 PM To: ietf@ietf.org Subject: Status of audio streaming for IETF 63. The new streaming effort continues for IETF 63. All eight parallel tracks=20 as well as the plenaries will be covered. It is our hope that this effort=20 will continue to provide useful timely and accessible access to the=20 proceedings of the IETF as they happen. An internet draft (revised since IETF 62) desscribing what the project=20 intends to accomplish, and the efforts up to this point is available at: http://www.ietf.org/internet-drafts/draft-jaeggli-ietftv-ng-01.txt Streams are to be delivered as 64Kb/s unicast-http-streamed mp3 audio, a popular and relativly standard way to deliver internet radio. Most platforms=20 should have a client immediatly available (windows media player, quicktime,=20 real, winamp, vlc, mplayer, zinf, etc) capable of playing back the stream. Streaming begins July 31. See the page located at: http://videolab.uoregon.edu/events/ietf/ietf63.html which will be updated as additional information including the final=20 schedule, becomes available. To test your client against a currently active stream of the same type prior to=20 the the meeting, visit the webpage for instructions. regards joelja --=20 ------------------------------------------------------------------------ -- Joel Jaeggli Unix Consulting joelja@darkwing.uoregon.edu GPG Key Fingerprint: 5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2 _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 26 21:57:18 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxbAc-0006kR-4K; Tue, 26 Jul 2005 21:57:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxbAa-0006kE-Ja; Tue, 26 Jul 2005 21:57:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11643; Tue, 26 Jul 2005 21:57:14 -0400 (EDT) Received: from warlock.qualcomm.com ([129.46.50.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dxbfj-0001Sz-0c; Tue, 26 Jul 2005 22:29:29 -0400 Received: from [192.168.1.13] (vpn-10-50-0-131.qualcomm.com [10.50.0.131]) by warlock.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j6R1utoZ002743; Tue, 26 Jul 2005 18:56:56 -0700 (PDT) Mime-Version: 1.0 Message-Id: X-Mailer: Eudora for Mac OS X v7.0a X-message-flag: Using Outlook? Upgrade to Eudora: Date: Tue, 26 Jul 2005 18:51:39 -0700 To: iesg@ietf.org, presnick@qualcomm.com From: Randall Gellens Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: Lemonade Subject: [lemonade] Comments on draft-ietf-lemonade-catenate-05.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org In Section 4 (Response Codes), do we really mean "may return a response code"? I think "SHOULD return a response code" would be better, but in any case it is not clear if "may" is intended to be normative. In Section 4.1 (BADURL Response), it is not clear if "invalid" means syntactically or semantically regarding UIDs and body parts. That is, is this response code to be used if the syntax is bad or if the referenced item does not exist? in Section 4.2 (TOOBIG Response), "The server may also wish to return" perhaps would be more clear written normatively, as "The server MAY return". Also, in the super nit-pick category, line 190 has "e.g." which should be "e.g.," (it needs a comma). -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- To die for an idea is unquestionably noble. But how much nobler it would be if men died for ideas that were true! --H.L. Mencken _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Tue Jul 26 23:00:04 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dxc9M-00059A-Gl; Tue, 26 Jul 2005 23:00:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dxc9L-00058Z-52; Tue, 26 Jul 2005 23:00:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14938; Tue, 26 Jul 2005 22:59:58 -0400 (EDT) Received: from tls.sendmail.com ([209.246.26.40] helo=foon.sendmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DxceR-00033P-Q4; Tue, 26 Jul 2005 23:32:14 -0400 Received: from lab.smi.sendmail.com ([10.210.100.93]) by foon.sendmail.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j6R2xdlV022954 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 26 Jul 2005 19:59:39 -0700 X-DomainKeys: Sendmail DomainKeys Filter v0.2.7 foon.sendmail.com j6R2xdlV022954 DomainKey-Signature: a=rsa-sha1; s=tls; d=sendmail.com; c=nofws; q=dns; b=em/TnxU+8pvSiGEerowqf5+vx3a3dBirIkPXSvpJr78tl2cKQSLET3VTjzJq+MiVS Mr4dmsLcXUQxJxm+bNJRVPoQgpb+He8CRmkKCfGTwRdClHqd8xa3mgtWfEzuA4r61x2 4BZD5uepkyPYZWirfUdAWT2Kr0A533wl2QBI18s= Received: from lab.smi.sendmail.com (localhost [127.0.0.1]) by lab.smi.sendmail.com (8.13.3/8.13.3) with ESMTP id j6R2xdVd026396; Tue, 26 Jul 2005 19:59:39 -0700 (PDT) (envelope-from guenther@lab.smi.sendmail.com) Message-Id: <200507270259.j6R2xdVd026396@lab.smi.sendmail.com> To: Randall Gellens From: Philip Guenther Subject: Re: [lemonade] Comments on draft-ietf-lemonade-catenate-05.txt In-reply-to: References: Date: Tue, 26 Jul 2005 19:59:39 -0700 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: presnick@qualcomm.com, Lemonade , iesg@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org Randall Gellens writes: >In Section 4 (Response Codes), do we really mean "may return a >response code"? I think "SHOULD return a response code" would be >better, but in any case it is not clear if "may" is intended to be >normative. The catenate draft does reference RFC 2119 or otherwise define particular words in uppercase as having special normative meaning. Changing that sentence to use "SHOULD" (or "MAY") would require many other changes to the draft to keep it consistent. On reflection, I agree with the author's choice to use normal English prose and let the words speak for themselves. No, really, we can use the words "may", "should", and "must" as other than normative baseball bats to beat implementors with. With regards to that particular sentence, I read it as being descriptive, acting as an introduction to the subsections that follow. >In Section 4.1 (BADURL Response), it is not clear if "invalid" means >syntactically or semantically regarding UIDs and body parts. That >is, is this response code to be used if the syntax is bad or if the >referenced item does not exist? Given the first sentence of the subsection, it is obviously meant to apply to *all* cases where a supplied URL cannot be resolved to a chunk of text to include. Perhaps the second sentence should be changed to start "Some possible reasons..." to make it clear that the list is _not_ exhaustive. Philip Guenther _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Wed Jul 27 08:21:53 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dxkv3-0004yh-0Q; Wed, 27 Jul 2005 08:21:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dxkv2-0004xr-4L; Wed, 27 Jul 2005 08:21:52 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22257; Wed, 27 Jul 2005 08:21:50 -0400 (EDT) Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DxlQG-0002v8-3q; Wed, 27 Jul 2005 08:54:10 -0400 Received: from [172.16.2.145] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (internal) with ESMTPA; Wed, 27 Jul 2005 13:21:20 +0100 Message-ID: <42E77C3E.5060308@isode.com> Date: Wed, 27 Jul 2005 13:21:18 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en To: Randall Gellens Subject: Re: [lemonade] Comments on draft-ietf-lemonade-catenate-05.txt References: In-Reply-To: MIME-version: 1.0 Content-type: text/plain; charset="ISO-8859-1"; format="flowed" Content-transfer-encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7bit Cc: presnick@qualcomm.com, Lemonade , iesg@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org Randall Gellens wrote: > In Section 4.1 (BADURL Response), it is not clear if "invalid" means > syntactically or semantically regarding UIDs and body parts. That is, > is this response code to be used if the syntax is bad or if the > referenced item does not exist? Both, at least that was my intent when I recommended it. Alexey _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Fri Jul 29 12:26:34 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyXgw-0004iU-O4; Fri, 29 Jul 2005 12:26:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyXgv-0004iP-Fv for lemonade@megatron.ietf.org; Fri, 29 Jul 2005 12:26:33 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21027; Fri, 29 Jul 2005 12:26:29 -0400 (EDT) Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyYCa-0006iU-5b; Fri, 29 Jul 2005 12:59:18 -0400 Received: from zcarhxm0.corp.nortel.com (zcarhxm0.corp.nortel.com [47.129.230.95]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j6TGQA408413; Fri, 29 Jul 2005 12:26:10 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 29 Jul 2005 12:25:52 -0400 Message-ID: <085091CB2CA14E4B8B163FFC37C84E9D0599A740@zcarhxm0.corp.nortel.com> Thread-Topic: LEMONADE agenda thread-index: AcWUWi/N/WZQJ6IRSZmhf3ev6LtrWg== From: "Glenn Parsons" To: X-Spam-Score: 0.2 (/) X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae Cc: agenda@ietf.org Subject: [lemonade] LEMONADE agenda X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1988127755==" Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org This is a multi-part message in MIME format. --===============1988127755== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5945A.3317BDA7" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5945A.3317BDA7 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Folks, Here is the proposed agenda for LEMONADE next week Let me know if you have any comments. Also, editors/authors be prepared to speak to your drafts. Cheers, Glenn. LEMONADE WG agenda - IETF 63 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= Tuesday (1030-1230 Morning Session II - Room 351 ): - status of docs - RFC Editor (Goals) draft-ietf-lemonade-goals=20 - IETF last call (pull trio, s2s) draft-ietf-lemonade-burl=20 draft-ietf-lemonade-catenate=20 draft-ietf-lemonade-urlauth=20 draft-ietf-lemonade-notify-s2s=20 - AD review (Future, MMS..) draft-ietf-lemonade-mms-mapping=20 draft-ietf-lemonade-futuredelivery=20 - WG last call (Reconnect) draft-ietf-lemonade-reconnect=20 - Others? draft-ietf-lemonade-intermediary-challenges=20 draft-smaes-lemonade-s2c-notification-reqs=20 - Profile v1 draft-ietf-lemonade-profile=20 - incoming OMA liaison Wednesday (1400-1630 Afternoon Session I - Room 341 ) -Profile v2 -Stephane's OMA based proposals=20 draft-maes-lemonade-deliver=20 draft-maes-lemonade-http-binding=20 draft-maes-lemonade-lconvert=20 draft-maes-lemonade-lzip=20 draft-maes-lemonade-mobile-email=20 draft-maes-lemonade-monoincuid=20 draft-maes-lemonade-notifications-server-to-client=20 draft-maes-lemonade-p-imap=20 ------_=_NextPart_001_01C5945A.3317BDA7 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable LEMONADE agenda

Folks,

Here is the proposed agenda for = LEMONADE next week

Let me know if you have any = comments.

Also, editors/authors be prepared to = speak to your drafts.

Cheers,
Glenn.



LEMONADE WG agenda - IETF 63
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

Tuesday (1030-1230 Morning Session II - = Room 351 ):

 - status of docs
        - RFC Editor (Goals)
        =         draft-ietf-lemonade-goals
        - IETF last call (pull trio, s2s)
        =         draft-ietf-lemonade-burl
        =         draft-ietf-lemonade-catenate
        =         draft-ietf-lemonade-urlauth
        =         draft-ietf-lemonade-notify-s2s
        - AD review (Future, MMS..)
        =         draft-ietf-lemonade-mms-mapping
        =         draft-ietf-lemonade-futuredelivery
        - WG last call (Reconnect)
        =         draft-ietf-lemonade-reconnect
        - Others?
        =         draft-ietf-lemonade-intermediary-challenges
        =         draft-smaes-lemonade-s2c-notification-reqs

- Profile v1
        draft-ietf-lemonade-profile

- incoming OMA liaison



Wednesday (1400-1630 Afternoon Session = I - Room 341 )

 -Profile v2
 -Stephane's OMA based proposals =
        draft-maes-lemonade-deliver
        = draft-maes-lemonade-http-binding
        = draft-maes-lemonade-lconvert
        = draft-maes-lemonade-lzip
        = draft-maes-lemonade-mobile-email
        = draft-maes-lemonade-monoincuid
        = draft-maes-lemonade-notifications-server-to-client
        = draft-maes-lemonade-p-imap




------_=_NextPart_001_01C5945A.3317BDA7-- --===============1988127755== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade --===============1988127755==-- From lemonade-bounces@ietf.org Fri Jul 29 12:38:42 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyXsg-0007pN-Tt; Fri, 29 Jul 2005 12:38:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyXse-0007pC-N6 for lemonade@megatron.ietf.org; Fri, 29 Jul 2005 12:38:40 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22282 for ; Fri, 29 Jul 2005 12:38:37 -0400 (EDT) Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyYOL-0007E1-3V for lemonade@ietf.org; Fri, 29 Jul 2005 13:11:26 -0400 Received: from [172.16.2.171] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (internal) with ESMTPA; Fri, 29 Jul 2005 17:38:15 +0100 Message-ID: <42EA5B75.8020303@isode.com> Date: Fri, 29 Jul 2005 17:38:13 +0100 From: Alexey Melnikov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en To: lemonade@ietf.org Subject: Re: [lemonade] LEMONADE agenda References: <085091CB2CA14E4B8B163FFC37C84E9D0599A740@zcarhxm0.corp.nortel.com> In-Reply-To: <085091CB2CA14E4B8B163FFC37C84E9D0599A740@zcarhxm0.corp.nortel.com> MIME-version: 1.0 Content-type: text/plain; charset="ISO-8859-1"; format="flowed" Content-transfer-encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: 7bit X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org Glenn Parsons wrote: > - Profile v1 > draft-ietf-lemonade-profile > In particular, the WG needs to discuss which IMAP and SMTP extensions are mandatory and which are optional for phase 1. _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Fri Jul 29 16:44:43 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dybil-00044S-2R; Fri, 29 Jul 2005 16:44:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dybih-00042q-DP; Fri, 29 Jul 2005 16:44:41 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08219; Fri, 29 Jul 2005 16:44:36 -0400 (EDT) Received: from warlock.qualcomm.com ([129.46.50.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DycEP-0005LA-Vo; Fri, 29 Jul 2005 17:17:27 -0400 Received: from [192.168.1.13] (vpn-10-50-16-80.qualcomm.com [10.50.16.80]) by warlock.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j6TKiHoZ011808; Fri, 29 Jul 2005 13:44:18 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: <200507270259.j6R2xdVd026396@lab.smi.sendmail.com> References: <200507270259.j6R2xdVd026396@lab.smi.sendmail.com> X-Mailer: Eudora for Mac OS X v7.0a X-message-flag: Using Outlook? Upgrade to Eudora: Date: Fri, 29 Jul 2005 13:34:59 -0700 To: Philip Guenther From: Randall Gellens Subject: Re: [lemonade] Comments on draft-ietf-lemonade-catenate-05.txt Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Random-Sig-Tag: 1.0b28 X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: presnick@qualcomm.com, Lemonade , iesg@ietf.org X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org At 7:59 PM -0700 7/26/05, Philip Guenther wrote: > Randall Gellens writes: >>In Section 4 (Response Codes), do we really mean "may return a >>response code"? I think "SHOULD return a response code" would be >>better, but in any case it is not clear if "may" is intended to be >>normative. > > The catenate draft does reference RFC 2119 or otherwise define > particular words in uppercase as having special normative meaning. > Changing that sentence to use "SHOULD" (or "MAY") would require many > other changes to the draft to keep it consistent. On reflection, I > agree with the author's choice to use normal English prose and let the > words speak for themselves. No, really, we can use the words "may", > "should", and "must" as other than normative baseball bats to beat > implementors with. I hadn't noticed the lack of RFC 2119 reference. Interesting to have a standards-track document with no normative language. By the way, I've written a few documents that use normative language, and as far as I know have never used such language as a bat or other implement of beating. > > With regards to that particular sentence, I read it as being > descriptive, acting as an introduction to the subsections that follow. > > >>In Section 4.1 (BADURL Response), it is not clear if "invalid" means >>syntactically or semantically regarding UIDs and body parts. That >>is, is this response code to be used if the syntax is bad or if the >>referenced item does not exist? > > Given the first sentence of the subsection, it is obviously meant to > apply to *all* cases where a supplied URL cannot be resolved to a chunk > of text to include. Perhaps the second sentence should be changed to > start "Some possible reasons..." to make it clear that the list is _not_ > exhaustive. OK. -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- Anyone can do any amount of work provided it isn't the work he is supposed to be doing at the moment. --Robert Benchley _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade From lemonade-bounces@ietf.org Fri Jul 29 17:40:20 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dycaa-0003xV-EG; Fri, 29 Jul 2005 17:40:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DycaY-0003xK-Ue for lemonade@megatron.ietf.org; Fri, 29 Jul 2005 17:40:18 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10440 for ; Fri, 29 Jul 2005 17:40:15 -0400 (EDT) Received: from salvelinus.brooktrout.com ([204.176.205.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dyd6H-0006ah-3y for lemonade@ietf.org; Fri, 29 Jul 2005 18:13:06 -0400 Received: from ATLANTIS.Brooktrout.com (oceans11.brooktrout.com [204.176.75.121]) by salvelinus.brooktrout.com (8.12.5/8.12.5) with ESMTP id j6TLb3XB001156 for ; Fri, 29 Jul 2005 17:37:03 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Fri, 29 Jul 2005 17:37:01 -0400 Message-ID: <330A23D8336C0346B5C1A5BB19666647878726@ATLANTIS.Brooktrout.com> Thread-Topic: Supplementary Web Site Thread-Index: AcWUhafN3dYXlNavTGKeqOJi8CqyFg== From: "Eric Burger" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: quoted-printable Subject: [lemonade] Supplementary Web Site X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: lemonade-bounces@ietf.org Errors-To: lemonade-bounces@ietf.org The supplementary web site has been updated with the current meeting information, including a reading list. Please read before Tuesday. Thanks. General web site: _______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade