From nobody Sat Sep 3 03:05:58 2016 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 025BF12B03D for ; Sat, 3 Sep 2016 03:05:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.002 X-Spam-Level: X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=andreasschulze.de 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 AA0CONEA8QzK for ; Sat, 3 Sep 2016 03:05:55 -0700 (PDT) Received: from mail.somaf.de (mail.somaf.de [IPv6:2001:a60:f0b4:e503:2cdb:beff:feaa:880b]) (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 4DA24126D74 for ; Sat, 3 Sep 2016 03:05:54 -0700 (PDT) Received: from andreasschulze.de (andreasschulze.de [IPv6:2001:a60:f0b4:e503:d86e:8dce:a73e:2fec]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: sca@andreasschulze.de) by mail.somaf.de (Postfix) with ESMTPSA id 3sRBT92FjVzDdy for ; Sat, 3 Sep 2016 12:05:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=andreasschulze.de; s=ybz; t=1472897149; bh=JEhQQ2fAbRGRQ4HQSbU+afS9eI5HLzz4kYY2+XJ4Coc=; h=Date:From:To:Subject; b=GfZ0o87QYDUsl6xp62VR4bUg+dUnlAZd4wpWul4uOvHigvHmdaMmR/bxWMmryG18M ZZnTNKG83YvL4a7nYPCs2D6aqNDwp8NkHc/0gHPJNIEJ6S3HnMh1yuJjg0OVFbtrjs FlkhF3xKKIeNYfSVuZFrtaIqJVQ5TgX0NBNW8RF2/i8L9l82A2nIeLJO3w4cKP8bg0 LzqaVUVCY8qV14w8fLtc/WVtpsDSBWvOxw4gLAs2k3K3xTA23FjRx5nTFPebD+2WbE PFt1fKIb3ywLRiPzAy+qlLdw8nHYHFntcsr6KZD0yGoJsXCyF9JwCFEWI+kNKMlV85 TN6IgnYKacpWA== Received: from dimos.somaf.de (dimos.somaf.de [2001:a60:f0b4:e502::152]) by andreasschulze.de (Horde Framework) with HTTPS; Sat, 03 Sep 2016 12:05:47 +0200 Date: Sat, 03 Sep 2016 12:05:47 +0200 Message-ID: <20160903120547.Horde.PRnauL8i58D78rC0HsAvclx@andreasschulze.de> From: "A. Schulze" To: dispatch@ietf.org User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Archived-At: Subject: [dispatch] implementing draft-bhjl-x509-srv-02 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2016 10:05:57 -0000 hello, I like to announce we're implementing a certificate lookup system described in RFC 4387 we also plan to adopt draft-bhjl-x509-srv-02 Andreas From nobody Thu Sep 8 01:19:06 2016 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 B889C12B20F for ; Thu, 8 Sep 2016 01:19:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.126 X-Spam-Level: X-Spam-Status: No, score=-4.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 HOHark3jOk12 for ; Thu, 8 Sep 2016 01:19:03 -0700 (PDT) Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 170ED12B19A for ; Thu, 8 Sep 2016 01:19:03 -0700 (PDT) Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 580BA40469 for ; Thu, 8 Sep 2016 10:19:01 +0200 (CEST) Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.63]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 2D19F1A00CC for ; Thu, 8 Sep 2016 10:19:01 +0200 (CEST) Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM6E.corporate.adroot.infra.ftgroup ([fe80::f5a7:eab1:c095:d9ec%18]) with mapi id 14.03.0301.000; Thu, 8 Sep 2016 10:19:01 +0200 From: To: "dispatch@ietf.org" Thread-Topic: New version of draft-mohali-dispatch-originating-cdiv-parameter-01 Thread-Index: AdIJqLvCApqapoplQoGK3CSoyRI3UQ== Date: Thu, 8 Sep 2016 08:19:00 +0000 Message-ID: <15443_1473322741_57D11EF5_15443_4367_8_8B970F90C584EA4E97D5BAAC9172DBB81AAC3B2B@OPEXCLILMA4.corporate.adroot.infra.ftgroup> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.3] Content-Type: multipart/alternative; boundary="_000_8B970F90C584EA4E97D5BAAC9172DBB81AAC3B2BOPEXCLILMA4corp_" MIME-Version: 1.0 Archived-At: Subject: [dispatch] New version of draft-mohali-dispatch-originating-cdiv-parameter-01 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2016 08:19:05 -0000 --_000_8B970F90C584EA4E97D5BAAC9172DBB81AAC3B2BOPEXCLILMA4corp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi folks, Here is a new version (-01) of draft-mohali-dispatch-originating-cdiv-par= ameter "P-Served-User Header Field Parameter for Originating CDIV session c= ase in Session Initiation Protocol (SIP)". The purpose of this draft is to register a SIP parameter defined in 3GPP fo= r the P-Served-User header field defined as per RFC5502. In this new version: - incorrect statements are corrected - some text has been improved for a better understanding URL: https://www.ietf.org/internet-drafts/draft-mohali-dispatch-= originating-cdiv-parameter-01.txt Diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-mohali-dispatch-o= riginating-cdiv-parameter-01 Comments are welcomed! Best Regards, Marianne Mohali ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. --_000_8B970F90C584EA4E97D5BAAC9172DBB81AAC3B2BOPEXCLILMA4corp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi folks,<= /p>

 

Here is a new version (-01) = of   draft-mohali-dispatch-originating-cdiv-parameter "P-Ser= ved-User Header Field Parameter for Originating CDIV session case in Sessio= n Initiation Protocol (SIP)".

The purpose of this draft is= to register a SIP parameter defined in 3GPP for the P-Served-User header f= ield defined as per RFC5502.

 

In this new version:

- incorrect statements are c= orrected

- some text has been improve= d for a better understanding

 

URL:    =         https://www.ietf.org/internet-drafts/draft-mohali= -dispatch-originating-cdiv-parameter-01.txt=

Diff:    = ;       https://www.ietf.org/rfcdiff?url2=3Ddraft-mohali-dispatch-o= riginating-cdiv-parameter-01

 

Comments are welcomed!<= /o:p>

 

Best Regards,

Marianne Mohali

 

______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
--_000_8B970F90C584EA4E97D5BAAC9172DBB81AAC3B2BOPEXCLILMA4corp_-- From nobody Thu Sep 8 14:56:21 2016 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 0D6DD12B0C6 for ; Thu, 8 Sep 2016 14:56:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.934 X-Spam-Level: X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 tS2m5Y1nCyYs for ; Thu, 8 Sep 2016 14:56:17 -0700 (PDT) Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (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 9E04812B00B for ; Thu, 8 Sep 2016 14:56:17 -0700 (PDT) Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-01v.sys.comcast.net with SMTP id i7Gvbog9GTaLwi7Iublhnk; Thu, 08 Sep 2016 21:56:16 +0000 Received: from hobgoblin.ariadne.com ([73.100.16.189]) by resomta-ch2-20v.sys.comcast.net with SMTP id i7ItbdGHPtzqti7IuboJLi; Thu, 08 Sep 2016 21:56:16 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u88LuFQ0015613 for ; Thu, 8 Sep 2016 17:56:15 -0400 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u88LuFJt015610; Thu, 8 Sep 2016 17:56:15 -0400 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: dispatch@ietf.org Sender: worley@ariadne.com (Dale R. Worley) Date: Thu, 08 Sep 2016 17:56:14 -0400 Message-ID: <87pooevywx.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfGat9V0+uoBfzqln3U8cYPhQqZOVdrOJcsRWnKUxguVQzcvv7sWQPY6eFlikTeP/32aM8n0A1nVyBIDW+ZKOOxGJge/8n+3F48IRIS0W7gfVRkhdr1+D Rl6R4/DhiF0yWKM9gEspJobPyAtrVoGDVYU4FpBuyUnrpbIcBZ9NQxcsr2R7EEYtqMLBlbSizr86NA== Archived-At: Subject: [dispatch] How to construct a finite state machine to select an alerting signal X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2016 21:56:19 -0000 RFC 7462 defines a series of "alert" URNs that can be used in the SIP Alert-Info header. When a UA receives an INVITE or a provisional response to an INVITE, the UA should process the "alert" URNs to determine which signal (ring tone or ringback tone) to present to the user. RFC 7462 provides normative constraints on the UA's processing of the URNs. It also provides a non-normative algorithm that a UA can use which satisfies the constraints. But the algorithm in RFC 7462 is complicated and we know of no implementations. I've worked out how to construct a finite state machine to process the 'alert' URNs in an Alert-Info header to select one of the alerting signals of a UA. Once you fix the set of signals and their meanings (the URNs that the signal indicates), there's an algorithm to construct the FSM, and it ensures that FSM satisfies the rules in RFC 7462. I've written a draft to describe the process in detail. The draft also points to an implementation of the algorithm in Python, so people can try out this method and see how it works for them. I believe that this draft (or something very much like it) is necessary and sufficient to make RFC 7462 usable in practice. I'd like to hear any feedback you have. Dale Name: draft-worley-alert-info-fsm Revision: 03 Title: A Simpler Method for Processing Alert-Info URNs Document date: 2016-09-08 Group: Individual Submission Pages: 36 URL: https://www.ietf.org/internet-drafts/draft-worley-alert-info-fsm-03.txt Status: https://datatracker.ietf.org/doc/draft-worley-alert-info-fsm/ Htmlized: https://tools.ietf.org/html/draft-worley-alert-info-fsm-03 Diff: https://www.ietf.org/rfcdiff?url2=draft-worley-alert-info-fsm-03 Abstract: The "alert" namespace of uniform resource names (URNs) can be used in the Alert-Info header field of Session Initiation Protocol (SIP) requests and responses to inform a VoIP telephone (user agent) of the characteristics of the call that the user agent has originated or terminated. Based on the URNs in the Alert-Info header field, the user agent must select an the best available signal to present to its user to indicate the characteristics of the call. This document describes a method by which a user agent's designer can, based on the user agent's signals and their meanings, constructing a finite state machine (FSM) to process the URNs to select a signal in a way that obeys the restrictions given in the definition of the "alert" URN namespace. In many situations, the resulting FSM is simpler and faster than the previously described selection algorithm. From nobody Fri Sep 9 08:34:20 2016 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 BA08B12B296 for ; Fri, 9 Sep 2016 08:23:39 -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 e9F3ys8bDl4W for ; Fri, 9 Sep 2016 08:23:31 -0700 (PDT) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 CF44212B4CA for ; Fri, 9 Sep 2016 08:16:17 -0700 (PDT) Received: by mail-lf0-x22a.google.com with SMTP id u14so46549632lfd.1 for ; Fri, 09 Sep 2016 08:16:17 -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; bh=tdp/KuxC9vUqv2TTjJZM9xAI6IaX1gTZV+BjbZwSk5M=; b=rStvGUczWvyJmBNX5F0JGwxrBeY68TrNh05SOJr0edGvmHXYuQz367tHDGoozyId06 fDBhVF/wCCO1vKDXlbWf1hpQyBzpBmY7uwWpSPYU+fr9H2nqe56sCFR0aOlRxYWiheu/ YlUKwfogwnAlIXLolx8n8fW2IPmSlYo7gn1R253V1tNdxtbLgRbvtQhJxnFinc16D+L3 qFREQOppykzKdXIvLTJQQSDZlPSPY+tMst+tZtAHBOOR1EkuovBFOl5pOqUMftv732H7 ohrlMmbtEBaCLFdjtlf9w6Sz6MUTvH4wyL3XC0Quo/k4seb2h9/ouazFNm5eDjEGfLS8 9bmw== 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; bh=tdp/KuxC9vUqv2TTjJZM9xAI6IaX1gTZV+BjbZwSk5M=; b=IFYLQhTXqGOI0pUu/tgZmPIe3Eb8vQPN/WQz5Frdz7+DsJm80X3n4FrlGMje59+TJE YYe25n/eYsOMohHaDOqvQOtJqN5f8mTHyDiscLTLK8Dc9h7rMjNj1Eg5BWoJkvBmNa/n z8FUOUmEj9q/umRUrJlaREGUtGe0HknhEHE0ZEIczEOAcczbzE1XTfUVFsklXcPOnom5 hNdXBKOnIQ0Dcyn7C0jNRYW3Vn63W5uQE6OyOyudywRl1mZd6wiRufG0GjolU5vTfQbP ALr4KRbwxaIOQ3jwxGCbnhHOlqm3dz0pwEXWpP1HJzkFfsA9HFSDrHBSX5CKGO/9Uwle rnDQ== X-Gm-Message-State: AE9vXwPM+J6vPn7sHcGjlJN4/Vn6OtwIXK7HBtA3UXibdUmwr+OPbEea7rakW9F0StO70UOB2ih2Vlj5hra//A== X-Received: by 10.25.169.213 with SMTP id s204mr1223893lfe.57.1473434175690; Fri, 09 Sep 2016 08:16:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.183.8 with HTTP; Fri, 9 Sep 2016 08:16:15 -0700 (PDT) From: "Murray S. Kucherawy" Date: Fri, 9 Sep 2016 08:16:15 -0700 Message-ID: To: dispatch@ietf.org Content-Type: multipart/alternative; boundary=001a114027aaa45d87053c14a03b Archived-At: Subject: [dispatch] Reminder: Deadlines for IETF-97 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2016 15:23:39 -0000 --001a114027aaa45d87053c14a03b Content-Type: text/plain; charset=UTF-8 ---------- Forwarded message ---------- From: Mary Barnes Date: Tue, Aug 2, 2016 at 7:07 AM Subject: [dispatch] Deadlines for IETF-97 To: DISPATCH Cc: "dispatch-chairs@tools.ietf.org" , ART ADs Hi all, The wiki has been updated with the dates for IETF-97 and topics from IETF-96: https://trac.tools.ietf.org/wg/dispatch/trac/wiki The dates are as follows: - October 3, 2016. Cutoff date to notify the chairs/DISPATCH WG of plans to submit a proposal. - October 10, 2016. Cutoff for charter proposals for topics. - October 17, 2016. Announcement of topics that have been dispatched for IETF-97. - October 31, 2016. Draft deadline. As a reminder, it's extremely helpful if folks would use the usual draft naming convention of including the WG name (i.e., - dispatch) in the document name. That makes it a whole lot easier for us to make sure we're not missing documents and to find links to the docs for the wiki, minutes, etc. Regards, Mary. _______________________________________________ dispatch mailing list dispatch@ietf.org https://www.ietf.org/mailman/listinfo/dispatch --001a114027aaa45d87053c14a03b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

---------- Forwarded messag= e ----------
From: Mary Barnes <mary.ietf.barn= es@gmail.com>
Date: Tue, Aug 2, 2016 at 7:07 AM
Subject= : [dispatch] Deadlines for IETF-97
To: DISPATCH <dispatch@ietf.org>
Cc: "dispatch-chairs@tools.ietf.org" <= ;dispatch-chairs@tools.ie= tf.org>, ART ADs <art-ads@iet= f.org>


Hi all,

The wi= ki has been updated with the dates for IETF-97 and topics from IETF-96:
https://trac.tools.ietf.org/wg/dispatch/trac/wiki
<= /div>

The dates are as follows:
  • October 3, 2016. Cutoff date to notify the chairs/DI= SPATCH WG of plans to submit a proposal.
  • October 10, 2016. Cutoff for charter proposals for topics.=
  • October 17, 2016. Announcement of topics that have been dispatche= d for IETF-97.
  • October 31, 2016. Draft deadline.
As a reminder, it's extremely helpful if folks would use the = usual draft naming convention of including the WG name (i.e., - dispatch) i= n the document name. That makes it a whole lot easier for us to make sure w= e're not missing documents and to find links to the docs for the wiki, = minutes, etc.

Regards,
Mary.=C2=A0=

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch


--001a114027aaa45d87053c14a03b-- From nobody Fri Sep 9 08:37:53 2016 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 3C50E12B2C5 for ; Fri, 9 Sep 2016 08:37:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_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 d93maUK0VUR3 for ; Fri, 9 Sep 2016 08:37:49 -0700 (PDT) Received: from smtp72.iad3a.emailsrvr.com (smtp72.iad3a.emailsrvr.com [173.203.187.72]) (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 0663612B3E0 for ; Fri, 9 Sep 2016 08:30:50 -0700 (PDT) Received: from smtp10.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp10.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 4B30760284; Fri, 9 Sep 2016 11:30:47 -0400 (EDT) X-Auth-ID: fluffy@iii.ca Received: by smtp10.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id A61F660115; Fri, 9 Sep 2016 11:30:46 -0400 (EDT) X-Sender-Id: fluffy@iii.ca Received: from [192.168.4.100] ([UNAVAILABLE]. [128.107.241.184]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.7); Fri, 09 Sep 2016 11:30:47 -0400 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Cullen Jennings In-Reply-To: Date: Fri, 9 Sep 2016 09:30:45 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Mary Barnes X-Mailer: Apple Mail (2.3124) Archived-At: Cc: "dispatch-chairs@tools.ietf.org" , ART ADs , DISPATCH Subject: Re: [dispatch] Deadlines for IETF-97 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2016 15:37:51 -0000 Just reminding people deadlines are coming up .... Please note the IETF = BOF deadline is Sept 30 which is before the dispatch dates.=20 > On Aug 2, 2016, at 8:07 AM, Mary Barnes = wrote: >=20 > Hi all, >=20 > The wiki has been updated with the dates for IETF-97 and topics from = IETF-96: > https://trac.tools.ietf.org/wg/dispatch/trac/wiki >=20 > The dates are as follows: > =E2=80=A2 October 3, 2016. Cutoff date to notify the = chairs/DISPATCH WG of plans to submit a proposal. > =E2=80=A2 October 10, 2016. Cutoff for charter proposals for = topics. > =E2=80=A2 October 17, 2016. Announcement of topics that have = been dispatched for IETF-97. > =E2=80=A2 October 31, 2016. Draft deadline. > As a reminder, it's extremely helpful if folks would use the usual = draft naming convention of including the WG name (i.e., - dispatch) in = the document name. That makes it a whole lot easier for us to make sure = we're not missing documents and to find links to the docs for the wiki, = minutes, etc. >=20 > Regards, > Mary.=20 > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch From nobody Mon Sep 12 13:38:24 2016 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 DE5ED12B078 for ; Mon, 12 Sep 2016 13:38:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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 RpVyuioe4Dzr for ; Mon, 12 Sep 2016 13:38:19 -0700 (PDT) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B71212B10D for ; Mon, 12 Sep 2016 13:38:18 -0700 (PDT) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d28 with ME id ikeF1t00W17Lgi403keGaR; Mon, 12 Sep 2016 22:38:17 +0200 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Mon, 12 Sep 2016 22:38:17 +0200 X-ME-IP: 92.170.5.52 To: dispatch@ietf.org From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: <17a8c5aa-c0c6-2153-dc91-a1b0403ae6fd@trigofacile.com> Date: Mon, 12 Sep 2016 22:38:15 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: [dispatch] Review of two drafts refreshing the use of TLS with NNTP X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2016 20:38:23 -0000 Hi all, As you may already know, TLS-level compression will be removed from the next version of the TLS protocol (currently named TLS 1.3) whereas NNTP was relying on this feature (as we can read it in the abstract of RFC 4642, dealing with the use of TLS with NNTP). In order to refresh RFC 4642 to be consistent with the latest published RFCs about TLS, I suggest two drafts: - one that defines an NNTP extension to allow a connection to be compressed (inspired from the IMAP COMPRESS command defined in RFC 4978): https://tools.ietf.org/html/draft-murchison-nntp-compress-05 - one that toilets all obsolete TLS-related stuff, in discrepancy with latest RFCs and UTA BCP 195: https://tools.ietf.org/html/draft-elie-nntp-tls-recommendations-01 In case some of you are interested and have time to review these drafts, do not hesitate to send your comments. For your information, Alexey is considering AD-sponsoring them. IETF Last Call has been sent for draft-murchison-nntp-compress-05 today, and draft-elie-nntp-tls-recommendations-01 will probably be also reviewed by people in the UTA WG. P.-S.: I've just seen that RFC 6648 deprecates the use of the "X-" prefix in application protocols. I bet it should be taken into account in the examples of Section 2.1 and 2.2.3 (X-SHRINK) as well as in Section 7.1 of draft-murchison-nntp-compress-05. Thanks beforehand for your valuable comments about these drafts. -- Julien ÉLIE « C'est une liqueur de grain distillée en Calédonie. » (Astérix) From nobody Tue Sep 13 07:33:51 2016 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 7C4E212B633 for ; Tue, 13 Sep 2016 07:33:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 3LyhjVOU_Uiz for ; Tue, 13 Sep 2016 07:33:45 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B39C12B4EF for ; Tue, 13 Sep 2016 06:54:41 -0700 (PDT) Received: (qmail 4721 invoked from network); 13 Sep 2016 13:54:39 -0000 Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 13 Sep 2016 13:54:39 -0000 Date: 13 Sep 2016 13:54:17 -0000 Message-ID: <20160913135417.53163.qmail@ary.lan> From: "John Levine" To: dispatch@ietf.org In-Reply-To: <17a8c5aa-c0c6-2153-dc91-a1b0403ae6fd@trigofacile.com> Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: Subject: Re: [dispatch] Review of two drafts refreshing the use of TLS with NNTP X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2016 14:33:49 -0000 >- one that defines an NNTP extension to allow a connection to be >compressed (inspired from the IMAP COMPRESS command defined in RFC 4978): > https://tools.ietf.org/html/draft-murchison-nntp-compress-05 > >- one that toilets all obsolete TLS-related stuff, in discrepancy with >latest RFCs and UTA BCP 195: > https://tools.ietf.org/html/draft-elie-nntp-tls-recommendations-01 > > >In case some of you are interested and have time to review these drafts, >do not hesitate to send your comments. I've looked at them, and they seem fine to me. Section 3 in the Murchison draft, offering advice on how to tune your compression, strikes me as premature overoptimization, but since it only affects compression efficiency, not interop, it's not very important. R's, John From nobody Tue Sep 13 12:28:52 2016 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 DE3EB12B05C for ; Tue, 13 Sep 2016 12:28:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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 1o5KuBsJGDBl for ; Tue, 13 Sep 2016 12:28:48 -0700 (PDT) Received: from smtp.smtpout.orange.fr (smtp13.smtpout.orange.fr [80.12.242.135]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC0DD12B040 for ; Tue, 13 Sep 2016 12:28:47 -0700 (PDT) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d76 with ME id j7Uk1t00C17Lgi4037UlRj; Tue, 13 Sep 2016 21:28:45 +0200 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Tue, 13 Sep 2016 21:28:45 +0200 X-ME-IP: 92.170.5.52 To: John Levine , dispatch@ietf.org References: <20160913135417.53163.qmail@ary.lan> From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: <94e66340-f394-5407-97e7-339e2c2c2e13@trigofacile.com> Date: Tue, 13 Sep 2016 21:28:44 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160913135417.53163.qmail@ary.lan> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [dispatch] Review of two drafts refreshing the use of TLS with NNTP X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2016 19:28:51 -0000 Hi John, >> - one that defines an NNTP extension to allow a connection to be >> compressed (inspired from the IMAP COMPRESS command defined in RFC 4978): >> https://tools.ietf.org/html/draft-murchison-nntp-compress-05 > > I've looked at them, and they seem fine to me. Section 3 in the > Murchison draft, offering advice on how to tune your compression, > strikes me as premature overoptimization, but since it only affects > compression efficiency, not interop, it's not very important. Thanks for having looked at the drafts. Maybe Section 3.1 should directly begin Section 3 (dealing with interoperability), and the current begin of Section 3 (advice of optimization) be an Appendix? -- Julien ÉLIE « Nigro notanda lapillo. » (Catulle) From nobody Tue Sep 13 13:22:36 2016 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 7B40F12B076 for ; Tue, 13 Sep 2016 13:22:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 FOqi-Yq0ZRt4 for ; Tue, 13 Sep 2016 13:22:32 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94B1F12B037 for ; Tue, 13 Sep 2016 13:22:32 -0700 (PDT) Received: (qmail 21989 invoked from network); 13 Sep 2016 20:22:30 -0000 Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 13 Sep 2016 20:22:30 -0000 Date: 13 Sep 2016 20:11:42 -0000 Message-ID: <20160913201142.53911.qmail@ary.lan> From: "John Levine" To: dispatch@ietf.org In-Reply-To: <94e66340-f394-5407-97e7-339e2c2c2e13@trigofacile.com> Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: Subject: Re: [dispatch] Review of two drafts refreshing the use of TLS with NNTP X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2016 20:22:34 -0000 >>> https://tools.ietf.org/html/draft-murchison-nntp-compress-05 >> >> I've looked at them, and they seem fine to me. Section 3 in the >> Murchison draft, offering advice on how to tune your compression, >> strikes me as premature overoptimization, but since it only affects >> compression efficiency, not interop, it's not very important. > >Thanks for having looked at the drafts. >Maybe Section 3.1 should directly begin Section 3 (dealing with >interoperability), and the current begin of Section 3 (advice of >optimization) be an Appendix? It's not clear in all of section 3 whether the advice is based on observations of how traffic actually compresses, or guesses about what will happen. Do you know which it is? If it's observation, the whole section can stay. If it's guesses, the whole section should go. R's, John From nobody Tue Sep 13 13:59:44 2016 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 1B8EF12B077 for ; Tue, 13 Sep 2016 13:59:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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 JrI-oYj4TzGs for ; Tue, 13 Sep 2016 13:59:40 -0700 (PDT) Received: from smtp.smtpout.orange.fr (smtp13.smtpout.orange.fr [80.12.242.135]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2694512B04D for ; Tue, 13 Sep 2016 13:59:39 -0700 (PDT) Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d76 with ME id j8zc1t00D17Lgi4038zd4F; Tue, 13 Sep 2016 22:59:38 +0200 X-ME-Helo: macbook-pro-de-julien-elie.home X-ME-Auth: anVsaWVuLmVsaWU0ODdAd2FuYWRvby5mcg== X-ME-Date: Tue, 13 Sep 2016 22:59:38 +0200 X-ME-IP: 92.170.5.52 To: John Levine , dispatch@ietf.org References: <20160913201142.53911.qmail@ary.lan> From: =?UTF-8?Q?Julien_=c3=89LIE?= Organization: TrigoFACILE -- http://www.trigofacile.com/ Message-ID: <6e3f97bd-31a8-4e09-3790-f90c042cf073@trigofacile.com> Date: Tue, 13 Sep 2016 22:59:36 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160913201142.53911.qmail@ary.lan> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [dispatch] Review of two drafts refreshing the use of TLS with NNTP X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2016 20:59:43 -0000 Hi John, >>>> https://tools.ietf.org/html/draft-murchison-nntp-compress-05 >> >> Thanks for having looked at the drafts. >> Maybe Section 3.1 should directly begin Section 3 (dealing with >> interoperability), and the current begin of Section 3 (advice of >> optimization) be an Appendix? > > It's not clear in all of section 3 whether the advice is based on > observations of how traffic actually compresses, or guesses about what > will happen. Do you know which it is? I ran some tests last year about compression ratios, and Bo Lindbergh about the use of different flush options: https://groups.google.com/forum/#!topic/news.software.nntp/ZXrwlcAUMMM (thread beginning with Message-ID ) Netnews articles are pretty similar to e-mails, so it is not surprising to find a performance similar to what Section 4 of RFC 4978 (COMPRESS for IMAP) mentioned. When we say that "responses not related to article header/body retrieval (e.g, CAPABILITIES, GROUP, LISTGROUP, LAST, NEXT, STAT, DATE, NEWNEWS, NEWGROUPS, LIST, CHECK [RFC4644], etc) are highly compressible; zlib using its least CPU-intensive setting compresses typical responses to 25-40% of their original size." We for instance have: LIST ACTIVE answer Uncompressed: 1393931 bytes Compressed with level 1: 394856 bytes (28%) [...] Compressed with level 9: 314809 bytes (22%) LIST NEWSGROUPS answer Uncompressed: 2564921 bytes Compressed with level 1: 836486 bytes (32%) [...] Compressed with level 9: 718244 bytes (28%) LISTGROUP answer Uncompressed: 53793 bytes Compressed with level 1: 20177 bytes (37%) [...] Compressed with level 9: 20329 bytes (37%) NEWNEWS answer Uncompressed: 474178 bytes Compressed with level 1: 147513 bytes (31%) [...] Compressed with level 9: 128067 bytes (27%) These are the most used commands in question, and the ratio is 25-40% for level 1. Maybe in the list given in example of commands, we should drop 1-line answers that in fact won't save many bytes. We're speaking of 30 bytes or like answers... And they are not compressed to 10 bytes, but as often as not remain of the same size, or are 70-100% compressed. Let's just keep LISTGROUP, NEWNEWS, NEWGROUPS and LIST for clarity. No need to list all existing NNTP commands! And for Base64 attachments, the result is not surprising: Uncompressed: 13710605 bytes Compressed with level 1: 10532602 bytes (76%) [...] Compressed with level 9: 10357010 bytes (75%) > If it's observation, the whole section can stay. If it's guesses, > the whole section should go. We can then keep it in Section 3 instead of an Appendix. -- Julien ÉLIE « Nigro notanda lapillo. » (Catulle) From nobody Wed Sep 14 07:42:32 2016 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 419E712B8A6 for ; Wed, 14 Sep 2016 07:42:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_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 9DR7BxahugVE for ; Wed, 14 Sep 2016 07:42:28 -0700 (PDT) Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 5077E12BCED for ; Wed, 14 Sep 2016 07:02:43 -0700 (PDT) X-AuditID: c1b4fb30-b73ff70000000cb2-5b-57d958815aaf Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by (Symantec Mail Security) with SMTP id 8D.79.03250.18859D75; Wed, 14 Sep 2016 16:02:41 +0200 (CEST) Received: from ESESSMB209.ericsson.se ([169.254.9.211]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0301.000; Wed, 14 Sep 2016 16:02:40 +0200 From: Christer Holmberg To: "dispatch@ietf.org" Thread-Topic: Draft pull request: draft-holmberg-dispatch-received-realm Thread-Index: AQHSDpCnguIp2UVaqEOKGntKXJh9zA== Date: Wed, 14 Sep 2016 14:02:40 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.6.5.160527 x-originating-ip: [153.88.183.147] Content-Type: multipart/alternative; boundary="_000_D3FF346FF341christerholmbergericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNLMWRmVeSWpSXmKPExsUyM2K7um5jxM1wg+tz1C2WTlrA6sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujAX7n7EWfOapWHzqEGMD4xbuLkZODgkBE4mtc1axdTFycQgJ rGeUWNR6gwUkISSwhFFi5W+rLkYODjYBC4nuf9ogYREBbYmjq7qYQcLCAs4Sc557QYQ9JG69 fsYOYetJrO68CDaFRUBV4vDBbjYQm1fASmJN22KwGkYBMYnvp9YwgdjMAuISt57MZ4I4R0Bi yZ7zzBC2qMTLx/9YQWxRoJnfv84GWyshoCQxbWsaRGu8xISeJYwQ4wUlTs58wjKBUWgWkqmz kJTNQlIGETeQeH9uPjOErS2xbOFrKFtfYuOXs4wQtrXEjJuHmJDVLGDkWMUoWpxanJSbbmSk l1qUmVxcnJ+nl5dasokRGCUHt/w22MH48rnjIUYBDkYlHt4H4TfDhVgTy4orcw8xSnAwK4nw xgUBhXhTEiurUovy44tKc1KLDzFKc7AoifP+O3s9XEggPbEkNTs1tSC1CCbLxMEp1cA4/f6K t9ZW3617JC1uq90qfXfT+jBX1rfSRW9dV1s+/t7N33mxvbs22PdQv03tvNyt2ts+rddofxLO VVRr9axw60W9uoLns3xM+D4/+vad/W1iIoP4hNczXORmnPvT6rfT/t6J15+lV+XOn3y8/0tU ovI173PzDsTl96wsWbPo4/ak9K+flmwoV2Ipzkg01GIuKk4EAB3icCuOAgAA Archived-At: Subject: [dispatch] Draft pull request: draft-holmberg-dispatch-received-realm X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2016 14:42:30 -0000 --_000_D3FF346FF341christerholmbergericssoncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, Based on the comments from Adam, I=92ve created a pull request in order to = update draft-holmberg-dispatch-received-realm. https://github.com/cdh4u/draft-received-realm/commit/79ad3186e5acfec01ab274= ba2a16737c04dd97b8 Feel free to take a look and comment before I submit the new version. Regards, Christer --_000_D3FF346FF341christerholmbergericssoncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable
Hi,

Based on the comments from Adam, I=92ve created a pull request in orde= r to update draft-holmberg-dispatch-received-realm.

Feel free to take a look and comment before I submit the new version.<= /div>

Regards,

Christer
--_000_D3FF346FF341christerholmbergericssoncom_-- From nobody Sun Sep 18 07:36:18 2016 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 463D812B03C for ; Sun, 18 Sep 2016 07:36:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.72 X-Spam-Level: X-Spam-Status: No, score=-2.72 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, 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 (1024-bit key) header.d=fastmail.fm header.b=KDVkfR1Z; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=qZw8H3tL 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 y5N2_9sZw18X for ; Sun, 18 Sep 2016 07:36:14 -0700 (PDT) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4350127A91 for ; Sun, 18 Sep 2016 07:36:14 -0700 (PDT) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 2123B203D5 for ; Sun, 18 Sep 2016 10:36:14 -0400 (EDT) Received: from web6 ([10.202.2.216]) by compute6.internal (MEProxy); Sun, 18 Sep 2016 10:36:14 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=626 c1rufUEDSIqJtec/JrjBUICY=; b=KDVkfR1ZfyQFgcuDl5W0mti+kPcIrJFEywz H2w5224xvpVkuwqf8hcsp4J7T6Y8EB9OoXKdDsot8+PTEJfb7z5VfGCaIBaOPOMe j0wK3oWvXT5nfTKfPrDwGcllPG54uMa/hJxJPJKVNbdKUyY/fcN2Y+/LUDo+obEM D1yo+KjE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=626c1rufUEDSIqJtec/JrjBUICY=; b=qZw8H 3tLHMHW3CawKIQFK1YrfIy1xdt5To/NrWbSHNLVhZcH7zhUS61Ks9suG9OCVgNnd kmgiTxy9rK2oT1hF6H6HYZHOlyXJrMNqZ50mFiYm8nZu0gdEaaWxxTBQ1IxSlgyI 9ZrULpHMtIjf+C8nG6lnfftttdGJa3ppscYBug= Received: by mailuser.nyi.internal (Postfix, from userid 99) id DAE9E1EB86; Sun, 18 Sep 2016 10:36:13 -0400 (EDT) Message-Id: <1474209373.3075077.729281857.674CFBF6@webmail.messagingengine.com> X-Sasl-Enc: nIFMZWrgM/9//jiEWzPY8qpU/Gh8Gdg2U4vJEVF8dG2O 1474209373 From: Alexey Melnikov To: DISPATCH MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-e7f54b57 Date: Sun, 18 Sep 2016 15:36:13 +0100 Archived-At: Subject: [dispatch] Straw man text for proposed charter: Security Event X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Sep 2016 14:36:16 -0000 Hi, I received a proposal to charter a new WG. Proponents are discussing it on id-event@ietf.org mailing list. Note, that at the moment it is not clear whether this will land in ART or SEC Area, this is to be decided. Please comment on the strawman Charter, which is shown below: Chairs: TBD Applications and Real-Time Area Directors: TBD Applications and Real-Time Area Advisor: TBD Mailing Lists: General Discussion: id-event@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/id-event Archive: https://mailarchive.ietf.org/arch/browse/id-event/ Description of Working Group: Many identity related protocols require a mechanism to convey messages between systems in order to prevent or mitigate security risks, or to provide out-of-band information as necessary. For example, an OAuth authorization server, having received a token revocation request (RFC7009) may need to inform affected resource servers; a cloud provider may wish to inform another cloud provider of suspected fraudulent use of identity information; an identity provider may wish to signal a session logout to a relying party. It is expected that several identity and security working groups and organizations will use Identity Event Tokens to describe area-specific events such as: SCIM Provisioning Events, OpenID RISC Events, and OpenID Connect Backchannel Logout, among others. The Security Event working group will produce a standards-track Event Token specification that includes: - A JWT extension for expressing security events - A syntax that enables event-specific data to be conveyed This Event Token specification will be event transport independent. The working group will also develop a simple standards-track Event Delivery specification that includes: - A method for delivering events using HTTP POST (push) - Metadata for describing event feeds - Methods for subscribing to and managing event feeds - Methods for validating event feed subscriptions Goals and Milestones: October 2016 - Initial adoption of event token and event delivery drafts February 2017 - WG last call of event token draft April 2017 - Event token draft to IESG as a proposed standard July 2017 - WG last call of event delivery draft September 2017 - Event delivery draft to IESG as a proposed standard November 2017 - Work completed; discuss rechartering if needed From nobody Mon Sep 19 00:42:07 2016 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 DA6DE12B0BF for ; Mon, 19 Sep 2016 00:42:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_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 qdQjBv8UALDq for ; Mon, 19 Sep 2016 00:42:03 -0700 (PDT) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 6895012B08C for ; Mon, 19 Sep 2016 00:42:03 -0700 (PDT) X-AuditID: c1b4fb2d-cf87d980000019a3-db-57df96c9ae01 Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by (Symantec Mail Security) with SMTP id 50.D5.06563.9C69FD75; Mon, 19 Sep 2016 09:42:01 +0200 (CEST) Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0301.000; Mon, 19 Sep 2016 09:42:00 +0200 From: Christer Holmberg To: "dispatch@ietf.org" Thread-Topic: Draft new version: draft-holmberg-dispatch-received-realm Thread-Index: AQHSEklONZDJlJ6970yyqTw8mJA5+g== Date: Mon, 19 Sep 2016 07:42:00 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.6.5.160527 x-originating-ip: [153.88.183.147] Content-Type: multipart/alternative; boundary="_000_D40572C3F5B6christerholmbergericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFLMWRmVeSWpSXmKPExsUyM2K7ou7JaffDDSb8MrJYOmkBqwOjx5Il P5kCGKO4bFJSczLLUov07RK4Mm5+fc5UcJK7YvlqlgbGtVxdjJwcEgImElsnz2DuYuTiEBJY zyix/MITdpCEkMBiRolzc/W7GDk42AQsJLr/aYOERQS0JY6u6mIGsYUFnCTWtnexQ8TdJZac +M0GUi4ioCexdIIwSJhFQFViUuNxsBJeASuJ/68XsIHYjAJiEt9PrWECsZkFxCVuPZnPBHGO gMSSPeeZIWxRiZeP/7GC2KJAI79/nc0MMl5CQEli2tY0iNZ4idVXzjJBjBeUODnzCcsERqFZ SKbOQlI2C0kZRNxA4v25+cwQtrbEsoWvoWx9iY1fzjJC2NYSy6YsQVGzgJFjFaNocWpxcW66 kbFealFmcnFxfp5eXmrJJkZgjBzc8lt3B+Pq146HGAU4GJV4eB/U3Q8XYk0sK67MPcQowcGs JML7sxcoxJuSWFmVWpQfX1Sak1p8iFGag0VJnPff2evhQgLpiSWp2ampBalFMFkmDk6pBsbe LWHCNtWCG0v8H55Yf2h+n/s09+klMXP1t/8/M/PLEqeG0z0VOc9fmYp+Er6ZyL7E5ug9u+kT FA/mTMksTZDnjpEWqjqbxeL9jGn5L/Z3pxfPS5pVztyxcdX2nvtVNX+TKg8wet70WBoceq5x gq+qrU/R9FmHQ1hCvl43yWqf+P5umNqcywxKLMUZiYZazEXFiQDSVjZpjQIAAA== Archived-At: Subject: [dispatch] Draft new version: draft-holmberg-dispatch-received-realm X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 07:42:05 -0000 --_000_D40572C3F5B6christerholmbergericssoncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, Based on comments from Adam, I=92ve submitted a new version (-03) of draft-= holmberg-dispatch-received-realm. Regards, Christer --_000_D40572C3F5B6christerholmbergericssoncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <67F0D33BF7A7F04BBF1B0EA0C7A51ADF@ericsson.com> Content-Transfer-Encoding: quoted-printable
Hi,

Based on comments from Adam, I=92ve submitted a new version (-03) of&n= bsp;draft= -holmberg-dispatch-received-realm.

Rega= rds,

Chri= ster
--_000_D40572C3F5B6christerholmbergericssoncom_-- From nobody Mon Sep 19 03:55:18 2016 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 84D7812B316 for ; Mon, 19 Sep 2016 03:55:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=broadsoft-com.20150623.gappssmtp.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 2i5VqZGZ2YXa for ; Mon, 19 Sep 2016 03:55:15 -0700 (PDT) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::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 BE2CE12B102 for ; Mon, 19 Sep 2016 03:55:14 -0700 (PDT) Received: by mail-lf0-x22e.google.com with SMTP id h127so107904349lfh.0 for ; Mon, 19 Sep 2016 03:55:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadsoft-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:thread-index:date:message-id:subject:to; bh=oakQu4oeO2hNov9HHqInHQPAmvy/xIpI5w6m4FsS8ng=; b=0BEy1VgIn14QbmZaGTDd5N/tLArWT999k2IGwMMf4Qftkov90h82gtCtUGH2oZ/e/3 p29Bs9xFShCKMWCyfxZlgYLHPWibTxMS3CFsafaIBzkfMvXoeryYa+mZdpMgaVOXdOTw hITcu2PRO/bRnr83GJegoIyGGeI++bPJ6NGoyWD30Hr6bmtO7HB57U4cmEvtfpmEa+gR zLRVE8RZWP/WWEMsvF7TwQHr6Sqgy2b/NhIhBUJFd3pEWyECX0C0tva4/WE4TVf2xtT3 VOofvvnrB6mXMAgEyt3t6wToHMAHaEC3C1U3XNW60i9MI6RwO92+JYt9gPwjLSWn06nW Ckzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to; bh=oakQu4oeO2hNov9HHqInHQPAmvy/xIpI5w6m4FsS8ng=; b=DLFiGSqUOuy5RwVkE/QOWff2kB6zKAvMCSVctkBw6vV7a2B4zNdRnjmOE40W5sW+Cp wuy5RoxwSs85kxe/8Jruj5BvSpEHzfKGE1ATNYHiIEIe0huHRWcL+wP63EJLXQ6FMLIZ WNdugfc2hYjEOtdMfpHCzQDU0g8/TByhN/kWJaRAPShzqpiauz1OmdGOAhBk/Tj/Cc9y sKPOo1of9BFMW/lo9bsjKSgJsqVkPKC0gG3Ljkh6qi1JBGZKMmwTfORgsdCl22enhJ/a Eu2Aukshb2YMuG6qKhpo4iaMG7Tq22xVI4jDUurqQTx9k72qNtxB0P63lp51n5Q0Yw7A MCLg== X-Gm-Message-State: AE9vXwMdvbodo/JACR1lAmsVcGgTPH6V9KQyWZlXa2N2WCokP9SlDQUoMsapzQ6tX2xRhlYx4EATnu/GBeRHw5gh X-Received: by 10.25.219.154 with SMTP id t26mr9531702lfi.116.1474282512513; Mon, 19 Sep 2016 03:55:12 -0700 (PDT) From: Brett Tate MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdISZDOEAso7uGHqTF6Amtr6489EAg== Date: Mon, 19 Sep 2016 06:55:10 -0400 Message-ID: <5b403598e6e3970be9885ebeb973ca68@mail.gmail.com> To: dispatch@ietf.org, draft-holmberg-dispatch-received-realm@tools.ietf.org Content-Type: text/plain; charset=UTF-8 Archived-At: Subject: [dispatch] draft-holmberg-dispatch-received-realm-03: syntax comment X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 10:55:16 -0000 Hi, Concerning draft-holmberg-dispatch-received-realm-03 section 5.5.2, the Via parameter syntax does not appear to be backward compatible with via-extension which is a generic-param. To remain backward compatible, the received-realm value would need to fall within the syntax of token, host, or quoted-string. Thanks, Brett From nobody Mon Sep 19 11:04:52 2016 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 EAE4312B4BF for ; Mon, 19 Sep 2016 11:04:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.221 X-Spam-Level: X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_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 s9GaRA7dazst for ; Mon, 19 Sep 2016 11:04:49 -0700 (PDT) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 2B39E12B4B1 for ; Mon, 19 Sep 2016 11:04:49 -0700 (PDT) X-AuditID: c1b4fb25-5405a9800000793b-54-57e028bf0624 Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by (Symantec Mail Security) with SMTP id 17.02.31035.FB820E75; Mon, 19 Sep 2016 20:04:47 +0200 (CEST) Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0301.000; Mon, 19 Sep 2016 20:04:44 +0200 From: Christer Holmberg To: Brett Tate , "dispatch@ietf.org" , "draft-holmberg-dispatch-received-realm@tools.ietf.org" Thread-Topic: [dispatch] draft-holmberg-dispatch-received-realm-03: syntax comment Thread-Index: AdISZDOEAso7uGHqTF6Amtr6489EAgAO/G3Q Date: Mon, 19 Sep 2016 18:04:44 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B4BCD378F@ESESSMB209.ericsson.se> References: <5b403598e6e3970be9885ebeb973ca68@mail.gmail.com> In-Reply-To: <5b403598e6e3970be9885ebeb973ca68@mail.gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.148] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyM2K7se5+jQfhBt/fK1o0z//HaLF00gJW i77dX1kdmD1+3A70WLLkJ5PHl8uf2QKYo7hsUlJzMstSi/TtErgy3j2vLXjPXvHscQdbA+N5 ti5GTg4JAROJdTvWMXYxcnEICaxnlLi34x8LhLOYUaJ59zGgKg4ONgELie5/2iANIgKHGCVO X7cCCQsLBEt0vGUCMUUEQiTW/5WCqDCSWPT8P9h4FgFViWsTrzOC2LwCvhKf/zeBxYUEbCWW 3rrCCmJzCthJrH/1AKyGUUBM4vupNUwgNrOAuMStJ/OZIM4UkFiy5zwzhC0q8fLxP1YIW0mi cckTVoh6HYkFuz+xQdjaEssWvmaG2CsocXLmE5YJjCKzkIydhaRlFpKWWUhaFjCyrGIULU4t TspNNzLWSy3KTC4uzs/Ty0st2cQIjI2DW36r7mC8/MbxEKMAB6MSD2/C+/vhQqyJZcWVucBg 4mBWEuGVln0QLsSbklhZlVqUH19UmpNafIhRmoNFSZzXbCVQtUB6YklqdmpqQWoRTJaJg1Oq gXGKcJLXLL36Z+/vpRnYdWTOvx7XGJKbL1dhWpehaCan+ujGPGd1qUNWsy2DvTkj7Q+Gurbv 9zy0aav9yufhee7vL0rILGtt2yQU+ieAk1nnRI3L8t1nXtlGnr6r+so8ImV7Urx0WP/vP8oX vsoJHNO6zn0jNst2YdmN7oPnJ7udmL9RMWjNJyWW4oxEQy3mouJEAGOulOiJAgAA Archived-At: Subject: Re: [dispatch] draft-holmberg-dispatch-received-realm-03: syntax comment X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 18:04:51 -0000 Hi Brett, You are correct. The intention was to define the whole value as quoted-stri= ng, so the LDQUOT shall be in front of operator-id. I'll correct it in the next version. Thanks! Regards, Christer -----Original Message----- From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Brett Tate Sent: 19 September 2016 13:55 To: dispatch@ietf.org; draft-holmberg-dispatch-received-realm@tools.ietf.or= g Subject: [dispatch] draft-holmberg-dispatch-received-realm-03: syntax comme= nt Hi, Concerning draft-holmberg-dispatch-received-realm-03 section 5.5.2, the Via= parameter syntax does not appear to be backward compatible with via-extens= ion which is a generic-param. To remain backward compatible, the received-= realm value would need to fall within the syntax of token, host, or quoted-= string. Thanks, Brett _______________________________________________ dispatch mailing list dispatch@ietf.org https://www.ietf.org/mailman/listinfo/dispatch From nobody Wed Sep 21 06:36:49 2016 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 A085212B194 for ; Wed, 21 Sep 2016 06:36:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_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 Mjc8C6DjBgpQ for ; Wed, 21 Sep 2016 06:36:46 -0700 (PDT) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 A59C812B166 for ; Wed, 21 Sep 2016 06:36:45 -0700 (PDT) X-AuditID: c1b4fb25-15fff7000000793b-a4-57e28ceabdc6 Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by (Symantec Mail Security) with SMTP id 1B.3D.31035.AEC82E75; Wed, 21 Sep 2016 15:36:43 +0200 (CEST) Received: from ESESSMB209.ericsson.se ([169.254.9.32]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0301.000; Wed, 21 Sep 2016 15:36:42 +0200 From: Christer Holmberg To: Brett Tate , "dispatch@ietf.org" , "draft-holmberg-dispatch-received-realm@tools.ietf.org" Thread-Topic: [dispatch] draft-holmberg-dispatch-received-realm-03: syntax comment Thread-Index: AdISZDOEAso7uGHqTF6Amtr6489EAgBqPyAg Date: Wed, 21 Sep 2016 13:36:42 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B4BCE7294@ESESSMB209.ericsson.se> References: <5b403598e6e3970be9885ebeb973ca68@mail.gmail.com> In-Reply-To: <5b403598e6e3970be9885ebeb973ca68@mail.gmail.com> Accept-Language: en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4BCE7294ESESSMB209erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGbHdQPd1z6NwgxmvDS2a5/9jtFg6aQGr Rd/ur6wOzB4/bgd6LFnyk8njy+XPbAHMUVw2Kak5mWWpRfp2CVwZvx5/ZinYL1vR9PwDcwPj OqkuRk4OCQETiRmXV7N3MXJxCAmsZ5T4dWIDM4SzmFHi48EFTF2MHBxsAhYS3f+0QRpEBA4x Spy+bgUSFhYIluh4C1YhIhAisf6vFESFkcSlVcvYQGwWAVWJWbOfsILYvAK+EvvnrGYGsYUE bCWW3roCFucUsJNY/+oBI4jNKCAm8f3UGiYQm1lAXKLpy0pWiDMFJJbsOc8MYYtKvHz8jxWi Jl/iyrrJUPMFJU7OfMIygVFoFpL2WUjKZiEpg4gbSHx5fxvK1pZYtvA1M4StL9H9/jQTsvgC RvZVjKLFqcVJuelGxnqpRZnJxcX5eXp5qSWbGIFRc3DLb9UdjJffOB5iFOBgVOLhfeDwMFyI NbGsuDIXGGQczEoivOu7HoUL8aYkVlalFuXHF5XmpBYfYpTmYFES5zVbeT9cSCA9sSQ1OzW1 ILUIJsvEwSnVwBhfu1h+RXOZjqpt9kef3sBzm0Wc8t5sLrmgWZJk0nOfS4Pr8fmJrrc6N3G3 d6svE99xZJeOYzxbzOXJUcp7CjoDpmpbbZhsKCR27230z2sHZSLdziUd4g7ofWPyeLKlyPbz CSfLoyXfKZ/+9jUuUVXPpUNgwzLBU7HhjEFn0ouburIO3T5frcRSnJFoqMVcVJwIAPFh7nKW AgAA Archived-At: Subject: Re: [dispatch] draft-holmberg-dispatch-received-realm-03: syntax comment X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2016 13:36:48 -0000 --_000_7594FB04B1934943A5C02806D1A2204B4BCE7294ESESSMB209erics_ Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: quoted-printable Hi, I've fixed the ABNF and submitted a new version (-04) of the draft. Regards, Christer Sent from my Windows Phone ________________________________ From: Brett Tate Sent: =FD19/=FD09/=FD2016 13:55 To: dispatch@ietf.org; draft-holmberg-dispatch-re= ceived-realm@tools.ietf.org Subject: [dispatch] draft-holmberg-dispatch-received-realm-03: syntax comme= nt Hi, Concerning draft-holmberg-dispatch-received-realm-03 section 5.5.2, the Via parameter syntax does not appear to be backward compatible with via-extension which is a generic-param. To remain backward compatible, the received-realm value would need to fall within the syntax of token, host, or quoted-string. Thanks, Brett _______________________________________________ dispatch mailing list dispatch@ietf.org https://www.ietf.org/mailman/listinfo/dispatch --_000_7594FB04B1934943A5C02806D1A2204B4BCE7294ESESSMB209erics_ Content-Type: text/html; charset="windows-1256" Content-Transfer-Encoding: quoted-printable
Hi,

I've fixed the ABNF and submitted a new version (-04) of the draft.

Regards,

Christer

Sent from my Windows Phone
From: Brett Tate
Sent: =FD19= /=FD09/=FD2016 13:55
To: dispatch@ietf.org; dr= aft-holmberg-dispatch-received-realm@tools.ietf.org
Subject: [disp= atch] draft-holmberg-dispatch-received-realm-03: syntax comment

Hi,

Concerning draft-holmberg-dispatch-received-realm-03 section 5.5.2, the
Via parameter syntax does not appear to be backward compatible with
via-extension which is a generic-param.  To remain backward compatible= ,
the received-realm value would need to fall within the syntax of token,
host, or quoted-string.

Thanks,
Brett

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf= .org/mailman/listinfo/dispatch
 --_000_7594FB04B1934943A5C02806D1A2204B4BCE7294ESESSMB209erics_-- From nobody Sun Sep 25 23:09:36 2016 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 0CBD412B094 for ; Sun, 25 Sep 2016 23:09:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.72 X-Spam-Level: X-Spam-Status: No, score=-2.72 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, 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 (1024-bit key) header.d=yandex.ru 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 2JAvVZRtpzuZ for ; Sun, 25 Sep 2016 23:09:34 -0700 (PDT) Received: from forward15o.cmail.yandex.net (forward15o.cmail.yandex.net [37.9.109.212]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2633912B095 for ; Sun, 25 Sep 2016 23:09:34 -0700 (PDT) Received: from mxback2o.mail.yandex.net (mxback2o.mail.yandex.net [37.140.190.16]) by forward15o.cmail.yandex.net (Yandex) with ESMTP id E441B20C00 for ; Mon, 26 Sep 2016 09:09:30 +0300 (MSK) Received: from web4o.yandex.ru (web4o.yandex.ru [95.108.205.104]) by mxback2o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 61VkYUDDPy-9UamXXLD; Mon, 26 Sep 2016 09:09:30 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1474870170; bh=jl/Ch30DhqQAghZcscpiBMItiBn5m0zTo9sClGUX5YY=; h=From:To:Subject:Message-Id:Date; b=wz5QzeRLVn61ypcL2u4Ve4OMf+ZFDwyjfymDkVp+5s1XT+xtouxQjlzjmGftFK8gN WVA/h0Io4ZwqkNBQINsgdADqurQ+u1okfz9VIw/QHqG40zzCY4JY6UMXF4wFSSQB15 JKopJ/hp+GPM8K7e6g/8JG8esDDadCRCW0IyrqZ8= Authentication-Results: mxback2o.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by web4o.yandex.ru with HTTP; Mon, 26 Sep 2016 09:09:30 +0300 From: =?utf-8?B?0KLQstC10YDQtdGC0LjQvSDQkNC90YLQvtC9INCh0LXRgNCz0LXQtdCy0LjRhw==?= To: DISPATCH list MIME-Version: 1.0 Message-Id: <2878671474870170@web4o.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Mon, 26 Sep 2016 11:09:30 +0500 Content-Transfer-Encoding: 7bit Content-Type: text/plain Archived-At: Subject: Re: [dispatch] draft-mohali-dispatch-originating-cdiv-parameter-01 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2016 06:09:36 -0000 I support this I-D. For me, it is in the spirit of RFC 2543 and RFC 3261. As a nit: this I-D reproduces ABNF from RFC 5502. The text should say that ABNFs are informative, not normative; RFC 5502 is normative. From nobody Mon Sep 26 02:23:50 2016 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 96D5012B071 for ; Mon, 26 Sep 2016 02:23:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.934 X-Spam-Level: X-Spam-Status: No, score=-4.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001, TVD_PH_BODY_ACCOUNTS_PRE=0.001, UNPARSEABLE_RELAY=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 6BN9k0lbpL_K for ; Mon, 26 Sep 2016 02:23:47 -0700 (PDT) Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F222F12B01A for ; Mon, 26 Sep 2016 02:23:46 -0700 (PDT) Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 6ABD4C03C2; Mon, 26 Sep 2016 11:23:45 +0200 (CEST) Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.63]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 482FB40075; Mon, 26 Sep 2016 11:23:45 +0200 (CEST) Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM6E.corporate.adroot.infra.ftgroup ([fe80::f5a7:eab1:c095:d9ec%18]) with mapi id 14.03.0301.000; Mon, 26 Sep 2016 11:23:44 +0200 From: To: =?utf-8?B?0KLQstC10YDQtdGC0LjQvSDQkNC90YLQvtC9INCh0LXRgNCz0LXQtdCy0Lg=?= =?utf-8?B?0Yc=?= , DISPATCH list Thread-Topic: [dispatch] draft-mohali-dispatch-originating-cdiv-parameter-01 Thread-Index: AQHSF7ySB+/zwbPSHkWZyzWJpnXn/6CLdYXw Date: Mon, 26 Sep 2016 09:23:44 +0000 Message-ID: <1850_1474881825_57E8E921_1850_1113_1_8B970F90C584EA4E97D5BAAC9172DBB81AACE4B8@OPEXCLILMA4.corporate.adroot.infra.ftgroup> References: <2878671474870170@web4o.yandex.ru> In-Reply-To: <2878671474870170@web4o.yandex.ru> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.3] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: Subject: Re: [dispatch] draft-mohali-dispatch-originating-cdiv-parameter-01 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2016 09:23:49 -0000 SGksDQoNClRoYW5rIHlvdSBmb3IgdGhlIHN1cHBvcnQuDQpJIHdpbGwgdGFrZSBpbnRvIGFjY291 bnQgdGhlIG5pdCBjb25jZXJuaW5nIHRoZSBBQk5GIGluIHRoZSB1cGRhdGVkIHZlcnNpb24gb2Yg dGhlIGRyYWZ0Lg0KDQpCZXN0IFJlZ2FyZHMsDQpNYXJpYW5uZSBNb2hhbGkNCg0KLS0tLS1NZXNz YWdlIGQnb3JpZ2luZS0tLS0tDQpEZcKgOiBkaXNwYXRjaCBbbWFpbHRvOmRpc3BhdGNoLWJvdW5j ZXNAaWV0Zi5vcmddIERlIGxhIHBhcnQgZGUgPz8/Pz8/Pz8gPz8/Pz8gPz8/Pz8/Pz8/DQpFbnZv ecOpwqA6IGx1bmRpIDI2IHNlcHRlbWJyZSAyMDE2IDA4OjEwDQrDgMKgOiBESVNQQVRDSCBsaXN0 DQpPYmpldMKgOiBSZTogW2Rpc3BhdGNoXSBkcmFmdC1tb2hhbGktZGlzcGF0Y2gtb3JpZ2luYXRp bmctY2Rpdi1wYXJhbWV0ZXItMDENCg0KSSBzdXBwb3J0IHRoaXMgSS1ELiBGb3IgbWUsIGl0IGlz IGluIHRoZSBzcGlyaXQgb2YgUkZDIDI1NDMgYW5kIFJGQyAzMjYxLg0KQXMgYSBuaXQ6IHRoaXMg SS1EIHJlcHJvZHVjZXMgQUJORiBmcm9tIFJGQyA1NTAyLiBUaGUgdGV4dCBzaG91bGQgc2F5IHRo YXQgQUJORnMgYXJlIGluZm9ybWF0aXZlLCBub3Qgbm9ybWF0aXZlOyBSRkMgNTUwMiBpcyBub3Jt YXRpdmUuDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f DQpkaXNwYXRjaCBtYWlsaW5nIGxpc3QNCmRpc3BhdGNoQGlldGYub3JnDQpodHRwczovL3d3dy5p ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2Rpc3BhdGNoDQoKX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBl dCBzZXMgcGllY2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNv bmZpZGVudGllbGxlcyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJl IGRpZmZ1c2VzLCBleHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3Vz IGF2ZXogcmVjdSBjZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEg bCdleHBlZGl0ZXVyIGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMu IExlcyBtZXNzYWdlcyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRp b24sCk9yYW5nZSBkZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBl dGUgYWx0ZXJlLCBkZWZvcm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQg aXRzIGF0dGFjaG1lbnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGlu Zm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBi ZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5 b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBz ZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1h aWxzIG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhh dCBoYXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo= From nobody Tue Sep 27 06:40:24 2016 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 B70E512B19D for ; Tue, 27 Sep 2016 06:40:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.619 X-Spam-Level: X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 QDJLlEZoZgRe for ; Tue, 27 Sep 2016 06:40:19 -0700 (PDT) Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E82212B19E for ; Tue, 27 Sep 2016 06:40:19 -0700 (PDT) Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 67635264839 for ; Tue, 27 Sep 2016 15:40:17 +0200 (CEST) Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.27]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 4D937238056 for ; Tue, 27 Sep 2016 15:40:17 +0200 (CEST) Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM7C.corporate.adroot.infra.ftgroup ([fe80::8007:17b:c3b4:d68b%19]) with mapi id 14.03.0301.000; Tue, 27 Sep 2016 15:40:17 +0200 From: To: DISPATCH list Thread-Topic: New version (-02) of draft-mohali-dispatch-originating-cdiv-parameter Thread-Index: AdIYL56aSk2Z9SUKR3qqnemiEWMb4Q== Date: Tue, 27 Sep 2016 13:40:16 +0000 Message-ID: <21780_1474983617_57EA76C1_21780_1371_1_8B970F90C584EA4E97D5BAAC9172DBB81AAD0C75@OPEXCLILMA4.corporate.adroot.infra.ftgroup> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.5] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.6.17.114517 Archived-At: Subject: [dispatch] New version (-02) of draft-mohali-dispatch-originating-cdiv-parameter X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2016 13:40:24 -0000 SGksDQoNCkkndmUgYWRkZWQgaW5kaWNhdGlvbiBpbnRvIEFCTkYgc2VjdGlvbiAodHJ5aW5nIHRv IGNhdGNoIEFudG9uJ3MgY29tbWVudCksIHJlbW92ZWQgdGhlIGJyYWNrZXRzIGluIHRoZSBBYnN0 cmFjdCBhbmQgZmV3IG90aGVyIGVkaXRvcmlhbCBjaGFuZ2VzIGluIHRoaXMgbmV3IHZlcnNpb24g KC0wMikgb2YgdGhlIGRyYWZ0Lg0KVVJMOiAgICAgICAgICAgIGh0dHBzOi8vd3d3LmlldGYub3Jn L2ludGVybmV0LWRyYWZ0cy9kcmFmdC1tb2hhbGktZGlzcGF0Y2gtb3JpZ2luYXRpbmctY2Rpdi1w YXJhbWV0ZXItMDIudHh0DQoNCg0KQmVzdCBSZWdhcmRzLA0KTWFyaWFubmUNCgpfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCgpD ZSBtZXNzYWdlIGV0IHNlcyBwaWVjZXMgam9pbnRlcyBwZXV2ZW50IGNvbnRlbmlyIGRlcyBpbmZv cm1hdGlvbnMgY29uZmlkZW50aWVsbGVzIG91IHByaXZpbGVnaWVlcyBldCBuZSBkb2l2ZW50IGRv bmMKcGFzIGV0cmUgZGlmZnVzZXMsIGV4cGxvaXRlcyBvdSBjb3BpZXMgc2FucyBhdXRvcmlzYXRp b24uIFNpIHZvdXMgYXZleiByZWN1IGNlIG1lc3NhZ2UgcGFyIGVycmV1ciwgdmV1aWxsZXogbGUg c2lnbmFsZXIKYSBsJ2V4cGVkaXRldXIgZXQgbGUgZGV0cnVpcmUgYWluc2kgcXVlIGxlcyBwaWVj ZXMgam9pbnRlcy4gTGVzIG1lc3NhZ2VzIGVsZWN0cm9uaXF1ZXMgZXRhbnQgc3VzY2VwdGlibGVz IGQnYWx0ZXJhdGlvbiwKT3JhbmdlIGRlY2xpbmUgdG91dGUgcmVzcG9uc2FiaWxpdGUgc2kgY2Ug bWVzc2FnZSBhIGV0ZSBhbHRlcmUsIGRlZm9ybWUgb3UgZmFsc2lmaWUuIE1lcmNpLgoKVGhpcyBt ZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMgbWF5IGNvbnRhaW4gY29uZmlkZW50aWFsIG9yIHBy aXZpbGVnZWQgaW5mb3JtYXRpb24gdGhhdCBtYXkgYmUgcHJvdGVjdGVkIGJ5IGxhdzsKdGhleSBz aG91bGQgbm90IGJlIGRpc3RyaWJ1dGVkLCB1c2VkIG9yIGNvcGllZCB3aXRob3V0IGF1dGhvcmlz YXRpb24uCklmIHlvdSBoYXZlIHJlY2VpdmVkIHRoaXMgZW1haWwgaW4gZXJyb3IsIHBsZWFzZSBu b3RpZnkgdGhlIHNlbmRlciBhbmQgZGVsZXRlIHRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1l bnRzLgpBcyBlbWFpbHMgbWF5IGJlIGFsdGVyZWQsIE9yYW5nZSBpcyBub3QgbGlhYmxlIGZvciBt ZXNzYWdlcyB0aGF0IGhhdmUgYmVlbiBtb2RpZmllZCwgY2hhbmdlZCBvciBmYWxzaWZpZWQuClRo YW5rIHlvdS4KCg== From nobody Fri Sep 30 18:03:37 2016 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 60D9D12B156 for ; Fri, 30 Sep 2016 18:03:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.516 X-Spam-Level: X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fccoffice.onmicrosoft.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 zsl5FduBn_yK for ; Fri, 30 Sep 2016 18:03:32 -0700 (PDT) Received: from DC-IP-2.fcc.gov (dc-ip-2.fcc.gov [192.104.54.91]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A77A12B179 for ; Fri, 30 Sep 2016 18:03:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fccoffice.onmicrosoft.com; s=selector1-fcc-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=pvI7UQWWFedwSze7t1s7zveBfrXqi00EWp8+XbubzBY=; b=gZxhqqdx49/6IabB8XSdmKZiVaZO43L0QEaKgLs8O8XAXAPpKN+CLzMtDb4m960a4H2BeRJ0UjwaXpyU+41/9K2TofT7bFFg4yTWw+YnCX9ao9LEr9+RqjQzmDHnhrn5OztseDas25quHpoenh5+eeblbh7nyW/IqhNVjUP4oIc= From: Henning Schulzrinne To: "dispatch@ietf.org" Thread-Topic: Two new VoIP spam drafts Thread-Index: AQHSG36WIrGP/9eHl0+bp0jA+s/icw== Date: Sat, 1 Oct 2016 01:03:28 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Henning.Schulzrinne@fcc.gov; x-ms-office365-filtering-correlation-id: cdf47181-6adb-45f1-8d34-08d3e996c116 x-microsoft-exchange-diagnostics: 1; CY1PR09MB0636; 6:V9ylQljKxTmDvrhhclAYcy6YvCpjFCM0420fFGcF5waJEkSsr/HV8a+3H+XLjGRontbPl9uU0ZnBEPst5DIh1WqGts0inn4GOJWKm3suDaaIwIuBX92/B1XF0+9kFjh3bDbrktHdAjSV5s/K+33DhReLEbDogpLICwMoLBuH/9EDySIXtLP6Lu9hVkrrJF0f5xLYcK4fQUv3Tadvow6lQsDXSL73osA6Bn/yLWsLiSgqZpsya5Si6givYm0Ot/8uH+ouE8ZBCjiYtggEazcHZVyrtGLkrfAITtCwkRzmxIg=; 5:4O2igdIUwos5OJNIbgRQFD8EBbJYWYgZbjSF5zpYttdZP2h3KzgRi1MGEkTrekEPe0jhj6hPbsuD1mpBW5/l84HeWVHuZoaQvJ0SBTzkzfJt6cyXdwwHhd6olGd37KEGyrtnKT7O2wKiVtlrLWj5/A==; 24:OXagz9uvIkBkPvIyO6JteFSEat9sd4uNNZQkCSXgzBdytgB1vFLoCFwf6YI94xLpHx8fjmdUFS9nIWAJdCmK8wyqOlzfJR9DZxtUrh/klpE=; 7:paQ4ErPO2PhDYDd7nMhZ2H9XCM8igCIq7aXC55uOC/mYT2T+jT9sPKg8ij4U7oXkfdqhu8NVAX/tAxJQf293t1frBkpzgaEe49fODvqa2JEwIQGgPBRJKc+nhv3PP96YTu27Xo4qz3SbYgDS0zG+pfAXQGzvR7dOw/TRc0yAm0yBb3pbKfIPKt7ky5CIAc646Q1TqozEh39SDhvN2mmy82jfl7VIH9WUKRzZEEk7h2aro44x55UBy5Ssl5xBOX9HIm+ZEIk/pXuezb48brlzMAjj+Wurff221+kXGdqMsPuLaKKpU8M7o/3zVUmn7O+5 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR09MB0636; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(120809045254105)(231250463719595); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:CY1PR09MB0636; BCL:0; PCL:0; RULEID:; SRVR:CY1PR09MB0636; x-forefront-prvs: 00826B6158 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(189002)(199003)(19580395003)(9686002)(450100001)(86362001)(189998001)(122556002)(101416001)(1730700003)(54356999)(81156014)(6916009)(81166006)(33656002)(76576001)(8676002)(110136003)(50986999)(19625215002)(5660300001)(16236675004)(7696004)(19617315012)(2906002)(586003)(3846002)(5640700001)(102836003)(107886002)(2900100001)(8936002)(74316002)(6116002)(10400500002)(7906003)(15975445007)(77096005)(7846002)(7736002)(87936001)(97736004)(106356001)(106116001)(66066001)(3660700001)(19627405001)(11100500001)(68736007)(5002640100001)(105586002)(99286002)(2501003)(229853001)(92566002)(2351001)(3280700002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR09MB0636; H:CY1PR09MB0634.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: fcc.gov does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_CY1PR09MB0634FFF59519E8DD62DE4FC0EAC00CY1PR09MB0634namp_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2016 01:03:28.1697 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72970aed-3669-4ca8-b960-dd016bc72973 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR09MB0636 X-OriginatorOrg: fcc.gov Archived-At: Subject: [dispatch] Two new VoIP spam drafts X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2016 01:03:35 -0000 --_000_CY1PR09MB0634FFF59519E8DD62DE4FC0EAC00CY1PR09MB0634namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In collaboration with members of the Robocall Strike Force (https://www.fcc= .gov/news-events/events/2016/08/first-meeting-industry-led-robocall-strike-= force), I have submitted two I-D's: https://datatracker.ietf.org/doc/draft-schulzrinne-dispatch-status-unwanted= / https://datatracker.ietf.org/doc/draft-schulzrinne-dispatch-callinfo-spam/ that fill in operational needs for dealing with SIP spam. The first defines= a new status code (666) that users can use to mark unwanted calls, either = as a response code to an INVITE or in a Reason header in a BYE response. (T= his will likely be supplemented in practice by API-based mechanisms for pos= t-call spam reports.) The second defines a set of Call-Info parameters that allow the carrier or = other UE-trusted SIP entity in the path to indicate the spam probability, t= ype of call and other related information that will allow the UE and user t= o make better call handling decisions. This complements the 'verstat' work being submitted to 3GPP (by others), fo= r indicating the level of trust in the From/PAI tel URI. Both are obviously pretty drafty, so comments on the approach are particula= rly appreciated. Henning --_000_CY1PR09MB0634FFF59519E8DD62DE4FC0EAC00CY1PR09MB0634namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

In collaboration with members of the Robocall Strike Force (https://www.fcc.gov/news-events/events/2016/08/first-meeting-ind= ustry-led-robocall-strike-force), I have submitted two I-D's:


https://datatracker.ietf.org/doc/draft-schulzrinne-dispatch-status-u= nwanted/

https://datatracker.ietf.org/doc/draft-schulzrinne-dispatch-callinfo-s= pam/


that fill in operational needs for dealing with SIP spam. The first defi= nes a new status code (666) that users can use to mark unwanted calls, eith= er as a response code to an INVITE or in a Reason header in a BYE response.= (This will likely be supplemented in practice by API-based mechanisms for post-call spam reports.)


The second defines a set of Call-Info parameters that allow the carrier = or other UE-trusted SIP entity in the path to indicate the spam probability= , type of call and other related information that will allow the UE and use= r to make better call handling decisions.


This complements the 'verstat' work being submitted to 3GPP (by others),= for indicating the level of trust in the From/PAI tel URI.


Both are obviously pretty drafty, so comments on the approach are partic= ularly appreciated.


Henning

--_000_CY1PR09MB0634FFF59519E8DD62DE4FC0EAC00CY1PR09MB0634namp_-- From nobody Fri Sep 30 19:37:02 2016 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 5B9B712B1DE for ; Fri, 30 Sep 2016 19:37:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.935 X-Spam-Level: X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 rszvLtuSG0Ip for ; Fri, 30 Sep 2016 19:36:59 -0700 (PDT) Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (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 B1BB212B1DC for ; Fri, 30 Sep 2016 19:36:59 -0700 (PDT) Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-11v.sys.comcast.net with SMTP id qAAWbvhhZlSxsqAAcb9S8D; Sat, 01 Oct 2016 02:36:58 +0000 Received: from [192.168.1.110] ([73.186.127.100]) by resomta-ch2-19v.sys.comcast.net with SMTP id qAAbb6ErQlRdoqAAbbvIdz; Sat, 01 Oct 2016 02:36:58 +0000 To: dispatch@ietf.org References: From: Paul Kyzivat Message-ID: Date: Fri, 30 Sep 2016 22:36:57 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfLMO7TZFW7oNpJDyfIqG2gKS+ghUI7q6xUJoq5LafW4qRNDkaOQEWNwd+hYxrwFwecgilwPNnNJIQagXqAypmg5CkUu3tPzQll0/jIdOiJB2tQclbOgx ZCJwQ2SY4F3nXcc+514eIjIFUOydn1Vd/CyRs71fLJIjuitOb6Xg5ZfjcJrnq30UurZQ6HXgsaJc1Q== Archived-At: Subject: Re: [dispatch] draft-schulzrinne-dispatch-status-unwanted X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2016 02:37:01 -0000 Audacious move choosing 666! I want to verify that it is crystal clear that the meaning of this response is that requests (often calls) from this caller are unwanted, rather than simply that this *call* is unwanted. At the time of call initiation there is of course little else that the callee has to go on to reject the call this way. But I guess I could imagine a UA that is intended only for originating calls, that considers *all* incoming calls to be undesirable, regardless of caller. In that case it would be bad to use 666 if that then put the caller on a list as an undesirable caller. And of course this code can be used with Reason to signify displeasure with a call after it has been answered. At that point there may be a wider range of reasons to object to the call. E.g., the subject matter is objectionable, the caller is identifiable and objectionable even though coming from a usually unobjectionable number, etc. It isn't necessary to boil the ocean here covering all the cases. I just want to make certain the all those using this code have a common understanding of the semantics. Thanks, Paul On 9/30/16 9:03 PM, Henning Schulzrinne wrote: > In collaboration with members of the Robocall Strike Force > (https://www.fcc.gov/news-events/events/2016/08/first-meeting-industry-led-robocall-strike-force), > I have submitted two I-D's: > > > https://datatracker.ietf.org/doc/draft-schulzrinne-dispatch-status-unwanted/ > > https://datatracker.ietf.org/doc/draft-schulzrinne-dispatch-callinfo-spam/ > > > that fill in operational needs for dealing with SIP spam. The first > defines a new status code (666) that users can use to mark unwanted > calls, either as a response code to an INVITE or in a Reason header in a > BYE response. (This will likely be supplemented in practice by API-based > mechanisms for post-call spam reports.) > > > The second defines a set of Call-Info parameters that allow the carrier > or other UE-trusted SIP entity in the path to indicate the spam > probability, type of call and other related information that will allow > the UE and user to make better call handling decisions. > > > This complements the 'verstat' work being submitted to 3GPP (by others), > for indicating the level of trust in the From/PAI tel URI. > > > Both are obviously pretty drafty, so comments on the approach are > particularly appreciated. > > > Henning > > > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > From nobody Fri Sep 30 19:51:14 2016 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 0BB7712B1A1 for ; Fri, 30 Sep 2016 19:51:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.516 X-Spam-Level: X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fccoffice.onmicrosoft.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 qEx4d7QpTVwd for ; Fri, 30 Sep 2016 19:51:10 -0700 (PDT) Received: from DC-IP-1.fcc.gov (dc-ip-1.fcc.gov [192.104.54.97]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75B9312B034 for ; Fri, 30 Sep 2016 19:51:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fccoffice.onmicrosoft.com; s=selector1-fcc-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=GeCX4fMQ5Xj8TIlGYpr2iFk0GcQ3ujvQRyXc5o5hzaQ=; b=DlAGCUlwbWQXzY3HjIqXsaDqLnOfRrR8uXFWqNXnUGLfmbFeTpHpk7olPTphA1G7LIpJl3VHDZMKRugtvZwdNse7u0jyUiillD7ahHTrzIRabXzcXIrnWnsAdOFwzIlkU8dIVn1YeD7J17iI8PkPK7XYudTqvEolzxy6aiRO0ag= From: Henning Schulzrinne To: Paul Kyzivat , "dispatch@ietf.org" Thread-Topic: [dispatch] draft-schulzrinne-dispatch-status-unwanted Thread-Index: AQHSG4y2GZvJepLQu06G9vFQbuxMyaCS4uS1 Date: Sat, 1 Oct 2016 02:51:05 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Henning.Schulzrinne@fcc.gov; x-ms-office365-filtering-correlation-id: ff308b58-7f4b-4b05-8698-08d3e9a5ca41 x-microsoft-exchange-diagnostics: 1; CY1PR09MB0634; 6:PMqF4AG3JAvZWvU55sCrXYVpMCyzuMCSCjzKUKduiml1/7OB+5rOJok+fiSPTDFXgewb0G7LhiTfKuRiOAfS6dBLdgxaD8t6lX/70osmNOXbd9TRezIt9lCq2kjfwh02DNwTJIIItFLKn5ibkZJ5A6uSs9kEez4M8v10+/1YBPJdOPNJklI7/8QwuH8x5CAwF4nbDgW0srFaKsuap7EbxCCX59uOjpdtZbQOIo4djoBwdLpB9/u02j8lFCZaGqRNLRNJPVE2ymqUoBaV+GgOwHMKvnPDIA52RdtGOf1yGVo=; 5:kKSE6XCFT/I6S6peKNoadnR4jWL9VYCQR8k/eJfWFCppuJQ7ZNLq8T/5///3btqBsCGOFp9LVL9bsiQ4m/oS8t0Sw7sBO8ZhZ4c+gm3n0kw2AeYzmjm9gdw9FfmWjcs8IKjWRdS4dP2FWvY9POTIHw==; 24:yV6YSpIjI4Bu6dlDbvqg+ukuK44CZLlJPHNMtgP5Jg0HX4DQumnZ39d4KZmHpv0av8QmrSf1nhpfp0p95SDHpPq3mD8jYKhr5rZoWyETEbo=; 7:KQq8gN1MdCNLeyI5ZWMRcKzjsMqQwI3exowNVFf3i2M/rTUTwkiWGBhi5ZgN2T9wGQXpAKAp/L8ZEh/m9u/TcFbGlUGlEyuLYg43SuPPijWoQ80TSfD6sHwQLPkRMod1BafUCyvc6hlAISx1J03bpnXypFGaWT99vfeMovQZNChoteB0YS8uppmG3DTYuSc6XEkOCcRGd4uL2P0/inCb8JUV0QW89DygTgyXeJIbvW1IyRFqV7aHQ7Z3+Jjqxk4L1fdG0Ym9dJOuNLtYtf2ZxOkYFDuHAHDTG44k/GUiiZcYb5ETQ1eYjJ3EUDyj7eZi x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR09MB0634; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:CY1PR09MB0634; BCL:0; PCL:0; RULEID:; SRVR:CY1PR09MB0634; x-forefront-prvs: 00826B6158 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(199003)(377454003)(189002)(9686002)(6116002)(3846002)(3660700001)(189998001)(102836003)(76176999)(2171001)(107886002)(586003)(5002640100001)(54356999)(3280700002)(2906002)(66066001)(19580405001)(16236675004)(19580395003)(99286002)(122556002)(106356001)(68736007)(81156014)(8676002)(19627405001)(81166006)(3900700001)(230783001)(2900100001)(19625215002)(105586002)(106116001)(101416001)(77096005)(2950100002)(50986999)(33656002)(10400500002)(8936002)(97736004)(86362001)(92566002)(5660300001)(7736002)(74316002)(2501003)(87936001)(7696004)(5001770100001)(7846002)(11100500001)(76576001)(26123001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR09MB0634; H:CY1PR09MB0634.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: fcc.gov does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_CY1PR09MB0634216774589A97F659B8F6EAC00CY1PR09MB0634namp_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2016 02:51:05.9778 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72970aed-3669-4ca8-b960-dd016bc72973 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR09MB0634 X-OriginatorOrg: fcc.gov Archived-At: Subject: Re: [dispatch] draft-schulzrinne-dispatch-status-unwanted X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2016 02:51:13 -0000 --_000_CY1PR09MB0634216774589A97F659B8F6EAC00CY1PR09MB0634namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Yes, this is meant to indicate that the calls from that caller are unwanted= . Given that numbers get re-assigned and that sometimes people hit the wron= g button (such as hitting the "spam" button in gmail when I meant delete), = this should presumably be treated more as a statistical indicator. I didn't= want to be too prescriptive here; for example, it is possible that such ca= lls, if they are not yet on a global blacklist, end up in the equivalent of= the email spam folder, i.e., voicemail, or that, again mimicking email, yo= u get a text message indicating calls that got this treatment, just in case= this was a mistake. I'll add a sentence about the caller being unwanted. I had considered adding Call-Info "type" information to allow the called pa= rty to provide more information, but I doubt that most users will want to m= ake in-depth selections of the nature of the badness when they just want to= get rid of the call. More detailed feedback seems more appropriate for a p= ost-call app-style response (and existing robocall filtering apps seem to a= llow this type of labeling). Call-Info can't be used in a BYE, so that method doesn't quite work. My inclination is to keep it simple for now, and consider adding more struc= tured information as a parameter separately and later if there's need. Henning ________________________________ From: dispatch on behalf of Paul Kyzivat Sent: Friday, September 30, 2016 10:36 PM To: dispatch@ietf.org Subject: Re: [dispatch] draft-schulzrinne-dispatch-status-unwanted Audacious move choosing 666! I want to verify that it is crystal clear that the meaning of this response is that requests (often calls) from this caller are unwanted, rather than simply that this *call* is unwanted. At the time of call initiation there is of course little else that the callee has to go on to reject the call this way. But I guess I could imagine a UA that is intended only for originating calls, that considers *all* incoming calls to be undesirable, regardless of caller. In that case it would be bad to use 666 if that then put the caller on a list as an undesirable caller. And of course this code can be used with Reason to signify displeasure with a call after it has been answered. At that point there may be a wider range of reasons to object to the call. E.g., the subject matter is objectionable, the caller is identifiable and objectionable even though coming from a usually unobjectionable number, etc. It isn't necessary to boil the ocean here covering all the cases. I just want to make certain the all those using this code have a common understanding of the semantics. Thanks, Paul --_000_CY1PR09MB0634216774589A97F659B8F6EAC00CY1PR09MB0634namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Yes, this is meant to indicate that the calls from that caller are unwan= ted. Given that numbers get re-assigned and that sometimes people hit the w= rong button (such as hitting the "spam" button in gmail when I me= ant delete), this should presumably be treated more as a statistical indicator. I didn't want to be too prescriptive here= ; for example, it is possible that such calls, if they are not yet on a glo= bal blacklist, end up in the equivalent of the email spam folder, i.e., voi= cemail, or that, again mimicking email, you get a text message indicating calls that got this treatment, ju= st in case this was a mistake.


I'll add a sentence about the caller being unwanted.


I had considered adding Call-Info "type" information to allow = the called party to provide more information, but I doubt that most users w= ill want to make in-depth selections of the nature of the badness when they= just want to get rid of the call. More detailed feedback seems more appropriate for a post-call app-style response (and ex= isting robocall filtering apps seem to allow this type of labeling).


Call-Info can't be used in a BYE, so that method doesn't quite work.


My inclination is to keep it simple for now, and consider adding more st= ructured information as a parameter separately and later if there's need.
Henning

From: dispatch <dispat= ch-bounces@ietf.org> on behalf of Paul Kyzivat <pkyzivat@alum.mit.edu= >
Sent: Friday, September 30, 2016 10:36 PM
To: dispatch@ietf.org
Subject: Re: [dispatch] draft-schulzrinne-dispatch-status-unwanted
 
Audacious move choosing 666!

I want to verify that it is crystal clear that the meaning of this
response is that requests (often calls) from this caller are unwanted,
rather than simply that this *call* is unwanted.

At the time of call initiation there is of course little else that the
callee has to go on to reject the call this way. But I guess I could
imagine a UA that is intended only for originating calls, that considers *all* incoming calls to be undesirable, regardless of caller. In that
case it would be bad to use 666 if that then put the caller on a list as an undesirable caller.

And of course this code can be used with Reason to signify displeasure
with a call after it has been answered. At that point there may be a
wider range of reasons to object to the call. E.g., the subject matter
is objectionable, the caller is identifiable and objectionable even
though coming from a usually unobjectionable number, etc.

It isn't necessary to boil the ocean here covering all the cases. I just want to make certain the all those using this code have a common
understanding of the semantics.

        Thanks,
        Paul


--_000_CY1PR09MB0634216774589A97F659B8F6EAC00CY1PR09MB0634namp_-- From nobody Fri Sep 30 20:24:55 2016 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 C042F12B1E7 for ; Fri, 30 Sep 2016 20:24:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.935 X-Spam-Level: X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 3Y2h6HWKENPe for ; Fri, 30 Sep 2016 20:24:52 -0700 (PDT) Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (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 65DC512B010 for ; Fri, 30 Sep 2016 20:24:51 -0700 (PDT) Received: from resomta-po-08v.sys.comcast.net ([96.114.154.232]) by resqmta-po-09v.sys.comcast.net with SMTP id qAuvbrQKFS0FEqAuxbG752; Sat, 01 Oct 2016 03:24:51 +0000 Received: from [192.168.1.110] ([73.186.127.100]) by resomta-po-08v.sys.comcast.net with SMTP id qAuwb6PaynH9OqAuwbRmnt; Sat, 01 Oct 2016 03:24:51 +0000 To: Henning Schulzrinne , "dispatch@ietf.org" References: From: Paul Kyzivat Message-ID: Date: Fri, 30 Sep 2016 23:24:49 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfBz7H9pjheMzGektMF1Ecarx84nC6sPwBYutVxF4+l425aotZtEBgl2G9AjvRCIWqYRj3HqW562kfKq7f19u6xqQnj9aKn03yQzXg/MnJUfSnLG9n2Yt 66BWyKXR7Ox8B6/p+sx7gRTnYJpqNIJk7pgexl6RxDvXg71lK13gK794Kup9iRMZBVDas4E7B8YNzcu/rjd2x+/z9vQ9bPZ5V8I= Archived-At: Subject: Re: [dispatch] draft-schulzrinne-dispatch-status-unwanted X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2016 03:24:54 -0000 On 9/30/16 10:51 PM, Henning Schulzrinne wrote: > Yes, this is meant to indicate that the calls from that caller are > unwanted. Given that numbers get re-assigned and that sometimes people > hit the wrong button (such as hitting the "spam" button in gmail when I > meant delete), this should presumably be treated more as a statistical > indicator. I didn't want to be too prescriptive here; for example, it is > possible that such calls, if they are not yet on a global blacklist, end > up in the equivalent of the email spam folder, i.e., voicemail, or that, > again mimicking email, you get a text message indicating calls that got > this treatment, just in case this was a mistake. > > > I'll add a sentence about the caller being unwanted. > > > I had considered adding Call-Info "type" information to allow the called > party to provide more information, but I doubt that most users will want > to make in-depth selections of the nature of the badness when they just > want to get rid of the call. More detailed feedback seems more > appropriate for a post-call app-style response (and existing robocall > filtering apps seem to allow this type of labeling). > > > Call-Info can't be used in a BYE, so that method doesn't quite work. > > > My inclination is to keep it simple for now, and consider adding more > structured information as a parameter separately and later if there's need. I just want to ensure that all the users of this are on the same page regarding its meaning. How it is institutionalized is more important than what the exact wording is in this document. Users are going to push a button on their phone to reject the call. (Probably the same one that is there now.) What they mean and how that is used had better be in agreement. Thanks, Paul > Henning > ------------------------------------------------------------------------ > *From:* dispatch on behalf of Paul Kyzivat > > *Sent:* Friday, September 30, 2016 10:36 PM > *To:* dispatch@ietf.org > *Subject:* Re: [dispatch] draft-schulzrinne-dispatch-status-unwanted > > Audacious move choosing 666! > > I want to verify that it is crystal clear that the meaning of this > response is that requests (often calls) from this caller are unwanted, > rather than simply that this *call* is unwanted. > > At the time of call initiation there is of course little else that the > callee has to go on to reject the call this way. But I guess I could > imagine a UA that is intended only for originating calls, that considers > *all* incoming calls to be undesirable, regardless of caller. In that > case it would be bad to use 666 if that then put the caller on a list as > an undesirable caller. > > And of course this code can be used with Reason to signify displeasure > with a call after it has been answered. At that point there may be a > wider range of reasons to object to the call. E.g., the subject matter > is objectionable, the caller is identifiable and objectionable even > though coming from a usually unobjectionable number, etc. > > It isn't necessary to boil the ocean here covering all the cases. I just > want to make certain the all those using this code have a common > understanding of the semantics. > > Thanks, > Paul > > From nobody Fri Sep 30 20:31:33 2016 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 15F8012B1F4 for ; Fri, 30 Sep 2016 20:31:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.516 X-Spam-Level: X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fccoffice.onmicrosoft.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 WGG1v-tvjbRa for ; Fri, 30 Sep 2016 20:31:29 -0700 (PDT) Received: from DC-IP-2.fcc.gov (dc-ip-2.fcc.gov [192.104.54.91]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9CAC12B010 for ; Fri, 30 Sep 2016 20:31:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fccoffice.onmicrosoft.com; s=selector1-fcc-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3dUnkNV/cmwsBiahg8b769MPO4nQw0Xj6PO8F+rwKU0=; b=wgykM8W00be57XVP+n5tPPqLfQJbD/BEA3yB03ctll49OdRHdBvSsQT73y9WK8us2ignQ5zGRxbpadtni+vQ3bhVELocZLFtv/zl2RT7zaDV459Y6c+cbXJNRgzzWWaRAwUL7H4J4L2q6tWwV+CM1uMkyEoFSNepLiwpdiBcYkg= From: Henning Schulzrinne To: Paul Kyzivat , "dispatch@ietf.org" Thread-Topic: [dispatch] draft-schulzrinne-dispatch-status-unwanted Thread-Index: AQHSG4y2GZvJepLQu06G9vFQbuxMyaCS4uS1gAAMvYCAAAArBw== Date: Sat, 1 Oct 2016 03:31:24 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Henning.Schulzrinne@fcc.gov; x-ms-office365-filtering-correlation-id: 9da188f5-79fb-4669-e960-08d3e9ab6c07 x-microsoft-exchange-diagnostics: 1; CY1PR09MB0634; 6:ur16A+8yG84dY9sN9pUN3k57rMazX1ESSgg3rQTdv2bM+8AAfu/hemDLnNE8Wq3n9o5JP6xRLTl0uuoVOVUPJT8dB8ZUYp2tJY/+rZUa9hResRHNV6jcI4s8SDxTjZjNjcFppfh+GlQE9HdJHb29dMHVD/6aHEijPcIUsjXUYZky0i5wxX4ieYgdGMU3Do1hWuxTklWy4BUZez/ia9c3ktgpaZ2BKaGYyrAVN55TLgb2xELHAtGlT1L0eB/SPDsobzPTukIc3jY8QW3IM+m4oOlzySrBo4cotWGCwLnbTAg=; 5:g/vYIjXRRlHV2OruODvSoQqeojmbEz8lXfZZCvbUNfq/IsBQIzaEsunF7tNvnvyPrAv78N2OoLM6JlQ2QPxIcgwusVEKZNF9+F96l+NxoGhzahlcZVpnY5xYqNfC+pIQ0buWO+lM9PoaSNgmalpHFQ==; 24:vt+bB6EnOf6hlpsPj4hxjcRBACUNv7+6vl12OBeFkFjtMn7zXUvppX3AeLt4fXWt/mRxVMt8uPGAcfqy0cy2eh9spRrfkHLUAuOTBQ3jQJY=; 7:nfnmyH468DKKWVRrcdKDI1ZbtkrKkDuhy7kTLw+iBfCYaxE5PSdNHX+1SgQh4qSOV5Fqp9Y8sCMKkk7gt5M0qFcDn5pm+dqPnK/xUuulvfs66t2Hys/fRNimCwOr06IHs41HO1vCCvBIpTCW/OKc5/bg4oSVMN4RGpO1hN0OcYoLXp2zzs+UzfxajtzKW225E155lVJf/9ypIfcPyPUNvizGsat3lYEfZLdrQX5dHCyHsR8tBdU3higFTj7+Wf7Oqh/svVCYsyyzzv68sb95jHJqkUKeUrEPbSPPMaaCm9raGtchGnPinkXecj+0Gqg4 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR09MB0634; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:CY1PR09MB0634; BCL:0; PCL:0; RULEID:; SRVR:CY1PR09MB0634; x-forefront-prvs: 00826B6158 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(189002)(199003)(377454003)(10400500002)(33656002)(50986999)(86362001)(8936002)(97736004)(101416001)(2950100002)(77096005)(7696004)(5001770100001)(87936001)(76576001)(11100500001)(7846002)(7736002)(92566002)(5660300001)(2501003)(74316002)(107886002)(586003)(3280700002)(2906002)(66066001)(5002640100001)(54356999)(3660700001)(189998001)(102836003)(3846002)(9686002)(6116002)(2171001)(76176999)(19627405001)(8676002)(81166006)(3900700001)(81156014)(105586002)(19625215002)(230783001)(2900100001)(19580395003)(99286002)(16236675004)(19580405001)(93886004)(68736007)(106356001)(122556002)(106116001)(26123001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR09MB0634; H:CY1PR09MB0634.namprd09.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: fcc.gov does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_CY1PR09MB0634E99418D77B62AB9BB1A4EAC00CY1PR09MB0634namp_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Oct 2016 03:31:24.6966 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72970aed-3669-4ca8-b960-dd016bc72973 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR09MB0634 X-OriginatorOrg: fcc.gov Archived-At: Subject: Re: [dispatch] draft-schulzrinne-dispatch-status-unwanted X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2016 03:31:31 -0000 --_000_CY1PR09MB0634E99418D77B62AB9BB1A4EAC00CY1PR09MB0634namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'd envision two hang-up buttons: the usual one and the "spam" one. Some th= ird-party Android dialer apps already do something like this, and Nougat ap= parently has a related feature. ________________________________ From: Paul Kyzivat Sent: Friday, September 30, 2016 11:24 PM To: Henning Schulzrinne; dispatch@ietf.org Subject: Re: [dispatch] draft-schulzrinne-dispatch-status-unwanted I just want to ensure that all the users of this are on the same page regarding its meaning. How it is institutionalized is more important than what the exact wording is in this document. Users are going to push a button on their phone to reject the call. (Probably the same one that is there now.) What they mean and how that is used had better be in agreement. Thanks, Paul --_000_CY1PR09MB0634E99418D77B62AB9BB1A4EAC00CY1PR09MB0634namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I'd envision two hang-up buttons: the usual one and the "spam"= one. Some third-party Android dialer apps already do something l= ike this, and Nougat apparently has a related feature.


From: Paul Kyzivat <pk= yzivat@alum.mit.edu>
Sent: Friday, September 30, 2016 11:24 PM
To: Henning Schulzrinne; dispatch@ietf.org
Subject: Re: [dispatch] draft-schulzrinne-dispatch-status-unwanted

I just want to ensure that all the users of this a= re on the same page
regarding its meaning. How it is institutionalized is more important
than what the exact wording is in this document. Users are going to push a button on their phone to reject the call. (Probably the same one that is there now.) What they mean and how that is used had better be in
agreement.

        Thanks,
        Paul
--_000_CY1PR09MB0634E99418D77B62AB9BB1A4EAC00CY1PR09MB0634namp_--