IMAP QUOTA extension draft-cridland-imap-quota-00 Dave Cridland Alexey Melnikov November 21, 2002.

Slides:

Advertisements

Similar presentations

Reinventing using REST. Anything addressable by a URI is called a resource GET, PUT, POST, DELETE WebDAV (MOVE, LOCK)

Advertisements

MUTE and UNMUTE Extension to RTSP draft-sergent-rtsp-mute-00.txt Aravind Narasimhan

PRIME Concepts used in BluES’n Demonstration and Briefing Meeting 17/18 November 2005 in Dresden.

Draft-lemonade-imap-submit-01.txt “Forward without Download” Allow IMAP client to include previously- received message (or parts) in or as new message.

 Need to Gather requirements and other related information  Use case Modeling ◦ What the system will do for the users.

OSI and TCP Reference Models RD-CSY  To understand  Basic definitions  Protocol  Application  Understand communication process using Reference.

Simple Mail Transfer Protocol (SMTP) CS-328 Dick Steflik.

Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.

Chapter 30 Electronic Mail Representation & Transfer

Esimerkki: Sähköposti. Lappeenranta University of Technology / JP, PH, AH Electronic Mail Three major components: user agents mail servers simple mail.

The CLS IS Unit Presents Account Storage Limits.

Form Handling, Validation and Functions. Form Handling Forms are a graphical user interfaces (GUIs) that enables the interaction between users and servers.

