From nobody Mon Oct 2 05:17:42 2017 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB3B01344EA for ; Mon, 2 Oct 2017 05:17:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.722 X-Spam-Level: X-Spam-Status: No, score=-0.722 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 IJWpyBGEDxGI for ; Mon, 2 Oct 2017 05:17:39 -0700 (PDT) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2768E1345DF for ; Mon, 2 Oct 2017 05:17:39 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9F66D20CD2; Mon, 2 Oct 2017 08:17:37 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute1.internal (MEProxy); Mon, 02 Oct 2017 08:17:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=7WnbfD 6CZnX4zS6Q78RXkomv+RnCTGxAM4ONXqgCQos=; b=V+//CLzpEY/TjJyRp3JP59 +s98A/2qBgkaR7DLqKXvzpD8z0TBoIOsb3cPR0uFE6P/vfFGIvVejYs6IrzDRy78 uz7FV6JP3BxBXb0Hrlkx7ZE0mp9U+g6Ef+rn5EUZgm5dRGu8VA1d5WvYvroWzv/o 0a4WAnkCu6k64bZEREor1bmIUeC8Gg+o1CQsdw3PNn/uezBNeP0EHNL2zHOjmZyW xiNNfLmYqOWaRU0b8YNo6XDWnubWGg0JOD3ASl9EvPAycfmyGzH1zQggJL3/kAl0 vBgZLK/apLWbpNl91qq4xJnOrcWEkRy/716h/bQig/5E5Uus2suCRDmQeRBOd1oQ == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 7754B95799; Mon, 2 Oct 2017 08:17:37 -0400 (EDT) Message-Id: <1506946657.1867996.1124819272.427835FD@webmail.messagingengine.com> From: Robert Stepanek To: "Dale R. Worley" Cc: dispatch@ietf.org, neilj@fastmailteam.com, brong@fastmailteam.com MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-6cb49228 Date: Mon, 02 Oct 2017 14:17:37 +0200 References: <87h8vm8dvo.fsf@hobgoblin.ariadne.com> In-Reply-To: <87h8vm8dvo.fsf@hobgoblin.ariadne.com> Archived-At: Subject: Re: [dispatch] Feedback requested: draft-jenkins-jscalendar X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 12:17:41 -0000 On Fri, Sep 29, 2017, at 03:58, Dale R. Worley wrote: > To what degree is this addressing actual > failures of iCal (e.g., where iCal is ambiguous) and to what degree is > it just *simpler* for the implementor? Two common pitfalls in iCalendar are embedded, custom timezones as well as time-span definitions that overlap daylight-savings time boundaries. JSCalendar addresses this by restricting timezones to the common IANA timezone definitions and requiring time-spans to be expressed by durations. In both cases, iCalendar per spec wasn't ambiguous, but in practice has shown to confuse many implementations about the intent of the calendar object creator. > to what degree does the simplicity of > JSCalendar simply push work back into the interface between the > calendaring system and the JSCalendar interface? Moving away from iCalendar format to JSON makes it actually simpler on both client and server implementations to handle the wire format. Feature-wise there isn't additional effort due to the data model, it's very much in line with iCalendar. > I suspect that in practice, semantic upward-compatibility from iCal will > be important. > You mention in section 1 item 3, "a conversion between > the data formats is not guaranteed to be completed without losing > semantic meaning". What exactly are the incompatibilities? In Cyrus IMAPd, we store calendar objects in iCalendar format on disk and serve them in JSCalendar format; compatibility with iCalendar is important to us. I also know of other vendors who implemented a draft version of JSCalendar to serve both formats with success. We take the liberty to be incompatible with iCalendar where it benefits users and allows richer semantics. Notable differences are the ability to define multiple owners for an event (versus a single ORGANIZER in iCalendar), the ability to localize all text properties (versus a single allowed SUMMARY in iCalendar), the ability to relate participants with locations and multi-location events (e.g. a meeting that has participants attending by video, audio and on-premises vs. a single LOCATION property in iCalendar). Probably we'll also propose to allow rich-text descriptions similar to HTML email bodies (versus plain-text only DESCRIPTION in iCalendar), but that's undecided, yet. Cheers, Robert From nobody Mon Oct 2 12:37:53 2017 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A4B813480E for ; Mon, 2 Oct 2017 12:37:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=shockey.us 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 qPJjUv8m3rhr for ; Mon, 2 Oct 2017 12:37:50 -0700 (PDT) Received: from qproxy3-pub.mail.unifiedlayer.com (qproxy3-pub.mail.unifiedlayer.com [67.222.38.20]) (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 227CF1347DC for ; Mon, 2 Oct 2017 12:37:50 -0700 (PDT) Received: from cmgw4 (unknown [10.0.90.85]) by qproxy3.mail.unifiedlayer.com (Postfix) with ESMTP id 00D1FD58CA for ; Mon, 2 Oct 2017 13:37:49 -0600 (MDT) Received: from box462.bluehost.com ([74.220.219.62]) by cmgw4 with id GjYl1w00Q1MNPNq01jYoXr; Mon, 02 Oct 2017 13:32:49 -0600 X-Authority-Analysis: v=2.2 cv=OZLoNlbY c=1 sm=1 tr=0 a=jTEj1adHphCQ5SwrTAOQMg==:117 a=jTEj1adHphCQ5SwrTAOQMg==:17 a=IkcTkHD0fZMA:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=02M-m0pO-4AA:10 a=jqBRFv0mrdUA:10 a=ZZnuYtJkoWoA:10 a=doUQZJtgAAAA:8 a=ll-iCDY8AAAA:8 a=M0OflfRGAAAA:8 a=9gU8epOxxBEsvSpJv-cA:9 a=QEXdDO2ut3YA:10 a=ivbTfD_dPm4A:10 a=d0-0EwFVFT64L02gzcZV:22 a=VpyrLIdO_Ztbr3SWPBuH:22 a=6yl0mh0s51TKORVA8GqK:22 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-transfer-encoding:Content-type:Mime-version:Message-ID: To:From:Subject:Date:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=ELqw6A7TYtP4epaIgVyp2hUvKWRtCOvXS/WpeL8eT2E=; b=jMn+eWPvFlW94q5xfanoy+e8C/ lOgkrhxiPaF6n8odAJLB9CvVernX5dPdyScZgXs4oiFCMjEWjC7msawhQbv2isVMVrMFjhGvU0ulA OEK+05lXhfarfnbEhpDhXvbCJ; Received: from pool-100-36-44-145.washdc.fios.verizon.net ([100.36.44.145]:58731 helo=[192.168.1.152]) by box462.bluehost.com with esmtpa (Exim 4.87) (envelope-from ) id 1dz6SL-0001l7-3j for dispatch@ietf.org; Mon, 02 Oct 2017 13:32:45 -0600 User-Agent: Microsoft-MacOutlook/f.26.0.170902 Date: Mon, 02 Oct 2017 15:32:43 -0400 From: Richard Shockey To: Message-ID: Thread-Topic: Eric Burger was just named CTO of the US FCC Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - box462.bluehost.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - shockey.us X-BWhitelist: no X-Source-IP: 100.36.44.145 X-Exim-ID: 1dz6SL-0001l7-3j X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: pool-100-36-44-145.washdc.fios.verizon.net ([192.168.1.152]) [100.36.44.145]:58731 X-Source-Auth: richard+shockey.us X-Email-Count: 2 X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NDYyLmJsdWVob3N0LmNvbQ== X-Local-Domain: yes Archived-At: Subject: [dispatch] Eric Burger was just named CTO of the US FCC X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 19:37:52 -0000 https://www.fcc.gov/document/chairman-pai-appoints-new-chief-technology-off= icer =E2=80=94=20 Richard Shockey Shockey Consulting LLC Chairman of the Board SIP Forum www.shockey.us www.sipforum.org richardshockey.us Skype-Linkedin-Facebook =E2=80=93Twitter rshockey101 PSTN +1 703-593-2683 =20 From nobody Tue Oct 3 16:38:11 2017 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D801331C2; Tue, 3 Oct 2017 16:38:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.298 X-Spam-Level: X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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, URIBL_BLOCKED=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 rklgIcGKOze2; Tue, 3 Oct 2017 16:38:08 -0700 (PDT) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (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 DC08A128D0D; Tue, 3 Oct 2017 16:38:07 -0700 (PDT) Received: by mail-qk0-x236.google.com with SMTP id u7so9372332qku.13; Tue, 03 Oct 2017 16:38:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=Om/u/TTLzrz3dcF44lhRjKn4Viqo4KpQi9N0VfhB8C0=; b=hGdrYGOU7sSsYxf9oXSXaBNcReUDXd7UUuFtBUj+rCnetvRbGuAER67PFRTVVCiof4 1Dvf6sMx1ail5rwT8O8GYI4a5zAK/iAX3bqJRxVF4b8rNhT5lb5t0AQ4AfY+5b3I4Jo8 PwUz92gFL6wt6D/j/YqNue1aKB1q1rvVZMnviId83F6yv6Zzp5HAvO3GLiR1AI8qDRvp 3mHyUnk894V2yDU8eVZqB4EapoynEWtAYqearIy25RkbDXw3IDUVavQI0Vs0kml54G18 bb0ClvpqXzjNi5Lrl5FwKlEk+/5YgKP2iNSsvDT02JBT3ZdfANNuv+FTt2uo2H7APlSD meaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=Om/u/TTLzrz3dcF44lhRjKn4Viqo4KpQi9N0VfhB8C0=; b=qb3XKEds+A1ZH4fU2g5bWl60o0urKbGx22aJVq8BV3Qqa9McRAiu4l0jZSk+PoieSR xLCsBKBgUY8jPYDOy+7zD3QPHnD29BDPE//RxqQ5UZ714LtM7cyvwIp5DZXVvRUg9cum Lx7u7EMrmTN8v9MyTeco8oWe1g4JyRdl4tCQyHjg15bI59LqKGQULKvqYq5OtQ+1AbGE 8q0sQo7HWYQ+2nB53Uvcj95C7niQsr7JNXbss8i48sgfBeROv/ltEIu5YetSIsvsSZQ/ U+GTOu2HWFy50xIUWChKz1iUwgEej6FrJIRdGPgaSRumA7Lhh118yFPjrouBfGsYBpg1 VARA== X-Gm-Message-State: AMCzsaXz8bjAWpgCaztPSWTADbhBPEg1I93H9XSpUnDf1ZvBfkVMhaOQ rDfvk0UlkGOXe2aguI2vzg7sNi9OetdoCKUl7JBtfg== X-Google-Smtp-Source: AOwi7QA+lxlyKz3ZPszKFIkMfeJ2K3sRydnbPnAt4qAyt9hS40P56bnhHbBxoZ9jMccuKJYjWxM+AeSD2fCy4Wdw4fk= X-Received: by 10.55.114.195 with SMTP id n186mr8689113qkc.319.1507073886811; Tue, 03 Oct 2017 16:38:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.32.202 with HTTP; Tue, 3 Oct 2017 16:38:06 -0700 (PDT) From: Mary Barnes Date: Tue, 3 Oct 2017 18:38:06 -0500 Message-ID: To: DISPATCH Cc: dispatch chairs , ART ADs Content-Type: multipart/alternative; boundary="001a114fe984ac7ab3055aacfbc6" Archived-At: Subject: [dispatch] Reminder: DISPATCH WG deadlines for IETF-100 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 23:38:09 -0000 --001a114fe984ac7ab3055aacfbc6 Content-Type: text/plain; charset="UTF-8" Hi all, As a reminder the deadlines for DISPATCH WG for IETF-100 are coming up: https://trac.ietf.org/trac/dispatch - Oct 9, 2017. Cutoff date to notify the chairs/DISPATCH WG of plans to submit a proposal. - Oct 15, 2017. Cutoff for charter proposals for topics. - Oct 20, 2017. Announcement of topics that have been dispatched for IETF-100. - Oct 30, 2017. Draft submission deadline. And, please remember to submit drafts with -dispatch in the name: e.g., draft-myname-dispatch-topic-xyz That makes it easier for us to make sure we're not missing anything. Regards, Mary --001a114fe984ac7ab3055aacfbc6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

