From nobody Thu Oct 4 08:28:43 2018 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 34998130E48; Thu, 4 Oct 2018 08:28:41 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: ben@nostrum.com, dispatch@ietf.org, lflynn@amsl.com, dispatch-chairs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.85.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153866692120.4449.13614017152290737138.idtracker@ietfa.amsl.com> Date: Thu, 04 Oct 2018 08:28:41 -0700 Archived-At: Subject: [dispatch] dispatch - Update to a Meeting Session Request for IETF 103 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 15:28:41 -0000 An update to a meeting session request has just been submitted by Liz Flynn, on behalf of the dispatch working group. --------------------------------------------------------- Working Group Name: Dispatch Area Name: Applications and Real-Time Area Session Requester: Liz Flynn Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 80 Conflicts to Avoid: First Priority: jmap uta dmarc xrblock stir sipcore rtcweb rmcat payload netvc mmusic ecrit avtcore bfcpbis clue core doh extra cfrg secdispatch Second Priority: tram tsvwg tsvarea opsarea 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 Wed Oct 10 08:48:29 2018 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 4DC3D130F91; Wed, 10 Oct 2018 08:48:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 hdujqIo_DHEm; Wed, 10 Oct 2018 08:48:22 -0700 (PDT) Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 BEBDB130F72; Wed, 10 Oct 2018 08:48:21 -0700 (PDT) Received: by mail-lj1-x231.google.com with SMTP id y71-v6so5353840lje.9; Wed, 10 Oct 2018 08:48:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WMhWO6b5tfRecFVJMoG2nOZ3AuN+gSXdR/IoYHhqIB4=; b=So/O0JpPJphqdwQQfkS8emCUtm8lKQh+NFwhC2pMPOhpQFqqrn/yxe16BDeetR4h8g ofVNFbMyxZGEm8CJfY01sD5u4OJBhkCy9U0zd1+7JxBq/hYoxmB3MTOg7QA9oBI1H/yy tgd90+zoEJOtDu5XZ59JkQ71X+IjSs5ey2t4P1IQoV+s8BzfHK9K0A9PVE1I81JW5HEb HhwwnqlEBDuaHNFTzhCMEfu+2ZU3B8GHmTQqDmUvUARX1oYUqt994rXXdXyYPQZrdQSg DVWO8lJjY5KoO6ukep/SD2ghiqQfex+UjY8DnYHlEHQGAJgcDOUx70IAzd4iPxNqy/p8 boYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WMhWO6b5tfRecFVJMoG2nOZ3AuN+gSXdR/IoYHhqIB4=; b=jkRHjFnif1r7yq0Bir77vaDgrhF++G2PcpContBpxoBv+mUmpHe4wc9lmcT1zby2J8 cnRG6VTtAaR0qHsRlDKbRsrBHobejSZzRMqSG/BeGQcyBerx7+fjuD/rJxmW6sxPMy7M 4tBLeJOycpb/J+vvW+/hyTrdqqGHuvKv7tKsG275c3+FrdExazmsS3oSdYp7gNTwgbSR fXkUe9eopF0M/1ETaDQTpLxijNrJ8NX+2Urbu+ro6QijpA/GCyUHTQig7d1wbRJoaU+s DjjjKL90/9bQTZTHhULeWdhM+VSABSgLtVNQiGg8EZGURW3RiDbwL4ZdkemdxDPfSxgn VXkA== X-Gm-Message-State: ABuFfoj+EA75DUFzlbtQ5A55vFsJ9Ufzp4b7+R7QrkthEdrKs/XQ7dfF 4QL8mf37T4A2ZnVp7ZmhuMKfOOrJXQew+S4VpvGk6w== X-Google-Smtp-Source: ACcGV63bgGDsMgOipRXApW/d1VFnEIDmdiCjUFYdpgsyrJS6piJTvOq8qXFxobW5K+HeGM31gD6jKl2nvv6zpW+YgNs= X-Received: by 2002:a2e:5b17:: with SMTP id p23-v6mr21102333ljb.91.1539186499461; Wed, 10 Oct 2018 08:48:19 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Mary Barnes Date: Wed, 10 Oct 2018 10:48:07 -0500 Message-ID: To: DISPATCH , IETF ART Mailing List Cc: ART ADs , dispatch chairs Content-Type: multipart/alternative; boundary="0000000000008b29720577e1c81d" Archived-At: Subject: Re: [dispatch] Reminder: DISPATCH WG deadlines for IETF-103 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 15:48:27 -0000 --0000000000008b29720577e1c81d Content-Type: text/plain; charset="UTF-8" Hi all, Folks might have noticed that DISPATCH did not get the usual Monday morning slot due to a conflict with SECDISPATCH. We only received one request for a 5-10 min slot that we decided could be discussed in another WG. So, unless someone brings a solid topic forward by CoB on Friday, October 12th, we will be canceling the DISPATCH WG/ART area session for IETF-103. And, if you think you submitted something that we missed, please let us know ASAP. Regards, Mary On behalf of DISPATCH WG chairs and ART ADs On Mon, Sep 10, 2018 at 12:32 PM Mary Barnes wrote: > As a reminder the deadlines for the DISPATCH WG for IETF-103 are as > follows: > > - September 21, 2018. Cutoff date for IETF BoF submissions. > > > - September 28, 2018. Cutoff date to notify the chairs/DISPATCH WG of > plans to submit a proposal. > > > - October 5, 2018. Cutoff for charter proposals (i.e., problem > statement and proposed deliverables) for topics posted to the DISPATCH WG > mailing list. > > > - October 12, 2018. Announcement of topics that have been dispatched > for IETF-103 > > > - October 22, 2018. Draft submission deadline. > > > If you have a topic that you think might require an official BoF, please > contact the ADs ASAP. > > Additional information on the DISPATCH WG process can be found here (along > with the deadlines): > https://trac.ietf.org/trac/dispatch/wiki/WikiStart > > Regards, > Mary Barnes > DISPATCH WG tri-chair > > --0000000000008b29720577e1c81d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