FTP File Transfer Protocol. Introduction transfer file to/from remote host client/server model  client: side that initiates transfer (either to/from.

2: Application Layer1 Chapter 2 Application Layer These slides derived from Computer Networking: A Top Down Approach, 6 th edition. Jim Kurose, Keith Ross.

Guide to MCSE , Enhanced 1 Activity 4-1: Creating and Adding Members to Global Groups Objective: Use Active Directory Users and Computers to create.

1 Application Layer Lecture 5 Imran Ahmed University of Management & Technology.

1 Chapter Internet Applications (DNS, )

1 Chapter Internet Applications (DNS, )

IT 424 Networks2 IT 424 Networks2 Ack.: Slides are adapted from the slides of the book: “Computer Networking” – J. Kurose, K. Ross Chapter 2: Application.

Electronic Mail Originally –Memo sent from one user to another Now –Memo sent to one or more mailboxes Mailbox –Destination point for messages.

Chapter 1 Internet & Web Basics Key Concepts Copyright © 2013 Terry Ann Morris, Ed.D. Revised 1/12/2015 by William Pegram 1.

Recovery-Oriented Computing User Study Training Materials October 2003.

Data Management Kelly Clynes Caitlin Minteer. Agenda Globus Toolkit Basic Data Management Systems Overview of Data Management Data Movement Grid FTP Reliable.

File Transfer Protocol (FTP)

August 1, 2008IETF 72 - Dublin, Ireland1 Revising QRESYNC (RFC 5162) Timo Sirainen Alexey Melnikov.

© 2007 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Partitions & Search Spaces TOI Aaron Belcher.

December 6, 2007IETF 70 - Vancouver, Canada1 Lemonade Interop event in Munich.

Diameter Group Signaling Thursday, November 07 th, 2013 draft-ietf-dime-group-signaling-02 Mark Jones, Marco Liebsch, Lionel Morand IETF 88 Vancouver,

1 SMTP - Simple Mail Transfer Protocol –RFC 821 POP - Post Office Protocol –RFC 1939 Also: –RFC 822 Standard for the Format of ARPA Internet Text.

SIEVE Mail Filtering WG IETF 69, Chicago WG Chairs: Cyrus Daboo, Alexey Melnikov Mailing List: Jabber:

1 Web Service Description Language (WSDL) 大葉大學資工系.

NT4 SP4 Security Jack Schmidt - Fermilab

MORG BOF IETF 72, Dublin July 30th, 2008 Chairs: Alexey Melnikov Randall Gellens Mailing List: Jabber:

Data Manipulation Jonathan Rosenberg dynamicsoft.

1 Web Services Web and Database Management System.

MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter Five Managing Addresses.

Chapter 10 Defining Classes. The Internal Structure of Classes and Objects Object – collection of data and operations, in which the data can be accessed.

IMAP Extension: Status-Counters ( draft-neystadt-imap- status-counters-01.txt ) John Neystadt Alexey Melnikov Ari Erev November 21, 2002 IETF-55 Update.

21 November 2002IETF 55 - Atlanta, GA, USA1 lemonade Eric Burger Glenn Parsons

RADEXT WG IETF 91 Rechartering. Why? Current charter doesn’t allow us to take on new work that is waiting in the queue Has an anachronistic Diameter entanglement.

SCIM conference call 4 September Issue #2 Add pagination capability to plural Resource attributes User Group retrieval could be resource intensive,

The world leader in serving science Overview of Thermo 21 CFR Part 11 tools Overview of software used by multiple business units within the Spectroscopy.

1 Lemonade Status Updates of assigned drafts (*) for IETF’65.5 in Ottawa May 31, 2006 / June 1, 2006 WG sessions (*) Other updates are to be presented.

Sieve Loops Tony Hansen Cyrus Daboo

Mapping Salutation to Bluetooth 4 Overview 4 Bluetooth Summary 4 Salutation Architecture Summary 4 Mapping Bluetooth SDP to Salutation APIs 4 Mapping Bluetooth.

1 Objectives Discuss File Services in Windows Server 2008 Install the Distributed File System in Windows Server 2008 Discuss and create shared file resources.

SMTP - Simple Mail Transfer Protocol RFC 821

Digital Library Syllabus Uploader Will Cameron CSC 8530 Fall 2006 Presentation 1.

CITA 310 Section 6 Providing Services (Textbook Chapter 8)

CS440 Computer Networks 1 Neil Tang 12/01/2008.

Slides based on Carey Williamson’s: FTP & SMTP1 File Transfer Protocol (FTP) r FTP client contacts FTP server at port 21, specifying TCP as transport protocol.

Diameter Group Signaling Thursday, March 6 th, 2014 draft-ietf-diameter-group-signaling-03 Mark Jones, Marco Liebsch, Lionel Morand IETF 89 London, U.K.

CSE 4939 Alex Riordan Brian Pruitt-Goddard. Design an interactive source control application that works between an android phone and a project located.

Unit-6 Handling Sessions and Cookies. Concept of Session Session values are store in server side not in user’s machine. A session is available as long.

Draft-lemonade-imap-submit-00.txt “Forward without Download” Allow IMAP client to include previously- received message (or parts) in or as new message.

CSI WG / IETF741/12 Implementation of SeND/CGA and Extensions Beijing University of Posts and Telecommunications HUAWEI.

@Yuan Xue A special acknowledge goes to J.F Kurose and K.W. Ross Some of the slides used in this lecture are adapted from their.

© Janice Regan, CMPT 128, Jan 2007 CMPT 371 Data Communications and Networking HTTP 0.

Implementing POP3 and IMAP4 Using Dovecot AfNOG 2016 Scalable Internet Services (SS-E) Gaborone, Botswana Presented by Michuki Mwangi (Built on materials.

Spring 2006 CPE : Application Layer_ 1 Special Topics in Computer Engineering Application layer: Some of these Slides are Based on Slides.

August 1, 2008IETF 72 - Dublin, Ireland1 IMAP NOTIFY Arnt Gulbrandsen Alexey Melnikov Curtis King draft-ietf-lemonade-imap-notify-06.txt.

SIEVE Mail Filtering WG IETF 68, Prague WG Chairs: Cyrus Daboo, Alexey Melnikov Mailing List: Jabber:

Jonathan Rosenberg dynamicsoft

SMTP - Simple Mail Transfer Protocol POP - Post Office Protocol

Module Overview Installing and Configuring a Network Policy Server

KARDEX Drive EWM

Use case Diagram.

IMAP CONVERT Alexey Melnikov Stéphane Maes Ray Cromwell

Joe Clarke (presenting)

Joe Clarke (presenting)

Presentation transcript:

IMAP QUOTA extension draft-cridland-imap-quota-00 Dave Cridland Alexey Melnikov November 21, 2002

Description Quotas can be used to restrict clients for administrative reasons, but the QUOTA extension can also be used to indicate system limits and current usage levels to clients. Based on RFC 2087 by John G. Myers and tries to be backward compatible where possible.

Changes from RFC 2087 Defines a registry of resources (existing STORAGE, MESSAGES and a new one: MAILBOXES). Defines a registry of mappings and new mappings. List all resources that can be set on a quota root: SUPPORTEDQUOTARES response on GETQUOTA in addition to QUOTA=RES- CAPABILITY responses.

Changes from RFC 2087 (cont.) Adds an untagged QUOTAMAP response that describes a relationship between the quota root and the mailbox (mapping). Adds LISTQUOTA command that for a given quota root returns QUOTAMAP responses for all mailboxes accessible to the user that are governed by the quota root. Adds DELQUOTA command: The resource limit associated with the resource name is removed (or reset to the underlying system limit), without affecting other limits.

Changes from RFC 2087 (cont.) Adds DELETED-MESSAGES and DELETED-STORAGE STATUS data items. Minor clarifications

Open Issues Add OVERQUOTA NO response code Define server behavior when the current usage is bigger than the limit provided in SETQUOTA (Another response code?) Add GETUSAGE command? Add QUOTARESINFO command that returns human readable text, measurement units, etc.? Minor syntactical issues with SUPPORTEDQUOTARES untagged response (missing response, empty list of resources)

Open Issues (cont.) SETQUOTA/DELQUOTA: Should we be sending untagged QUOTA responses for all side effect changes? Specify that a quota root name must uniquely identify a mapping [if any] - namespaces collision. USER mapping - currently works with the logged in user only. Is it sufficient? Interaction with ACL and ACL2