From nobody Mon Jun 6 00:00:42 2016 Return-Path: X-Original-To: apps-discuss@ietf.org Delivered-To: apps-discuss@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B7F3812B030; Mon, 6 Jun 2016 00:00:40 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Meeting Session Request Tool\"" To: X-Test-IDTracker: no X-IETF-IDTracker: 6.21.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160606070040.20834.65662.idtracker@ietfa.amsl.com> Date: Mon, 06 Jun 2016 00:00:40 -0700 Archived-At: Cc: appsawg-chairs@ietf.org, apps-discuss@ietf.org, aamelnikov@fastmail.fm Subject: [apps-discuss] appsawg - Not having a session at IETF 96 X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.17 List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2016 07:00:40 -0000 Murray Kucherawy, a chair of the appsawg working group, indicated that the appsawg working group does not plan to hold a session at IETF 96. This message was generated and sent by the IETF Meeting Session Request Tool. From nobody Thu Jun 9 09:33:45 2016 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E57F12D88A for ; Thu, 9 Jun 2016 09:33:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.602 X-Spam-Level: X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id opq7HcKTAZu9 for ; Thu, 9 Jun 2016 09:33:41 -0700 (PDT) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77D0E12D87C for ; Thu, 9 Jun 2016 09:33:40 -0700 (PDT) Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 732AF50A85 for ; Thu, 9 Jun 2016 12:33:39 -0400 (EDT) To: "apps-discuss@ietf.org" From: Sean Leonard Message-ID: <50acffcc-044f-f7a7-95ba-59f9282643c1@seantek.com> Date: Thu, 9 Jun 2016 09:34:08 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [apps-discuss] Regular Expressions for Internet Mail Identifiers (draft-seantek-mail-regexen) X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2016 16:33:43 -0000 Hi Apps-Discuss, Just wanted to bring this work to this mailing list's attention: Regular Expressions for Internet Mail Identifiers (draft-seantek-mail-regexen) Basically it is a proposed set of regular expressions for identifying and teasing out e-mail addresses and Message-IDs. It got some time at IETF95 and has been discussed on the dispatch@ list. Joe Hildebrand and Tony Hansen are working with me on the next iterations of the draft. Sean PS I am still a bit confused about the distinction between dispatch@ and apps-discuss@ at this point for getting practical work done. But based on the most recent directive e-mails, I am going with posting this (on the understanding that dispatch@ is not meant for "actual technical work"). -------- Forwarded Message -------- Subject: New Version Notification for draft-seantek-mail-regexen-00.txt Date: Mon, 21 Mar 2016 16:55:53 -0700 From: internet-drafts@ietf.org A new version of I-D, draft-seantek-mail-regexen-00.txt has been successfully submitted by Sean Leonard and posted to the IETF repository. Name: draft-seantek-mail-regexen Revision: 00 Title: Regular Expressions for Internet Mail Document date: 2016-03-21 Group: Individual Submission Pages: 24 URL: https://www.ietf.org/internet-drafts/draft-seantek-mail-regexen-00.txt Status: https://datatracker.ietf.org/doc/draft-seantek-mail-regexen/ Htmlized: https://tools.ietf.org/html/draft-seantek-mail-regexen-00 Abstract: Internet Mail identifiers are used ubiquitously throughout computing systems as building blocks of online identity. Unfortunately, incomplete understandings of the syntaxes of these identifiers has led to interoperability problems and poor user experiences. Many users use specific characters in their addresses that are not properly accepted on various systems. This document prescribes normative regular expression (regex) patterns for all Internet- connected systems to use when validating or parsing Internet Mail identifiers, with special attention to regular expressions that work with popular languages and platforms. From nobody Thu Jun 9 12:51:36 2016 Return-Path: X-Original-To: apps-discuss@ietfa.amsl.com Delivered-To: apps-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 092C912D989 for ; Thu, 9 Jun 2016 12:51:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01GJJ5BFSCQ7 for ; Thu, 9 Jun 2016 12:51:33 -0700 (PDT) Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AE0C12D696 for ; Thu, 9 Jun 2016 12:51:33 -0700 (PDT) Received: by mail-yw0-x22e.google.com with SMTP id g20so47691870ywb.0 for ; Thu, 09 Jun 2016 12:51:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=dVq4Gc4qhVun03fHlgLABWXya4Orq813sAUlXi8mHKs=; b=PTs/0j3wre1pgsLNrDKdSID1vOd3Wr6EL9WzmR0v8W32FxSobQ2NIBgLDxWkppw511 MaupnTbd484kmcsMXcDN/z21T5U/mchfs/Yg7dTiXIupqYPpfBCrFErsQTM4DLuhWeiu oVT/fXg1FhS01vgmfPsakeB1HR8QwlD4XUhB/cCXDXBnXRRrSPY64sJT4eVwG0Fmz2fz FpMcJ6drxfmHtvNxBB97z+MouG2maZUBYmrr8ITuZUJIJJXHlxCkPqXXh5xZsieuYjPt HJNfk/sKTKbVxSP0/eqx+W7uaRCfl/qL3I/6IP+trsZEj7f7plyx4jt64z2AY4InAuee +flA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=dVq4Gc4qhVun03fHlgLABWXya4Orq813sAUlXi8mHKs=; b=e59PUE6+4g32YQLmTZp6hUl6td27RH9vDTl7w9z36Zjo/2RodcWmNxAQeXXz3XEqZ0 E4QdtKHjIu0gQ4lBny6Itu5+Qa3yHxmk9kNZ8bBsqJA27VUjrp9GWTU6kecU23W7Y5E5 2tm5FSSypC/5dM6w67Rgfth2gYldS3yR0GJuXq8Md/IcoYU/jRA5/3ixfVUi1/y/uLsM 6Ou7koyxz3bZymRPVqBTR5fTV901vs0NsA4of4O0q2w3Jeh9QuW5bj/cryAtTu4GYGMY HtJDslWgcjKziDZYhc+CAbQgR+xrGNVX2nyGeVurYYp46sTaXNx6Sv7FRKHpZFcN1/fS d/pQ== X-Gm-Message-State: ALyK8tLRJd7dBqRa6jIC4xo9aNyglY6PwTgTPeIPX6YPm7l8bcwYNzpCbB7hM8NLJpbsqxZtmi8yj6GqgB187A== X-Received: by 10.129.98.130 with SMTP id w124mr6920536ywb.222.1465501892697; Thu, 09 Jun 2016 12:51:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.215.149 with HTTP; Thu, 9 Jun 2016 12:51:32 -0700 (PDT) From: "Murray S. Kucherawy" Date: Thu, 9 Jun 2016 12:51:32 -0700 Message-ID: To: Sean Leonard Content-Type: multipart/alternative; boundary=001a114707f8bb63310534ddbf03 Archived-At: Cc: "apps-discuss@ietf.org" Subject: [apps-discuss] dispatch vs. apps-discuss (was Re: Regular Expressions for Internet Mail Identifiers (draft-seantek-mail-regexen)) X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2016 19:51:35 -0000 --001a114707f8bb63310534ddbf03 Content-Type: text/plain; charset=UTF-8 On Thu, Jun 9, 2016 at 9:34 AM, Sean Leonard wrote: > > PS I am still a bit confused about the distinction between dispatch@ and > apps-discuss@ at this point for getting practical work done. But based on > the most recent directive e-mails, I am going with posting this (on the > understanding that dispatch@ is not meant for "actual technical work"). > As APPSAWG is nearing its end, this list is now the general ART discussion list. It's basically no longer a working group list but one for topics of general interest to the participants of the ART area. DISPATCH is for doing things under the charter of that working group, which is to say proposing work and, if there's sustained support for it, finding a home for that work. This post, which is basically "Hi, I have a draft, please read it and let me know what you think" belongs here. When the question becomes "How should we process this through the IETF (if at all)?", it becomes a candidate for DISPATCH. -MSK, co-chair of both --001a114707f8bb63310534ddbf03 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, Jun 9, 2016 at 9:34 AM, Sean Leonard <dev+ietf= @seantek.com> wrote:

PS I am still a bit confused about the distinction between dispatch@ and ap= ps-discuss@ at this point for getting practical work done. But based on the= most recent directive e-mails, I am going with posting this (on the unders= tanding that dispatch@ is not meant for "actual technical work").=

As APPSAWG is nearing its end, this li= st is now the general ART discussion list.=C2=A0 It's basically no long= er a working group list but one for topics of general interest to the parti= cipants of the ART area.

DISPATCH is for doing things und= er the charter of that working group, which is to say proposing work and, i= f there's sustained support for it, finding a home for that work.
This post, which is basically "Hi, I have a draft, please= read it and let me know what you think" belongs here.=C2=A0 When the = question becomes "How should we process this through the IETF (if at a= ll)?", it becomes a candidate for DISPATCH.

-MSK, co= -chair of both
--001a114707f8bb63310534ddbf03-- From nobody Sun Jun 12 02:41:16 2016 Return-Path: X-Original-To: apps-discuss@ietf.org Delivered-To: apps-discuss@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4D612D1B1; Sun, 12 Jun 2016 02:41:15 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.21.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160612094115.5491.82399.idtracker@ietfa.amsl.com> Date: Sun, 12 Jun 2016 02:41:15 -0700 Archived-At: Cc: apps-discuss@ietf.org Subject: [apps-discuss] I-D Action: draft-ietf-appsawg-file-scheme-11.txt X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.17 List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jun 2016 09:41:15 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the ART Area General Applications Working Group of the IETF. Title : The file URI Scheme Author : Matthew Kerwin Filename : draft-ietf-appsawg-file-scheme-11.txt Pages : 18 Date : 2016-06-12 Abstract: This document specifies the "file" Uniform Resource Identifier (URI) scheme, replacing the definition in RFC 1738. It defines a common syntax which is intended to interoperate across the broad spectrum of existing usages. At the same time it notes some other current practices around the use of file URIs. Note to Readers (To be removed by the RFC Editor) This draft should be discussed on the IETF Applications Area Working Group discussion list . The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-appsawg-file-scheme/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-appsawg-file-scheme-11 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-file-scheme-11 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sat Jun 25 09:51:08 2016 Return-Path: X-Original-To: apps-discuss@ietf.org Delivered-To: apps-discuss@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 16E5012D108; Sat, 25 Jun 2016 09:51:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.24.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20160625165107.17097.9800.idtracker@ietfa.amsl.com> Date: Sat, 25 Jun 2016 09:51:07 -0700 Archived-At: Cc: apps-discuss@ietf.org Subject: [apps-discuss] I-D Action: draft-ietf-appsawg-mdn-3798bis-08.txt X-BeenThere: apps-discuss@ietf.org X-Mailman-Version: 2.1.17 List-Id: General discussion of application-layer protocols List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jun 2016 16:51:07 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the ART Area General Applications Working Group of the IETF. Title : Message Disposition Notification Authors : Tony Hansen Alexey Melnikov Filename : draft-ietf-appsawg-mdn-3798bis-08.txt Pages : 35 Date : 2016-06-25 Abstract: This memo defines a MIME content-type that may be used by a mail user agent (MUA) or electronic mail gateway to report the disposition of a message after it has been successfully delivered to a recipient. This content-type is intended to be machine-processable. Additional message header fields are also defined to permit Message Disposition Notifications (MDNs) to be requested by the sender of a message. The purpose is to extend Internet Mail to support functionality often found in other messaging systems, such as X.400 and the proprietary "LAN-based" systems, and often referred to as "read receipts," "acknowledgements", or "receipt notifications." The intention is to do this while respecting privacy concerns, which have often been expressed when such functions have been discussed in the past. Because many messages are sent between the Internet and other messaging systems (such as X.400 or the proprietary "LAN-based" systems), the MDN protocol is designed to be useful in a multi- protocol messaging environment. To this end, the protocol described in this memo provides for the carriage of "foreign" addresses, in addition to those normally used in Internet Mail. Additional attributes may also be defined to support "tunneling" of foreign notifications through Internet Mail. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-appsawg-mdn-3798bis/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-appsawg-mdn-3798bis-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-mdn-3798bis-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/