As a reminder the deadlines for= DISPATCH WG for IETF-100 are coming up:
<= ul style=3D"color:rgb(0,0,0);font-size:13px">
  • Oct 9, 2017. Cutoff date to notify the chairs/= DISPATCH WG of plans to submit a proposal.
    • Oct 15, 2017. Cutoff for charter proposals for topics.
    <= ul style=3D"color:rgb(0,0,0);font-size:13px">
  • Oct 20, 2017. Announcement of topics that have been dispa= tched for IETF-100.
    • Oct 30, 2017. Draft = submission deadline.
    And, please remember to submit drafts with -di= spatch in the name: e.g., draft-myname-dispatch-topic-xyz
    =
    That makes it easier for us to make sure we're not missi= ng anything.=C2=A0

    Regards,
    Mary=C2=A0




    --001a114fe984ac7ab3055aacfbc6-- From nobody Tue Oct 3 17:50:10 2017 Return-Path: X-Original-To: dispatch@ietf.org Delivered-To: dispatch@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EDA6E13420B for ; Tue, 3 Oct 2017 17:50:08 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: X-Test-IDTracker: no X-IETF-IDTracker: 6.63.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150707820897.24020.2058556178820254119.idtracker@ietfa.amsl.com> Date: Tue, 03 Oct 2017 17:50:08 -0700 From: IETF Secretariat Archived-At: Subject: [dispatch] Milestones changed for dispatch WG X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2017 00:50:09 -0000 Added milestone "EMCAscript Media Type Updates to IESG for publication as Informational", due April 2018. URL: https://datatracker.ietf.org/wg/dispatch/about/ From nobody Sun Oct 8 06:49:33 2017 Return-Path: X-Original-To: dispatch@ietf.org Delivered-To: dispatch@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4942713463D; Sun, 8 Oct 2017 06:49:25 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: dispatch@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.63.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150747056524.22996.6512442369343550010@ietfa.amsl.com> Date: Sun, 08 Oct 2017 06:49:25 -0700 Archived-At: Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-00.txt X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 13:49:25 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dispatch WG of the IETF. Title : ECMAScript Media Types Updates Authors : Bradley Farias Matthew A. Miller Filename : draft-ietf-dispatch-javascript-mjs-00.txt Pages : 21 Date : 2017-10-08 Abstract: This document proposes updates to the ECMAScript media types, superseding the existing registrations for "application/javascript" and "text/javascript" by adding an additional extension and removing usage warnings. This document updates RFC4329, "Scripting Media Types". The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs-00 https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-00 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 Fri Oct 20 17:28:42 2017 Return-Path: X-Original-To: dispatch@ietf.org Delivered-To: dispatch@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 751C3134515; Fri, 20 Oct 2017 17:24:23 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: ben@nostrum.com, dispatch@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150854546347.20809.16805416478293499014.idtracker@ietfa.amsl.com> Date: Fri, 20 Oct 2017 17:24:23 -0700 Archived-At: Subject: [dispatch] dispatch - Requested session has been scheduled for IETF 100 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 00:24:23 -0000 Dear Alexey Melnikov, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. dispatch Session 1 (1:30:00) Monday, Morning Session I 0930-1200 Room Name: Collyer size: 250 --------------------------------------------- Special Note: 0930-1100 Joint with ARTAREA Request Information: --------------------------------------------------------- Working Group Name: Dispatch Area Name: Applications and Real-Time Area Session Requester: Alexey Melnikov Number of Sessions: 1 Length of Session(s): 1.5 Hours Number of Attendees: 100 Conflicts to Avoid: First Priority: dmarc uta jmap xrblock webpush stir sipcore rtcweb rmcat payload netvc mmusic insipid ecrit avtcore bfcpbis clue core dcrup doh extra Second Priority: tram tsvwg tsvarea opsarea lmap People who must be present: Alexey Melnikov Mary Barnes Adam Roach Ben Campbell Cullen Jennings Murray Kucherawy Resources Requested: Special Requests: Please schedule in the 1st slot on Monday morning, list the meeting as coupled with ARTAREA, and avoid the same kind of conflicts with other area meetings and any Bofs and potential new ART WGs. --------------------------------------------------------- From nobody Mon Oct 30 15:24:38 2017 Return-Path: X-Original-To: dispatch@ietf.org Delivered-To: dispatch@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9274A13F43E; Mon, 30 Oct 2017 15:24:35 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: dispatch@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150940227553.28403.15976208430752936836@ietfa.amsl.com> Date: Mon, 30 Oct 2017 15:24:35 -0700 Archived-At: Subject: [dispatch] I-D Action: draft-ietf-dispatch-javascript-mjs-01.txt X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2017 22:24:35 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dispatch WG of the IETF. Title : ECMAScript Media Types Updates Authors : Bradley Farias Matthew A. Miller Filename : draft-ietf-dispatch-javascript-mjs-01.txt Pages : 21 Date : 2017-10-30 Abstract: This document proposes updates to the ECMAScript media types, superseding the existing registrations for "application/javascript" and "text/javascript" by adding an additional extension and removing usage warnings. This document updates RFC4329, "Scripting Media Types". The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dispatch-javascript-mjs/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dispatch-javascript-mjs-01 https://datatracker.ietf.org/doc/html/draft-ietf-dispatch-javascript-mjs-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dispatch-javascript-mjs-01 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 Tue Oct 31 11:49:22 2017 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 804A613F5BD for ; Tue, 31 Oct 2017 11:49:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.88 X-Spam-Level: X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 goISVlritqul for ; Tue, 31 Oct 2017 11:49:18 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 ACF1913F4C1 for ; Tue, 31 Oct 2017 11:49:18 -0700 (PDT) Received: from [10.0.1.82] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v9VInGjj066705 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 31 Oct 2017 13:49:16 -0500 (CDT) (envelope-from ben@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.82] From: Ben Campbell Content-Type: multipart/signed; boundary="Apple-Mail=_82169D06-B181-4993-A641-59EB1FEABD55"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Message-Id: <25B9F35E-BAE3-42A5-8621-5664246AE2E7@nostrum.com> Date: Tue, 31 Oct 2017 13:47:56 -0500 Cc: Russ Housley To: dispatch@ietf.org X-Mailer: Apple Mail (2.3445.1.7) Archived-At: Subject: [dispatch] E2E Secure Messaging for SIP/SIMPLE X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2017 18:49:20 -0000 --Apple-Mail=_82169D06-B181-4993-A641-59EB1FEABD55 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 (strictly as an individual) Hi everyone, Russ and I submitted a draft [1] on the use of S/MIME for the SIP = MESSAGE method and for MSRP. It mainly offers clarifications of the = S/MIME guidance in RFCs 3261, 3428, and 4975, but it also makes a few = updates. The main use case we have in mind is for where organizations want to = send secure notifications to their users. For example, financial = organizations send transaction notices, organizations send password = update notices, 2FA notices, etc. Much of that is currently done over = various mobile messaging systems (SMS, etc). Most of that is done with = no e2e authentication or integrity protection. We=E2=80=99d like to = enable at least end-to-end signed messaging for SIP based mobile = messaging systems. We would appreciate it if people would take a look, and send your = comments. [1] https://tools.ietf.org/html/draft-campbell-sip-messaging-smime-00 Thanks! Ben. --Apple-Mail=_82169D06-B181-4993-A641-59EB1FEABD55 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAln4xVwACgkQgFZKbJXz 1A1UdQ//cwjWzr1nREreeVgtp5rXsvIDjsXptU6/fnwXdbhloreCEi486tjFfX/2 z7xCLiBCWAN7TssFIDYvH3o4AT5hvtQEpsykAhfxJpXbSu4BB2kso6PnQV4BE7Du EdhfktaSuGzxKhxnY0JV0/6PQZA7kvb9+bdtYn5zeu5YHWz/DgKAhLQXalcMItzT JL6q6nOP5EO0LjW6iyhjvHWMJTzC8VHr1yo9vBxb2EWxQhPUUDcLeNIdQKH879lb sH/JTKhEEXBC4dlwZYeWci1u4FpFVQoNXl5N5hOQ7XnxJvJOrtRsETP7Pup7G0cB NsnblVxcodTMoSUu8owvfqZwOvZENNgqpyyXLAtlaLImCVDrQsXLcgLHAHhCzfWK K75escAKI/vXRs0kgxNVLKGtWVtjUowR+6Qk9mfEmNR9yRDTVJQJ6rNmrAZmh4GQ invP3ZNmqdWNzHUC7bXskItS0Y7qQ2ahEk9llaJvCkOegG6mHx9iKVZE4RT0XCSr Cu2INewtKNt51YIN1Z6NOGCU0ndgUDFAqg84/rPvB0kR2HNFB2860Y0HZ1ura0pT 3QZTwQR8WbtQS+PAFSdSO/8Px3mUn5qIlm0pKceGD1+o0pO92XS0TIJiQv3qFDTm VxYt13eOlQGblQIf47AuS9eF0TTZTUo8yGdVVe5Ns7gBS6md9aA= =+pNv -----END PGP SIGNATURE----- --Apple-Mail=_82169D06-B181-4993-A641-59EB1FEABD55--