Folks might have noticed that D= ISPATCH did not get the usual Monday morning slot due to a conflict with SE= CDISPATCH. We only received one request for a 5-10 min slot that we decided= could be discussed in another WG.=C2=A0 =C2=A0 So, unless someone brings a= solid topic forward by CoB on Friday, October 12th, we will be canceling t= he DISPATCH WG/ART area session for IETF-103.=C2=A0 And,=C2=A0 if you think= you submitted something that we missed, please let us know ASAP.=C2=A0=C2= =A0

Regards,
Mary
On behalf of= DISPATCH WG chairs and ART ADs

On Mon, Sep 10, 2018 at 12:32 PM Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
=
As a reminder the dea= dlines for the DISPATCH WG for IETF-103 are as follows:
    =
  • September 21, 2018. Cutoff date for IETF BoF submissions.
  • September 28, 2018. Cutoff date to notify the chairs/DI= SPATCH WG of plans to submit a proposal.
  • O= ctober 5, 2018. Cutoff for charter proposals (i.e., problem statement and p= roposed deliverables) for topics posted to the DISPATCH WG mailing list.
  • October 12, 2018. Announcement of topics tha= t have been dispatched for IETF-103=C2=A0
  • = October 22, 2018. Draft submission deadline.

I= f you have a topic that you think might require an official BoF, please con= tact the ADs ASAP.

Additional information on the D= ISPATCH WG process can be found here (along with the deadlines):=C2=A0
https://trac.ietf.org/trac/dispatch/wiki/WikiStart

Regards,
Mary Barnes
DISPATCH WG t= ri-chair

--0000000000008b29720577e1c81d-- From nobody Thu Oct 11 12:31:25 2018 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 42122130E63 for ; Thu, 11 Oct 2018 12:31:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.751 X-Spam-Level: X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=khk4K/uY; dkim=pass (1536-bit key) header.d=taugh.com header.b=rF1HonrE 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 my1Bh7gkZSfF for ; Thu, 11 Oct 2018 12:31:22 -0700 (PDT) Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 457F3124D68 for ; Thu, 11 Oct 2018 12:31:22 -0700 (PDT) Received: (qmail 22641 invoked from network); 11 Oct 2018 19:31:21 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=586f.5bbfa509.k1810; bh=mV1tYfrtZkh9z5xaxVADHexJfIXSlDNzhAxyQcdUNUo=; b=khk4K/uYfjjAO8oJUythViVO0w52czUsjr4DuDS8oezypTs1CFaSK5uPbhIesi5oRENhrBTBzJS90t+hxcKtjxma04V3OrF58+ybpqy7glYeb53ZPOweeMr2rq6gX3Z2F9AxPkzfQ8vHjS8VZ1wsnADg6QLtKW76t7vqYy+/tnpIl42wMkgKAkMNnKypuUlAvWgiz5nf6JBlT2j5mcEy8fTVo1tLcCnzub68U1jzCRogW6IPYqFY82yMSpv7DK/f DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=586f.5bbfa509.k1810; bh=mV1tYfrtZkh9z5xaxVADHexJfIXSlDNzhAxyQcdUNUo=; b=rF1HonrEmkyuKJ3c0n0vKeN5Xp3D9lsbQC0nLNPAK9LCm96xnPXyu9+kWurY3tRu5ZguVT1M+Iafz/2zDUMXSezwcph32h0X+fUzS9sYQKgapu80HYPRl2vNYHtBfGT04VxiZgodlvjUG2OiF+uuE6VHL9GKM4okBkdjBBjzRIXPJh5vswcBtJdLRIx/0bjR36H49idVzDxnDqto+A+yK7ZxVTEDiTDy1L1K0Io4GYpj4hpTSSJxy9n9+ttB05vl Received: from ary.local ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 11 Oct 2018 19:31:21 -0000 Received: by ary.local (Postfix, from userid 501) id 014CF2006CC435; Thu, 11 Oct 2018 15:31:20 -0400 (EDT) Date: 11 Oct 2018 15:31:20 -0400 Message-Id: <20181011193121.014CF2006CC435@ary.local> From: "John Levine" To: dispatch@ietf.org In-Reply-To: Organization: Taughannock Networks X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: Subject: Re: [dispatch] [art] Reminder: DISPATCH WG deadlines for IETF-103 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2018 19:31:23 -0000 In article you write: >unless someone brings a solid topic forward by CoB on Friday, October 12th, >we will be canceling the DISPATCH WG/ART area session for IETF-103. And, >if you think you submitted something that we missed, please let us know >ASAP. It would be nice to get some motion on draft-levine-appsarea-eaiauth but I realize this would be about a five minute session. From nobody Mon Oct 15 10:39:56 2018 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 EB8A3130DC1 for ; Mon, 15 Oct 2018 10:39:54 -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_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=2M0GGOC9; dkim=pass (1536-bit key) header.d=taugh.com header.b=jycm9iWZ 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 HvWUiNUctuqN for ; Mon, 15 Oct 2018 10:39:53 -0700 (PDT) Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 2249D12D7EA for ; Mon, 15 Oct 2018 10:39:53 -0700 (PDT) Received: (qmail 94501 invoked from network); 15 Oct 2018 17:39:52 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1711f.5bc4d0e8.k1810; bh=8v3PSp4nB6vGNLpVX9mqD4/ZVth3R5Ho7IZLxv6237c=; b=2M0GGOC9jldrf0bgoarz33Kls3E5noqnIvFyhirFn4jY4VpyXE/yhppYOa4dcWe/X2BnMM2zBE+c0p6nM78NW2YXcjMy6r0ZduUn71hGsoQuyBnTNu2syv5lr/eluCKreIDsH/0TO6TD8FOnBdyb6nPXTx/84nIr9XeiCeltU2PZR/XLoIyZvuRVrJc0EcpEBv2mKI8j+m/zxrAsLW/kF4lluo7ujfes9mFT0Q09kWBWHIEEkp5gwRe0YAwf4Icl DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1711f.5bc4d0e8.k1810; bh=8v3PSp4nB6vGNLpVX9mqD4/ZVth3R5Ho7IZLxv6237c=; b=jycm9iWZYiBMuASoP0lai3+0lh2QjwYAFHprL9R1vN7d3Hl5yDX7Tkt7viH8SsfzeCvzQUToAJ9eNlbJdbxC2nnCp+t3U9bkNxYz6AJJ+ffg3c0T40LMIRMDRlP2+57fdkfO2w54Lc1+Eyel5bfoubCz7L9ckccOTg2HoXkHOpm1Y9BUIKRXhb6AUxv3Qn1xWxmIOZwNHe2t4HcwKTte1Tto/JM1/c3a/gQMF6Z+mWUv9z8xmZRTZC6PgE6HP90h Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 15 Oct 2018 17:39:51 -0000 Date: 15 Oct 2018 13:39:51 -0400 Message-ID: From: "John R Levine" To: "Dispatch WG" In-Reply-To: <20181011193121.014CF2006CC435@ary.local> References: <20181011193121.014CF2006CC435@ary.local> User-Agent: Alpine 2.21 (OSX 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Archived-At: Subject: Re: [dispatch] [art] Reminder: DISPATCH WG deadlines for IETF-103 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2018 17:39:55 -0000 > It would be nice to get some motion on draft-levine-appsarea-eaiauth > but I realize this would be about a five minute session. I realize it's too late but I'd also like to do something about draft-seantek-mail-regexen, standard regular expressions for mail addresses. This came up in some EAI work and even for ordinary ASCII addresses, most of the regexes that people use to validate web forms are painfully wrong. Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly From nobody Fri Oct 19 12:01:49 2018 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 C033F131023; Fri, 19 Oct 2018 11:56:35 -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.87.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153997539577.6592.124468843123385339.idtracker@ietfa.amsl.com> Date: Fri, 19 Oct 2018 11:56:35 -0700 Archived-At: Subject: [dispatch] dispatch - Requested session has been scheduled for IETF 103 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.29 List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2018 18:56:44 -0000 Dear Mary Barnes, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. dispatch Session 1 (2:00 requested) Monday, 5 November 2018, Morning Session I 0900-1100 Room Name: Chitlada 2 size: 250 --------------------------------------------- Special Note: Joint with ARTAREA iCalendar: https://datatracker.ietf.org/meeting/103/sessions/dispatch.ics Request Information: --------------------------------------------------------- Working Group Name: Dispatch Area Name: Applications and Real-Time Area Session Requester: Mary Barnes Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 80 Conflicts to Avoid: First Priority: secdispatch cfrg extra doh core clue bfcpbis avtcore ecrit mmusic netvc payload rmcat rtcweb sipcore stir xrblock dmarc uta jmap Second Priority: tram tsvwg tsvarea opsarea 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. ---------------------------------------------------------