
From nobody Mon Jul  3 13:12:43 2017
Return-Path: <internet-drafts@ietf.org>
X-Original-To: modern@ietf.org
Delivered-To: modern@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B753C1252BA; Mon,  3 Jul 2017 13:12:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: modern@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149911276173.22803.12558230957182189993@ietfa.amsl.com>
Date: Mon, 03 Jul 2017 13:12:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/3FmVAbCtlPfn5BNvAmOa-duMfNY>
Subject: [Modern] I-D Action: draft-ietf-modern-problem-framework-03.txt
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 20:12:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers of the IETF.

        Title           : Modern Problem Statement, Use Cases, and Framework
        Authors         : Jon Peterson
                          Tom McGarry
	Filename        : draft-ietf-modern-problem-framework-03.txt
	Pages           : 23
	Date            : 2017-07-03

Abstract:
   The functions of the public switched telephone network (PSTN) are
   rapidly migrating to the Internet.  This is generating new
   requirements for many traditional elements of the PSTN, including
   telephone numbers (TNs).  TNs no longer serve simply as telephone
   routing addresses: they are now identifiers which may be used by
   Internet-based services for a variety of purposes including session
   establishment, identity verification, and service enablement.  This
   problem statement examines how the existing tools for allocating and
   managing telephone numbers do not align with the use cases of the
   Internet environment, and proposes a framework for Internet-based
   services relying on TNs.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-modern-problem-framework/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-modern-problem-framework-03
https://datatracker.ietf.org/doc/html/draft-ietf-modern-problem-framework-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-modern-problem-framework-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun Jul 16 05:20:42 2017
Return-Path: <prvs=2370e5e3cb=jon.peterson@team.neustar>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8851E131468 for <modern@ietfa.amsl.com>; Sun, 16 Jul 2017 05:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=team.neustar
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 bCmdUwFvdYBp for <modern@ietfa.amsl.com>; Sun, 16 Jul 2017 05:20:38 -0700 (PDT)
Received: from mx0b-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (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 303FC1318EC for <modern@ietf.org>; Sun, 16 Jul 2017 05:20:38 -0700 (PDT)
Received: from pps.filterd (m0078664.ppops.net [127.0.0.1]) by mx0a-0018ba01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v6GCDUCa029154 for <modern@ietf.org>; Sun, 16 Jul 2017 08:20:36 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=team.neustar; h=from : to : subject : date : message-id : content-type : mime-version; s=selector1; bh=DJpArpPifcVi1ZvYIef1e1PR+hiFO9ZQkLJYMhHlQME=; b=noNDbkUj8akkSG/Q5L9X0i8z0RWRNWMX4A898Fe/c2RmZHThN8IYHiPteThO4nFKo0Of oIeR7JHPPuMasdo2lriK5qmse+eKQYkmqUBLCGeBSQPEiB4eaFNc7QKrIxnGRa86mfL1 k/6FCitdsRGVuTUQb6lSwkkATXw5JbRi0TJPdR3rVqwLjg8VamslLHf/4UMLFkfpeEIu 0kYhTM+PcJGesF7UK/Tlvr8USNsW468WoKdajRQcGzUF76CvHfRhuCfTbxmIDxyyG1Iv iDJZlveWHPKUVmxvOZt0DZnhzJHnEwnY7sii6WvoAz+UnhcUroajGhbqVUQBezONN7YS Pg== 
Received: from stntexhc10.cis.neustar.com ([156.154.17.216]) by mx0a-0018ba01.pphosted.com with ESMTP id 2bqdpvjbg4-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT) for <modern@ietf.org>; Sun, 16 Jul 2017 08:20:36 -0400
Received: from stntexmb12.cis.neustar.com ([169.254.2.239]) by stntexhc10.cis.neustar.com ([169.254.4.65]) with mapi id 14.03.0279.002; Sun, 16 Jul 2017 08:20:35 -0400
From: "Peterson, Jon" <jon.peterson@team.neustar>
To: "modern@ietf.org" <modern@ietf.org>
Thread-Topic: modern meeting discussion
Thread-Index: AQHS/i3spxzn04CvwEydFOBWIWz+jQ==
Date: Sun, 16 Jul 2017 12:20:34 +0000
Message-ID: <D590D266.1EA813%jon.peterson@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [10.96.12.35]
Content-Type: multipart/alternative; boundary="_000_D590D2661EA813jonpetersonneustarbiz_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-16_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1707160204
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/GGx4Swwh5QU3QyQU8KRTflHUHm8>
Subject: [Modern] modern meeting discussion
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jul 2017 12:20:39 -0000

--_000_D590D2661EA813jonpetersonneustarbiz_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


For the MODERN meeting this time, Chris Wendt and I put our heads together =
to try to come up with a more concrete use case that would have some immedi=
ate applicability to the industry. Lately there has been some talk in North=
 America recently about ways to share data structures that will let carrier=
s know if a number is invalid or unallocated, so that abusive calls from nu=
mbers that simply shouldn't be able to originate at all can be blocked or o=
therwise given special treatment.

Taking that as the sort of thing we hope MODERN could address, we put toget=
her this TeRI data structure for expressing that numbers are valid and allo=
cated  - this is a "whitelist" sort of approach to the problem, as it seeme=
d easier to us to share a list of numbers that are valid than it is to come=
 up with all the different ways that someone might try to structure an inva=
lid number. This is intended primarily for use with number ranges, though f=
or some existing use cases (like freephone), assignment of individual numbe=
rs is what matters, and that is probably true of some of our future use cas=
es here (like DRiP) as well.

https://tools.ietf.org/html/draft-peterson-modern-teri-valid-00

To get this into shape, I also did a bit more work fleshing out parts of Te=
RI, which has also been revised for the meeting, and I'll talk a bit about =
that as well on Friday.

Jon Peterson
Neustar, Inc.

--_000_D590D2661EA813jonpetersonneustarbiz_
Content-Type: text/html; charset="us-ascii"
Content-ID: <8469A09DBA6EFA4B84B93D114D004BC1@neustar.biz>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div><br>
</div>
<div>For the MODERN meeting this time, Chris Wendt and I put our heads toge=
ther to try to come up with a more concrete use case that would have some i=
mmediate applicability to the industry. Lately there has been some talk in =
North America recently about ways
 to share data structures that will let carriers know if a number is invali=
d or unallocated, so that abusive calls from numbers that simply shouldn't =
be able to originate at all can be blocked or otherwise given special treat=
ment.&nbsp;</div>
<div><br>
</div>
<div>Taking that as the sort of thing we hope MODERN could address, we put =
together this TeRI data structure for expressing that numbers are valid and=
 allocated &nbsp;- this is a &quot;whitelist&quot; sort of approach to the =
problem, as it seemed easier to us to share a list
 of numbers that are valid than it is to come up with all the different way=
s that someone might try to structure an invalid number. This is intended p=
rimarily for use with number ranges, though for some existing use cases (li=
ke freephone), assignment of individual
 numbers is what matters, and that is probably true of some of our future u=
se cases here (like DRiP) as well.</div>
<div><br>
</div>
<div><a href=3D"https://tools.ietf.org/html/draft-peterson-modern-teri-vali=
d-00">https://tools.ietf.org/html/draft-peterson-modern-teri-valid-00</a></=
div>
<div><br>
</div>
<div>To get this into shape, I also did a bit more work fleshing out parts =
of TeRI, which has also been revised for the meeting, and I'll talk a bit a=
bout that as well on Friday.</div>
<div><br>
</div>
<div>Jon Peterson</div>
<div>Neustar, Inc.</div>
</body>
</html>

--_000_D590D2661EA813jonpetersonneustarbiz_--


From nobody Sun Jul 16 11:38:14 2017
Return-Path: <richard@shockey.us>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92DFB12ECBD for <modern@ietfa.amsl.com>; Sun, 16 Jul 2017 11:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.699
X-Spam-Level: 
X-Spam-Status: No, score=-4.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=shockey.us
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wHrCgH22wHiN for <modern@ietfa.amsl.com>; Sun, 16 Jul 2017 11:38:09 -0700 (PDT)
Received: from qproxy3.mail.unifiedlayer.com (qproxy3-pub.mail.unifiedlayer.com [67.222.38.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3E6C129AA0 for <modern@ietf.org>; Sun, 16 Jul 2017 11:38:09 -0700 (PDT)
Received: from CMOut01 (unknown [10.0.90.82]) by qproxy3.mail.unifiedlayer.com (Postfix) with ESMTP id 36EC9D5898 for <modern@ietf.org>; Sun, 16 Jul 2017 12:38:08 -0600 (MDT)
Received: from box462.bluehost.com ([74.220.219.62]) by CMOut01 with  id lWZ41v0081MNPNq01WZ7uP; Sun, 16 Jul 2017 12:33:08 -0600
X-Authority-Analysis: v=2.2 cv=FvB1xyjq c=1 sm=1 tr=0 a=jTEj1adHphCQ5SwrTAOQMg==:117 a=jTEj1adHphCQ5SwrTAOQMg==:17 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=G3gG6ho9WtcA:10 a=jqBRFv0mrdUA:10 a=ZZnuYtJkoWoA:10 a=PeFO9FbFhS32YxYntvkA:9 a=ll-iCDY8AAAA:8 a=M0OflfRGAAAA:8 a=48vgC7mUAAAA:8 a=BnDEmklN2TBxw0FUSJgA:9 a=eWHnn2PGByrc8OjS:21 a=cJIRw92HPaG4y8xP:21 a=QEXdDO2ut3YA:10 a=ivbTfD_dPm4A:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=ldG2xuoQ9TDTbmbMMWwA:9 a=_vnImK6mG-2F5ku9:21 a=adhCKJHs7IhZlmWm:21 a=uoAb9cSOYpUi3GCw:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=VpyrLIdO_Ztbr3SWPBuH:22 a=6yl0mh0s51TKORVA8GqK:22 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us;  s=default; h=Content-type:Mime-version:Message-ID:To:From:Subject:Date: Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=UwUgI6u5p3zvhbIao6VidmBtkP7KU1FYRWMH3h5oc88=; b=BuFQvzCYx3h5uH+yJwzsr96dl2 JdcOzFlHCyt15H4opOKizW76IGTA4C5cMJbgHNHZmu+pwiI1IPRWBaKWcnAmldfWATOf0mtju6ox4 xKAo/FYObDq1CoAkpFypv5aG7;
Received: from [64.134.221.172] (port=49989 helo=[10.20.4.198]) by box462.bluehost.com with esmtpa (Exim 4.87) (envelope-from <richard@shockey.us>) id 1dWoLo-0045bD-30; Sun, 16 Jul 2017 12:33:04 -0600
User-Agent: Microsoft-MacOutlook/f.24.0.170702
Date: Sun, 16 Jul 2017 11:30:37 -0700
From: Richard Shockey <richard@shockey.us>
To: "Peterson, Jon" <jon.peterson@team.neustar>, "modern@ietf.org" <modern@ietf.org>
Message-ID: <C06D3FC8-877D-4E12-8C32-B92D95F0DFDA@shockey.us>
Thread-Topic: [Modern] modern meeting discussion
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3583049584_1450687632"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box462.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - shockey.us
X-BWhitelist: no
X-Source-IP: 64.134.221.172
X-Exim-ID: 1dWoLo-0045bD-30
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: ([10.20.4.198]) [64.134.221.172]:49989
X-Source-Auth: richard+shockey.us
X-Email-Count: 6
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NDYyLmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/wHWMQajw2vj-eeaiNuMUmeRcx6Q>
Subject: Re: [Modern] modern meeting discussion
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jul 2017 18:38:13 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3583049584_1450687632
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

=20

Well this idea has the benefit of being actually practical and deployable v=
s the useless idea of individual number allocation.=C2=A0 Useless in the sense t=
hat no carrier I know of is going to rip out their existing OSS/BSS systems =
to accommodate the original idea.

=20

The idea of white/black lists for the Do Not Originate application has meri=
t as does the idea of listing numbers that have been disconnected and recent=
ly reassigned.=C2=A0 MODERN would have to compete, potentially, other methods th=
at the NANPA and other numbering authorities could consider.

=20

The problem right now is that the spoofing industry has moved on into the f=
ully allocated range of the national numbering plans in order to increase an=
swer rates. =C2=A0=C2=A0A problem only STIR/SHAKEN can ultimately address. There is =
adequate data from the current crop of data analytics firms to support that =
thesis.=20

=20

In any event this idea does have merit and worth investigation.=20

=20

=20

=20

=20

=20

=E2=80=94=20

Richard Shockey

Shockey Consulting LLC

Chairman of the Board SIP Forum

www.shockey.us

www.sipforum.org

richard<at>shockey.us

Skype-Linkedin-Facebook =E2=80=93Twitter  rshockey101

PSTN +1 703-593-2683

=20

=20

From: Modern <modern-bounces@ietf.org> on behalf of "Peterson, Jon" <jon.pe=
terson@team.neustar>
Date: Sunday, July 16, 2017 at 5:20 AM
To: "modern@ietf.org" <modern@ietf.org>
Subject: [Modern] modern meeting discussion

=20

=20

For the MODERN meeting this time, Chris Wendt and I put our heads together =
to try to come up with a more concrete use case that would have some immedia=
te applicability to the industry. Lately there has been some talk in North A=
merica recently about ways to share data structures that will let carriers k=
now if a number is invalid or unallocated, so that abusive calls from number=
s that simply shouldn't be able to originate at all can be blocked or otherw=
ise given special treatment.=20

=20

Taking that as the sort of thing we hope MODERN could address, we put toget=
her this TeRI data structure for expressing that numbers are valid and alloc=
ated  - this is a "whitelist" sort of approach to the problem, as it seemed =
easier to us to share a list of numbers that are valid than it is to come up=
 with all the different ways that someone might try to structure an invalid =
number. This is intended primarily for use with number ranges, though for so=
me existing use cases (like freephone), assignment of individual numbers is =
what matters, and that is probably true of some of our future use cases here=
 (like DRiP) as well.

=20

https://tools.ietf.org/html/draft-peterson-modern-teri-valid-00

=20

To get this into shape, I also did a bit more work fleshing out parts of Te=
RI, which has also been revised for the meeting, and I'll talk a bit about t=
hat as well on Friday.

=20

Jon Peterson

Neustar, Inc.

_______________________________________________ Modern mailing list Modern@=
ietf.org https://www.ietf.org/mailman/listinfo/modern=20


--B_3583049584_1450687632
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DTitle c=
ontent=3D""><meta name=3DKeywords content=3D""><meta http-equiv=3DContent-Type conte=
nt=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 1=
5 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple><di=
v class=3DWordSection1><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNor=
mal>Well this idea has the benefit of being actually practical and deployabl=
e vs the useless idea of individual number allocation.=C2=A0 Useless in the sens=
e that no carrier I know of is going to rip out their existing OSS/BSS syste=
ms to accommodate the original idea.<o:p></o:p></p><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p><p class=3DMsoNormal>The idea of white/black lists for the Do N=
ot Originate application has merit as does the idea of listing numbers that =
have been disconnected and recently reassigned.=C2=A0 MODERN would have to compe=
te, potentially, other methods that the NANPA and other numbering authoritie=
s could consider.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p c=
lass=3DMsoNormal>The problem right now is that the spoofing industry has moved=
 on into the fully allocated range of the national numbering plans in order =
to increase answer rates. =C2=A0=C2=A0A problem only STIR/SHAKEN can ultimately addr=
ess. There is adequate data from the current crop of data analytics firms to=
 support that thesis. <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
><p class=3DMsoNormal>In any event this idea does have merit and worth investi=
gation. <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3D=
MsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div>=
<p class=3DMsoNormal style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-b=
ottom:1.0pt;margin-left:0in'><span style=3D'font-size:8.0pt;color:black'>=E2=80=94&n=
bsp;<o:p></o:p></span></p><div><p class=3DMsoNormalCxSpMiddle style=3D'mso-margi=
n-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;margin-left:0in;mso-add=
-space:auto'><span style=3D'font-size:8.0pt;color:black'>Richard Shockey<o:p><=
/o:p></span></p></div><div><p class=3DMsoNormalCxSpMiddle style=3D'mso-margin-to=
p-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;margin-left:0in;mso-add-spa=
ce:auto'><span style=3D'font-size:8.0pt;color:black'>Shockey Consulting LLC<o:=
p></o:p></span></p></div><div><p class=3DMsoNormalCxSpMiddle style=3D'mso-margin=
-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;margin-left:0in;mso-add-=
space:auto'><span style=3D'font-size:8.0pt;color:black'>Chairman of the Board =
SIP Forum<o:p></o:p></span></p></div><div><p class=3DMsoNormalCxSpMiddle style=
=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;margin-left:=
0in;mso-add-space:auto'><span style=3D'font-size:8.0pt;color:black'>www.shocke=
y.us<o:p></o:p></span></p></div><div><p class=3DMsoNormalCxSpMiddle style=3D'mso=
-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;margin-left:0in;m=
so-add-space:auto'><span style=3D'font-size:8.0pt;color:black'>www.sipforum.or=
g<o:p></o:p></span></p></div><div><p class=3DMsoNormalCxSpMiddle style=3D'mso-ma=
rgin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;margin-left:0in;mso-=
add-space:auto'><span style=3D'font-size:8.0pt;color:black'>richard&lt;at&gt;s=
hockey.us<o:p></o:p></span></p></div><div><p class=3DMsoNormalCxSpMiddle style=
=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;margin-left:=
0in;mso-add-space:auto'><span style=3D'font-size:8.0pt;color:black'>Skype-Link=
edin-Facebook =E2=80=93Twitter &nbsp;rshockey101<o:p></o:p></span></p></div><div><=
p class=3DMsoNormalCxSpMiddle style=3D'mso-margin-top-alt:1.0pt;margin-right:0in=
;margin-bottom:1.0pt;margin-left:0in;mso-add-space:auto'><span style=3D'font-s=
ize:8.0pt;color:black'>PSTN +1 703-593-2683<o:p></o:p></span></p></div></div=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0i=
n 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:12.0pt;color:black'>=
From: </span></b><span style=3D'font-size:12.0pt;color:black'>Modern &lt;moder=
n-bounces@ietf.org&gt; on behalf of &quot;Peterson, Jon&quot; &lt;jon.peters=
on@team.neustar&gt;<br><b>Date: </b>Sunday, July 16, 2017 at 5:20 AM<br><b>T=
o: </b>&quot;modern@ietf.org&quot; &lt;modern@ietf.org&gt;<br><b>Subject: </=
b>[Modern] modern meeting discussion<o:p></o:p></span></p></div><div><p clas=
s=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</=
o:p></p></div><div><p class=3DMsoNormal>For the MODERN meeting this time, Chri=
s Wendt and I put our heads together to try to come up with a more concrete =
use case that would have some immediate applicability to the industry. Latel=
y there has been some talk in North America recently about ways to share dat=
a structures that will let carriers know if a number is invalid or unallocat=
ed, so that abusive calls from numbers that simply shouldn't be able to orig=
inate at all can be blocked or otherwise given special treatment.&nbsp;<o:p>=
</o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p c=
lass=3DMsoNormal>Taking that as the sort of thing we hope MODERN could address=
, we put together this TeRI data structure for expressing that numbers are v=
alid and allocated &nbsp;- this is a &quot;whitelist&quot; sort of approach =
to the problem, as it seemed easier to us to share a list of numbers that ar=
e valid than it is to come up with all the different ways that someone might=
 try to structure an invalid number. This is intended primarily for use with=
 number ranges, though for some existing use cases (like freephone), assignm=
ent of individual numbers is what matters, and that is probably true of some=
 of our future use cases here (like DRiP) as well.<o:p></o:p></p></div><div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal><a hre=
f=3D"https://tools.ietf.org/html/draft-peterson-modern-teri-valid-00">https://=
tools.ietf.org/html/draft-peterson-modern-teri-valid-00</a><o:p></o:p></p></=
div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNorm=
al>To get this into shape, I also did a bit more work fleshing out parts of =
TeRI, which has also been revised for the meeting, and I'll talk a bit about=
 that as well on Friday.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p></div><div><p class=3DMsoNormal>Jon Peterson<o:p></o:p></p></div=
><div><p class=3DMsoNormal>Neustar, Inc.<o:p></o:p></p></div><p class=3DMsoNorma=
l>_______________________________________________ Modern mailing list Modern=
@ietf.org https://www.ietf.org/mailman/listinfo/modern <o:p></o:p></p></div>=
</body></html>

--B_3583049584_1450687632--



From prvs=2371579e54=tom.mcgarry@team.neustar  Mon Jul 17 01:11:33 2017
Return-Path: <prvs=2371579e54=tom.mcgarry@team.neustar>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8675713179D for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 01:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=team.neustar
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 MmUxc6kJOODd for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 01:11:32 -0700 (PDT)
Received: from mx0b-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (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 75903131798 for <modern@ietf.org>; Mon, 17 Jul 2017 01:11:32 -0700 (PDT)
Received: from pps.filterd (m0078664.ppops.net [127.0.0.1]) by mx0a-0018ba01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v6H82lmh011839 for <modern@ietf.org>; Mon, 17 Jul 2017 04:11:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=team.neustar; h=from : to : subject : date : message-id : content-type : mime-version; s=selector1; bh=4ItUoc1+5pPtRvyHbPfvavjvh6mNA4VbihloyV9YY5s=; b=Nn2HWmAdsEU56sl/OTY1nj/UYxTAvBwkgTswGmU5hoBYiBNwen+fZ64pmUtjviP704yg Adyt6ycXN0WgDeYCAYzypHyBBSlm6GnRVh+nnVAV4EF7Cj8FtA30asZuOcmmZlUv2Kc4 ZhNvzb8q9HYqXVucVvBvTGSIJwyuVAXF97Tx1nXqh1Qlwu4SsGJ9AJA23wRH0KqR7KQJ KPMKagHYDdLiWU7OWdTEpdDolH0O2exKd1B2cPIQesRegKtOFfhZwYWy/H4pFnt+6UMu GbDadWPCa4/9hLPBBWUlX9u5/cDSUE6cuzhQFVmz15GWAAzqIoKWquXiJHqh1SRWFn02 vA== 
Received: from stntexhc12.cis.neustar.com ([156.154.17.216]) by mx0a-0018ba01.pphosted.com with ESMTP id 2bqdpvkqjn-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT) for <modern@ietf.org>; Mon, 17 Jul 2017 04:11:30 -0400
Received: from STNTEXMB11.cis.neustar.com ([169.254.1.47]) by stntexhc12.cis.neustar.com ([::1]) with mapi id 14.03.0279.002; Mon, 17 Jul 2017 04:11:29 -0400
From: "McGarry, Tom" <Tom.McGarry@team.neustar>
To: Modern List <modern@ietf.org>
Thread-Topic: Comments on draft-peterson-modern-teri-valid-00
Thread-Index: AQHS/tRLuR6OHWgxdk62k9nDPx51Qg==
Date: Mon, 17 Jul 2017 08:11:29 +0000
Message-ID: <D591E85F.42BC4%tom.mcgarry@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-originating-ip: [10.96.9.117]
Content-Type: multipart/alternative; boundary="_000_D591E85F42BC4tommcgarryneustarbiz_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-17_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1707170124
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/rFlG_1GNtikYDRp29SnDg6KmxSo>
X-Mailman-Approved-At: Mon, 17 Jul 2017 02:58:38 -0700
Subject: [Modern] Comments on draft-peterson-modern-teri-valid-00
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 09:56:32 -0000

--_000_D591E85F42BC4tommcgarryneustarbiz_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

ALLOCATED VS ASSIGNED
There are generally 3 states for the number:

  *   "Available" to be allocated to a service provider (I suppose =93Unava=
ilable" is also a state)
  *   =93Allocated" to a service provider
  *   =93Assigned" to a user

This draft addresses the last two, but only uses the term =93allocated=94. =
 It would be good to have both and make the distinction.

QUERY VS LIST
This seems to be a query and response process, e.g., tell me about this num=
ber or block of numbers.  We should include the ability to pull down a list=
, e.g., provide me all allocated numbers, provide me all allocated numbers =
in this prefix.

NIT
4.1, 1st para., last word is misspelled


Tom McGarry

--_000_D591E85F42BC4tommcgarryneustarbiz_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <89C5741B0EAB2C4A92385F2DE324BBE0@neustar.biz>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div><u>ALLOCATED VS ASSIGNED</u></div>
<div>There are generally 3 states for the number:</div>
<ul>
<li>&quot;Available&quot; to be allocated to a service provider (I suppose =
=93Unavailable&quot; is also a state)</li><li>=93Allocated&quot; to a servi=
ce provider</li><li>=93Assigned&quot; to a user</li></ul>
<div>This draft addresses the last two, but only uses the term =93allocated=
=94. &nbsp;It would be good to have both and make the distinction. &nbsp;</=
div>
<div><br>
</div>
<div><u>QUERY VS LIST</u></div>
<div>This seems to be a query and response process, e.g., tell me about thi=
s number or block of numbers. &nbsp;We should include the ability to pull d=
own a list, e.g., provide me all allocated numbers, provide me all allocate=
d numbers in this prefix. &nbsp;</div>
<div><br>
</div>
<div><u>NIT</u></div>
<div>4.1, 1st para., last word is misspelled</div>
<div><br>
</div>
<div><br>
</div>
<div>Tom McGarry</div>
</body>
</html>

--_000_D591E85F42BC4tommcgarryneustarbiz_--


From nobody Mon Jul 17 04:58:31 2017
Return-Path: <prvs=23714af1a5=jon.peterson@team.neustar>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A70B312708C for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 04:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=team.neustar
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 hwLcWO1TZd2q for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 04:58:28 -0700 (PDT)
Received: from mx0b-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (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 4062112F257 for <modern@ietf.org>; Mon, 17 Jul 2017 04:58:28 -0700 (PDT)
Received: from pps.filterd (m0078666.ppops.net [127.0.0.1]) by mx0a-0018ba01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v6HBr38k025866; Mon, 17 Jul 2017 07:58:26 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=team.neustar; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=selector1; bh=BBh9coRIBGCkSjm0VQvthhRA/Rpk28d0s4xTapQhcdo=; b=Ke1oSJV0NzU/Ac2TKyaJaBMyNiD52gcPe7929f4x416yE00LItEEcjJdc2WrEgy9mqAQ q7VTVM/aNa7zCFUtNK2ptycATAlIPACjdy3DjSHcTmfnzbWr3s2DzAygDnqPR3i8Cbaa 23vE9p/ZlFIID9DoSGNlp7YR2swBjRHbEc/nHMiC5NsMv4mZy1UvNISJh/P0EK20FQWl qZlZq4/ndcFq+0FHdXX92P3Bz8qsUa93KLplH4Pt++kMQtbIt4OCqWlE0f07jEfoGRY9 Eg/Ak35fcv0Z0flnR6AHurBOg1xZ3/vNMWpFpPtfutVK/CrxGv3E2o5FR7+7MbkBtRrp 5Q== 
Received: from stntexhc10.cis.neustar.com ([156.154.17.216]) by mx0a-0018ba01.pphosted.com with ESMTP id 2bqf5tbvfe-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 17 Jul 2017 07:58:26 -0400
Received: from stntexmb12.cis.neustar.com ([169.254.2.239]) by stntexhc10.cis.neustar.com ([169.254.4.65]) with mapi id 14.03.0279.002; Mon, 17 Jul 2017 07:58:25 -0400
From: "Peterson, Jon" <jon.peterson@team.neustar>
To: Steve Donovan <srdonovan@usdonovans.com>, "modern@ietf.org" <modern@ietf.org>
Thread-Topic: [Modern] End of WGLC on draft-ietf-modern-problem-framework-02
Thread-Index: AQHS8BjRAt69W94/wkqjpcycLdNPgaJYBlCA
Date: Mon, 17 Jul 2017 11:58:24 +0000
Message-ID: <D5828B13.1E1D4F%jon.peterson@neustar.biz>
References: <d7d2a38d-965e-e908-fd0c-862a5f339ff2@usdonovans.com>
In-Reply-To: <d7d2a38d-965e-e908-fd0c-862a5f339ff2@usdonovans.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [10.96.12.35]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7BBC2F9D5DAA054AB89F44303A9EBD74@neustar.biz>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-17_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1707170188
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/1tbP4I6_kkDkSK8ss_FxarYMFUA>
Subject: Re: [Modern] End of WGLC on draft-ietf-modern-problem-framework-02
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 11:58:30 -0000

We did in fact get some private comments, and based on those I made a few
changes to the document for this version. Given all the interest in
credentials in STIR and ACME, it made sense to introduce a "credential
authority" role in the MODERN framework. One could say that the MODERN
framework now gives an overall picture of how we imagine a lot of the
components surrounding STIR could come together - which might not be a bad
destiny for the MODERN work.

Jon Peterson
Neustar, Inc.

On 6/28/17, 10:13 AM, "Modern on behalf of Steve Donovan"
<modern-bounces@ietf.org on behalf of srdonovan@usdonovans.com> wrote:

>All,
>
>The two week WGLC has completed without comment.  We will talk about
>next steps for the draft during the MODERN session in Prague.
>
>Regards,
>
>Steve
>
>_______________________________________________
>Modern mailing list
>Modern@ietf.org
>https://www.ietf.org/mailman/listinfo/modern


From nobody Mon Jul 17 07:23:22 2017
Return-Path: <rhill@hill-a.ch>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B110131BE2 for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 07:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 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, URIBL_BLOCKED=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 NbYIFle41g4c for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 07:23:17 -0700 (PDT)
Received: from smtp-sh.infomaniak.ch (smtp-sh.infomaniak.ch [128.65.195.4]) (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 83E13131BFA for <modern@ietf.org>; Mon, 17 Jul 2017 07:23:17 -0700 (PDT)
Received: from smtp5.infomaniak.ch (smtp5.infomaniak.ch [83.166.132.18]) by smtp-sh.infomaniak.ch (8.14.5/8.14.5) with ESMTP id v6HENEKN028521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 17 Jul 2017 16:23:14 +0200
Received: from RHillNew (adsl-178-39-160-44.adslplus.ch [178.39.160.44]) (authenticated bits=0) by smtp5.infomaniak.ch (8.14.5/8.14.5) with ESMTP id v6HENCZC058437; Mon, 17 Jul 2017 16:23:13 +0200
From: "Richard Hill" <rhill@hill-a.ch>
To: "'Richard Shockey'" <richard@shockey.us>, "'Peterson, Jon'" <jon.peterson@team.neustar>, <modern@ietf.org>
References: <C06D3FC8-877D-4E12-8C32-B92D95F0DFDA@shockey.us>
In-Reply-To: <C06D3FC8-877D-4E12-8C32-B92D95F0DFDA@shockey.us>
Date: Mon, 17 Jul 2017 16:23:13 +0200
Message-ID: <012401d2ff08$3a0764b0$ae162e10$@ch>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0125_01D2FF18.FD9034B0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdL+YrHGxTOY45DoQsyVr92zoP+/pAApTTUw
Content-Language: en-us
X-Antivirus: Dr.Web (R) for Unix mail servers drweb plugin ver.6.0.2.8
X-Antivirus-Code: 0x100000
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/ikwrWRun5wHl2leNWjuVuvK9R4w>
Subject: Re: [Modern] modern meeting discussion
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 14:23:21 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0125_01D2FF18.FD9034B0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

We get a lot of spoofed calls in Switzerland also. They are illegal, but =
the call centers are located outside of Switzerland, so there =
isn=E2=80=99t much that the Swiss authorities can do about it.

=20

If the call center is willing to break the law (and is able to get away =
with it because they are offshore), how would the proposed TERI scheme =
help?  Are there variations of TERI that would help?

=20

Thanks and best,

Richard

=20

From: Modern [mailto:modern-bounces@ietf.org] On Behalf Of Richard =
Shockey
Sent: Sunday, July 16, 2017 20:31
To: Peterson, Jon; modern@ietf.org
Subject: Re: [Modern] modern meeting discussion

=20

=20

Well this idea has the benefit of being actually practical and =
deployable vs the useless idea of individual number allocation.  Useless =
in the sense that no carrier I know of is going to rip out their =
existing OSS/BSS systems to accommodate the original idea.

=20

The idea of white/black lists for the Do Not Originate application has =
merit as does the idea of listing numbers that have been disconnected =
and recently reassigned.  MODERN would have to compete, potentially, =
other methods that the NANPA and other numbering authorities could =
consider.

=20

The problem right now is that the spoofing industry has moved on into =
the fully allocated range of the national numbering plans in order to =
increase answer rates.   A problem only STIR/SHAKEN can ultimately =
address. There is adequate data from the current crop of data analytics =
firms to support that thesis.=20

=20

In any event this idea does have merit and worth investigation.=20

=20

=20

=20

=20

=20

=E2=80=94=20

Richard Shockey

Shockey Consulting LLC

Chairman of the Board SIP Forum

www.shockey.us

www.sipforum.org

richard<at>shockey.us

Skype-Linkedin-Facebook =E2=80=93Twitter  rshockey101

PSTN +1 703-593-2683

=20

=20

From: Modern <modern-bounces@ietf.org> on behalf of "Peterson, Jon" =
<jon.peterson@team.neustar>
Date: Sunday, July 16, 2017 at 5:20 AM
To: "modern@ietf.org" <modern@ietf.org>
Subject: [Modern] modern meeting discussion

=20

=20

For the MODERN meeting this time, Chris Wendt and I put our heads =
together to try to come up with a more concrete use case that would have =
some immediate applicability to the industry. Lately there has been some =
talk in North America recently about ways to share data structures that =
will let carriers know if a number is invalid or unallocated, so that =
abusive calls from numbers that simply shouldn't be able to originate at =
all can be blocked or otherwise given special treatment.=20

=20

Taking that as the sort of thing we hope MODERN could address, we put =
together this TeRI data structure for expressing that numbers are valid =
and allocated  - this is a "whitelist" sort of approach to the problem, =
as it seemed easier to us to share a list of numbers that are valid than =
it is to come up with all the different ways that someone might try to =
structure an invalid number. This is intended primarily for use with =
number ranges, though for some existing use cases (like freephone), =
assignment of individual numbers is what matters, and that is probably =
true of some of our future use cases here (like DRiP) as well.

=20

https://tools.ietf.org/html/draft-peterson-modern-teri-valid-00

=20

To get this into shape, I also did a bit more work fleshing out parts of =
TeRI, which has also been revised for the meeting, and I'll talk a bit =
about that as well on Friday.

=20

Jon Peterson

Neustar, Inc.

_______________________________________________ Modern mailing list =
Modern@ietf.org https://www.ietf.org/mailman/listinfo/modern=20


------=_NextPart_000_0125_01D2FF18.FD9034B0
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-US link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>We get a lot of spoofed =
calls in Switzerland also. They are illegal, but the call centers are =
located outside of Switzerland, so there isn=E2=80=99t much that the =
Swiss authorities can do about it.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>If the call center is =
willing to break the law (and is able to get away with it because they =
are offshore), how would the proposed TERI scheme help?=C2=A0 Are there =
variations of TERI that would help?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Thanks and =
best,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Richard<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Modern [mailto:modern-bounces@ietf.org] <b>On Behalf Of </b>Richard =
Shockey<br><b>Sent:</b> Sunday, July 16, 2017 20:31<br><b>To:</b> =
Peterson, Jon; modern@ietf.org<br><b>Subject:</b> Re: [Modern] modern =
meeting discussion<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Well this =
idea has the benefit of being actually practical and deployable vs the =
useless idea of individual number allocation.&nbsp; Useless in the sense =
that no carrier I know of is going to rip out their existing OSS/BSS =
systems to accommodate the original idea.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>The idea of =
white/black lists for the Do Not Originate application has merit as does =
the idea of listing numbers that have been disconnected and recently =
reassigned.&nbsp; MODERN would have to compete, potentially, other =
methods that the NANPA and other numbering authorities could =
consider.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>The problem right now is that the spoofing industry =
has moved on into the fully allocated range of the national numbering =
plans in order to increase answer rates. &nbsp;&nbsp;A problem only =
STIR/SHAKEN can ultimately address. There is adequate data from the =
current crop of data analytics firms to support that thesis. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>In any event this idea does have merit and worth =
investigation. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;ma=
rgin-left:0in'><span =
style=3D'font-size:8.0pt;color:black'>=E2=80=94&nbsp;<o:p></o:p></span></=
p><div><p class=3DMsoNormalCxSpMiddle =
style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;ma=
rgin-left:0in'><span style=3D'font-size:8.0pt;color:black'>Richard =
Shockey<o:p></o:p></span></p></div><div><p class=3DMsoNormalCxSpMiddle =
style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;ma=
rgin-left:0in'><span style=3D'font-size:8.0pt;color:black'>Shockey =
Consulting LLC<o:p></o:p></span></p></div><div><p =
class=3DMsoNormalCxSpMiddle =
style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;ma=
rgin-left:0in'><span style=3D'font-size:8.0pt;color:black'>Chairman of =
the Board SIP Forum<o:p></o:p></span></p></div><div><p =
class=3DMsoNormalCxSpMiddle =
style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;ma=
rgin-left:0in'><span style=3D'font-size:8.0pt;color:black'><a =
href=3D"http://www.shockey.us">www.shockey.us</a><o:p></o:p></span></p></=
div><div><p class=3DMsoNormalCxSpMiddle =
style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;ma=
rgin-left:0in'><span style=3D'font-size:8.0pt;color:black'><a =
href=3D"http://www.sipforum.org">www.sipforum.org</a><o:p></o:p></span></=
p></div><div><p class=3DMsoNormalCxSpMiddle =
style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;ma=
rgin-left:0in'><span =
style=3D'font-size:8.0pt;color:black'>richard&lt;at&gt;shockey.us<o:p></o=
:p></span></p></div><div><p class=3DMsoNormalCxSpMiddle =
style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;ma=
rgin-left:0in'><span =
style=3D'font-size:8.0pt;color:black'>Skype-Linkedin-Facebook =
=E2=80=93Twitter &nbsp;rshockey101<o:p></o:p></span></p></div><div><p =
class=3DMsoNormalCxSpMiddle =
style=3D'mso-margin-top-alt:1.0pt;margin-right:0in;margin-bottom:1.0pt;ma=
rgin-left:0in'><span style=3D'font-size:8.0pt;color:black'>PSTN +1 =
703-593-2683<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:12.0pt;color:black'>From: </span></b><span =
style=3D'font-size:12.0pt;color:black'>Modern &lt;<a =
href=3D"mailto:modern-bounces@ietf.org">modern-bounces@ietf.org</a>&gt; =
on behalf of &quot;Peterson, Jon&quot; &lt;<a =
href=3D"mailto:jon.peterson@team.neustar">jon.peterson@team.neustar</a>&g=
t;<br><b>Date: </b>Sunday, July 16, 2017 at 5:20 AM<br><b>To: =
</b>&quot;<a href=3D"mailto:modern@ietf.org">modern@ietf.org</a>&quot; =
&lt;<a =
href=3D"mailto:modern@ietf.org">modern@ietf.org</a>&gt;<br><b>Subject: =
</b>[Modern] modern meeting =
discussion<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>For the MODERN meeting this time, Chris Wendt and I =
put our heads together to try to come up with a more concrete use case =
that would have some immediate applicability to the industry. Lately =
there has been some talk in North America recently about ways to share =
data structures that will let carriers know if a number is invalid or =
unallocated, so that abusive calls from numbers that simply shouldn't be =
able to originate at all can be blocked or otherwise given special =
treatment.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Taking that as the sort of thing we hope MODERN could =
address, we put together this TeRI data structure for expressing that =
numbers are valid and allocated &nbsp;- this is a &quot;whitelist&quot; =
sort of approach to the problem, as it seemed easier to us to share a =
list of numbers that are valid than it is to come up with all the =
different ways that someone might try to structure an invalid number. =
This is intended primarily for use with number ranges, though for some =
existing use cases (like freephone), assignment of individual numbers is =
what matters, and that is probably true of some of our future use cases =
here (like DRiP) as well.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><a =
href=3D"https://tools.ietf.org/html/draft-peterson-modern-teri-valid-00">=
https://tools.ietf.org/html/draft-peterson-modern-teri-valid-00</a><o:p><=
/o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>To get this into shape, I also did a bit more work =
fleshing out parts of TeRI, which has also been revised for the meeting, =
and I'll talk a bit about that as well on =
Friday.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Jon Peterson<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Neustar, Inc.<o:p></o:p></p></div><p =
class=3DMsoNormal>_______________________________________________ Modern =
mailing list <a href=3D"mailto:Modern@ietf.org">Modern@ietf.org</a> <a =
href=3D"https://www.ietf.org/mailman/listinfo/modern">https://www.ietf.or=
g/mailman/listinfo/modern</a> <o:p></o:p></p></div></div></body></html>
------=_NextPart_000_0125_01D2FF18.FD9034B0--


From nobody Mon Jul 17 21:40:41 2017
Return-Path: <nmcnamer@iconectiv.com>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B850D12ECC0 for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 21:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.691
X-Spam-Level: 
X-Spam-Status: No, score=-4.691 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iconectiv.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 NJdNtFbuOFmY for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 21:40:37 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0113.outbound.protection.outlook.com [104.47.34.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91646126C0F for <modern@ietf.org>; Mon, 17 Jul 2017 21:40:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iconectiv.onmicrosoft.com; s=selector1-iconectiv-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=JkMUcFl+KI919MS4n5+kw0XEYNDXqh0AYbHOU/kugUc=; b=ag+VJTOyfc3JXEkPBsVyDiUbgLLQl9dSyANVT8+4Ojpq96lLenfezegRq3U8U9EkTOd1PGQ/t7A5zj7SsqaF52if4W0WXOIwWnAsVIq7oHEE4ndpfKJ19kTGOAfUHV+YJaIA5swWAe+PH7A/1SoloPqPezwb9O5hbdz3anuXj8M=
Received: from BY2PR06MB1800.namprd06.prod.outlook.com (10.163.33.30) by BY2PR06MB1800.namprd06.prod.outlook.com (10.163.33.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.13; Tue, 18 Jul 2017 04:40:35 +0000
Received: from BY2PR06MB1800.namprd06.prod.outlook.com ([10.163.33.30]) by BY2PR06MB1800.namprd06.prod.outlook.com ([10.163.33.30]) with mapi id 15.01.1261.022; Tue, 18 Jul 2017 04:40:35 +0000
From: "McNamer, Natalie" <nmcnamer@iconectiv.com>
To: "Peterson, Jon" <jon.peterson@team.neustar>, Steve Donovan <srdonovan@usdonovans.com>, "modern@ietf.org" <modern@ietf.org>
Thread-Topic: [Modern] End of WGLC on draft-ietf-modern-problem-framework-02
Thread-Index: AQHS8BjOkrF38MBjb0KPji84pK5af6JYB8oAgAEWTYA=
Date: Tue, 18 Jul 2017 04:40:35 +0000
Message-ID: <BY2PR06MB1800530A5BD8217ABADAF5AFC6A10@BY2PR06MB1800.namprd06.prod.outlook.com>
References: <d7d2a38d-965e-e908-fd0c-862a5f339ff2@usdonovans.com> <D5828B13.1E1D4F%jon.peterson@neustar.biz>
In-Reply-To: <D5828B13.1E1D4F%jon.peterson@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: team.neustar; dkim=none (message not signed) header.d=none; team.neustar; dmarc=none action=none header.from=iconectiv.com; 
x-originating-ip: [40.128.180.248]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR06MB1800; 7:0Ym+aBr6+ZWj7/R5Cj7RDKKhN1MS8d2b5Dec9LgpED0z4RSuIXqQiTgjlxIlrNkL9iu7K36pNruMoMqJ9Ns5n8r+xhOQS+xFKx7hE5QdeCm7YnSpML5w05f5NYXdmH+nlijcGOw9AKfYCGN15153BCmd4JE9o9obtBnKEiJ0/rWK1dM3FAJ+aMlkugjJ5n8ejfrS+j/mPZ8S8EYhkb4EYdB152iNsVQ8EOcBzy3+ud3fJbiR7GYDA+39upRLBTe+ox9bQ8/ArclpifBKbuRjmkpJsAdONQ+33PAPAm1vFuDlrBVmtBRga1oCaRhG3aKu6F3skjbtw2ppbLMNhAzhzVowYSbXpq154UoU4FljjolU5dGhbKp/q/EOSYuMX+WXFQ6eMF180mXKxKaa+AJtywJAYGmbO1a6nRWVUosQ/+MKs+ws41yhmq0D2Zc1Q0ubZG+zMCRlkndI2TOIJNQq4B+1N3JlI7YsI14OJUOwHEz3upWY4zbpg9yIhjt72nZHXaNvXaTNt9PY0pDTY+XNM0aK6gnUjusisiO+rnqzMKKg1aw8ja33UIdGqc7Ga4XIikD9ugbW6dOqwxp7cfP2q+WcxFDnAun/ABF8wm8+kq4jXTPnKI5so/U0Q6iLLYnXHIGE60a0ZCo496N/yCROMvzyDEJHAY0zcEhZSPjdnRuUUM8EZc7UMPMFuAxe5VZ54rctrU6edpFSbCeuZloLc7vPBiX4LaV+/u/EwFQwO+cdT8q4gvXy6xBi28fxvGmD2V8BExSOe+OlGB5O5Hk52AbizDC8AUBSpll++QuEfdk=
x-ms-office365-filtering-correlation-id: 2a4592b4-a4b4-4fc6-d21c-08d4cd9721ee
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(48565401081)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:BY2PR06MB1800; 
x-ms-traffictypediagnostic: BY2PR06MB1800:
x-exchange-antispam-report-test: UriScan:(278178393323532)(236129657087228)(247924648384137); 
x-microsoft-antispam-prvs: <BY2PR06MB1800BEB6AAE233C9CBA01749C6A10@BY2PR06MB1800.namprd06.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(2017060910075)(100000703101)(100105400095)(10201501046)(3002001)(93006095)(93001095)(6055026)(6041248)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123555025)(20161123562025)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BY2PR06MB1800; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BY2PR06MB1800; 
x-forefront-prvs: 037291602B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(39840400002)(39850400002)(39410400002)(39400400002)(377454003)(24454002)(13464003)(3846002)(102836003)(6116002)(2501003)(66066001)(81166006)(229853002)(38730400002)(2900100001)(5660300001)(3660700001)(7736002)(8676002)(33656002)(305945005)(9686003)(6246003)(8936002)(2950100002)(478600001)(7696004)(53936002)(76176999)(86362001)(99286003)(14454004)(74316002)(53546010)(3280700002)(50986999)(6306002)(6436002)(77096006)(230783001)(2906002)(54356999)(966005)(189998001)(55016002)(25786009)(6506006); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR06MB1800; H:BY2PR06MB1800.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: iconectiv.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jul 2017 04:40:35.8669 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 69c8e407-b674-422e-b87b-0e5394e0005e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR06MB1800
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/8E6EVCCHO7gIEnDJ20e06MZbFLY>
Subject: Re: [Modern] End of WGLC on draft-ietf-modern-problem-framework-02
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 04:40:40 -0000

I apologize, I am still trying to gain an understanding of the process flow=
s of the IETF -=20

Please clarify what this means?  I had thought comments needed to be made w=
ithin the Last Call timeframe?

Below, Steve states as a co-chair of the group that the WGLC  completed wit=
hout comment.  I assumed that meant it was final - now am I correct that it=
 is "reopened"?

Please advise.

Thanks=20
Natalie McNamer

-----Original Message-----
From: Modern [mailto:modern-bounces@ietf.org] On Behalf Of Peterson, Jon
Sent: Monday, July 17, 2017 6:58 AM
To: Steve Donovan <srdonovan@usdonovans.com>; modern@ietf.org
Subject: Re: [Modern] End of WGLC on draft-ietf-modern-problem-framework-02


We did in fact get some private comments, and based on those I made a few c=
hanges to the document for this version. Given all the interest in credenti=
als in STIR and ACME, it made sense to introduce a "credential authority" r=
ole in the MODERN framework. One could say that the MODERN framework now gi=
ves an overall picture of how we imagine a lot of the components surroundin=
g STIR could come together - which might not be a bad destiny for the MODER=
N work.

Jon Peterson
Neustar, Inc.

On 6/28/17, 10:13 AM, "Modern on behalf of Steve Donovan"
<modern-bounces@ietf.org on behalf of srdonovan@usdonovans.com> wrote:

>All,
>
>The two week WGLC has completed without comment.  We will talk about=20
>next steps for the draft during the MODERN session in Prague.
>
>Regards,
>
>Steve
>
>_______________________________________________
>Modern mailing list
>Modern@ietf.org
>https://www.ietf.org/mailman/listinfo/modern

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


From nobody Mon Jul 17 23:01:06 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E64FF1275AB for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 23:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0H85qekhX9E1 for <modern@ietfa.amsl.com>; Mon, 17 Jul 2017 23:01:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81ADC126B72 for <modern@ietf.org>; Mon, 17 Jul 2017 23:01:03 -0700 (PDT)
Received: from dhcp-8097.meeting.ietf.org (dhcp-8097.meeting.ietf.org [31.133.128.151]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v6I611KI045192 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <modern@ietf.org>; Tue, 18 Jul 2017 01:01:02 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
To: modern@ietf.org
References: <d7d2a38d-965e-e908-fd0c-862a5f339ff2@usdonovans.com> <D5828B13.1E1D4F%jon.peterson@neustar.biz> <BY2PR06MB1800530A5BD8217ABADAF5AFC6A10@BY2PR06MB1800.namprd06.prod.outlook.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <cbbd1d7c-03ac-7cda-46e1-fd18ca2f49ed@nostrum.com>
Date: Tue, 18 Jul 2017 08:00:57 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <BY2PR06MB1800530A5BD8217ABADAF5AFC6A10@BY2PR06MB1800.namprd06.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/g5v6jodBr3H2C5cc1Izwg6v9iP0>
Subject: Re: [Modern] End of WGLC on draft-ietf-modern-problem-framework-02
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 06:01:05 -0000

Natalie -

WGLC is just one step for a document on its way to publication. It is a 
tool the chairs use to determine that there is consensus in the working 
group to ask the IESG to review the document for publication.

There will be more reviews and opportunity to comment going forward, the 
most visible being an IETF-wide Last call (IETF LC).

Comments are welcome at any time. Early comments are better than late 
comments.

RjS


On 7/18/17 6:40 AM, McNamer, Natalie wrote:
> I apologize, I am still trying to gain an understanding of the process flows of the IETF -
>
> Please clarify what this means?  I had thought comments needed to be made within the Last Call timeframe?
>
> Below, Steve states as a co-chair of the group that the WGLC  completed without comment.  I assumed that meant it was final - now am I correct that it is "reopened"?
>
> Please advise.
>
> Thanks
> Natalie McNamer
>
> -----Original Message-----
> From: Modern [mailto:modern-bounces@ietf.org] On Behalf Of Peterson, Jon
> Sent: Monday, July 17, 2017 6:58 AM
> To: Steve Donovan <srdonovan@usdonovans.com>; modern@ietf.org
> Subject: Re: [Modern] End of WGLC on draft-ietf-modern-problem-framework-02
>
>
> We did in fact get some private comments, and based on those I made a few changes to the document for this version. Given all the interest in credentials in STIR and ACME, it made sense to introduce a "credential authority" role in the MODERN framework. One could say that the MODERN framework now gives an overall picture of how we imagine a lot of the components surrounding STIR could come together - which might not be a bad destiny for the MODERN work.
>
> Jon Peterson
> Neustar, Inc.
>
> On 6/28/17, 10:13 AM, "Modern on behalf of Steve Donovan"
> <modern-bounces@ietf.org on behalf of srdonovan@usdonovans.com> wrote:
>
>> All,
>>
>> The two week WGLC has completed without comment.  We will talk about
>> next steps for the draft during the MODERN session in Prague.
>>
>> Regards,
>>
>> Steve
>>
>> _______________________________________________
>> Modern mailing list
>> Modern@ietf.org
>> https://www.ietf.org/mailman/listinfo/modern
> _______________________________________________
> Modern mailing list
> Modern@ietf.org
> https://www.ietf.org/mailman/listinfo/modern
>
> _______________________________________________
> Modern mailing list
> Modern@ietf.org
> https://www.ietf.org/mailman/listinfo/modern


From nobody Tue Jul 18 00:59:48 2017
Return-Path: <chris-ietf@chriswendt.net>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0A612ECF0 for <modern@ietfa.amsl.com>; Tue, 18 Jul 2017 00:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=chriswendt-net.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 0uHCGV6eu0BR for <modern@ietfa.amsl.com>; Tue, 18 Jul 2017 00:59:44 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (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 8E0AE12ECC0 for <modern@ietf.org>; Tue, 18 Jul 2017 00:59:44 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id y43so16853164wrd.3 for <modern@ietf.org>; Tue, 18 Jul 2017 00:59:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chriswendt-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rAAHdrdd1rnDGICfJZj6iT1jvGlBUsY8PV37KVdsAm0=; b=yUIByRuBygrGEFm7+ZprX+ilMkqddhG2MFzqMW3BlCWrMkss0jbbYs3HBWZGJfdE1r O2YGJocmMzNSkyhJdLd01OZokG4b2Azt8dBUoFG2bwWiygsiAM9Gjau0MJFNp1MC7PoN 3yIVs3GH6mmuf3URK6RGuw+tOhYsBNAIJO0KoDB0KmaEGk7o7w8w7WKU7Igikfpmp/lb IOHpcO8LNNFHVvzVYp6+91HoYzzBBZjRaiAyE55qWopOn2eHMTs43TFZVXq68n3OiTTD gNrr1s5V7mWKtz5d/k9SWlHHQNd/or3NCLKVqCAcNf9g4NfpmWP/8M7cTluYBzruMguj eY2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rAAHdrdd1rnDGICfJZj6iT1jvGlBUsY8PV37KVdsAm0=; b=aBn5qfW/vbrdIEe4aShuGwhv4yY/H+An+VyJVodE4jYQZJmYBBH48rZTVqiAVNZscE B+9akOa4lPRLqROqoxE2HFKc5V9e1PHWO8HP/RmboM5xHlYbuKzStHUhI9sXAp0f+Idp JbAcYQVJbRi94vgoeVvDDvvEEkbkhMwZzH1hQPXSDMh+ybjXhLrkn1JE0NSncXjIFgCK jiIc1zg8pQHdOm0MoMuhm3L1JP8tx7OdPgREk9bzy4SZ4vg6K+7jViXnFrA+lo5lFbnW qKwv6+XP1KucuP+w5aWSLJG2847f/2ZOJs+1leSGWs98saA9DJOhw5hXljwbsDvqnlOx ABGg==
X-Gm-Message-State: AIVw111mWFO8gNS30qCFSSR+QuZZaxaZf82s5AL4jm0+2zutmkB6kyNu n46XlM76HUB30cwe
X-Received: by 10.28.59.138 with SMTP id i132mr759872wma.12.1500364783121; Tue, 18 Jul 2017 00:59:43 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:7920:a125:a5ce:cfa4? ([2001:67c:370:128:7920:a125:a5ce:cfa4]) by smtp.gmail.com with ESMTPSA id n2sm2520757wmd.19.2017.07.18.00.59.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 00:59:42 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Chris Wendt <chris-ietf@chriswendt.net>
In-Reply-To: <D5828B13.1E1D4F%jon.peterson@neustar.biz>
Date: Tue, 18 Jul 2017 09:59:38 +0200
Cc: Steve Donovan <srdonovan@usdonovans.com>, "modern@ietf.org" <modern@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <36D4A6FC-C1F5-4BF7-A9F9-89E2E4646C25@chriswendt.net>
References: <d7d2a38d-965e-e908-fd0c-862a5f339ff2@usdonovans.com> <D5828B13.1E1D4F%jon.peterson@neustar.biz>
To: "Peterson, Jon" <jon.peterson@team.neustar>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/IMYLbCQ5EL3iBmYtyGDF5KkT_XQ>
Subject: Re: [Modern] End of WGLC on draft-ietf-modern-problem-framework-02
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 07:59:46 -0000

I support those changes to aligning STIR/ACME and MODERN credentials and =
authority models.  Obviously we want to use as common tools as possible =
going forward as the telephone network evolves to incorporate STIR =
related technologies as well as IP transition related technologies.

-Chris

> On Jul 17, 2017, at 1:58 PM, Peterson, Jon <jon.peterson@team.neustar> =
wrote:
>=20
>=20
> We did in fact get some private comments, and based on those I made a =
few
> changes to the document for this version. Given all the interest in
> credentials in STIR and ACME, it made sense to introduce a "credential
> authority" role in the MODERN framework. One could say that the MODERN
> framework now gives an overall picture of how we imagine a lot of the
> components surrounding STIR could come together - which might not be a =
bad
> destiny for the MODERN work.
>=20
> Jon Peterson
> Neustar, Inc.
>=20
> On 6/28/17, 10:13 AM, "Modern on behalf of Steve Donovan"
> <modern-bounces@ietf.org on behalf of srdonovan@usdonovans.com> wrote:
>=20
>> All,
>>=20
>> The two week WGLC has completed without comment.  We will talk about
>> next steps for the draft during the MODERN session in Prague.
>>=20
>> Regards,
>>=20
>> Steve
>>=20
>> _______________________________________________
>> Modern mailing list
>> Modern@ietf.org
>> https://www.ietf.org/mailman/listinfo/modern
>=20
> _______________________________________________
> Modern mailing list
> Modern@ietf.org
> https://www.ietf.org/mailman/listinfo/modern


From nobody Tue Jul 18 02:42:30 2017
Return-Path: <prvs=2372a84a6b=tom.mcgarry@team.neustar>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01358126E3A for <modern@ietfa.amsl.com>; Tue, 18 Jul 2017 02:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=team.neustar
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 6POhCv3k4IUz for <modern@ietfa.amsl.com>; Tue, 18 Jul 2017 02:42:29 -0700 (PDT)
Received: from mx0b-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (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 09EDB126C0F for <modern@ietf.org>; Tue, 18 Jul 2017 02:42:29 -0700 (PDT)
Received: from pps.filterd (m0078666.ppops.net [127.0.0.1]) by mx0a-0018ba01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id v6I9Y4Im013938 for <modern@ietf.org>; Tue, 18 Jul 2017 05:42:27 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=team.neustar; h=from : to : subject : date : message-id : content-type : mime-version; s=selector1; bh=BCv4bZfsSUzcgqK5yCOS0SW8nHN6BHAw8vTa7H/81Wo=; b=grC2tABKeZYiOR/LuqRsB3qr4weH7FpQgDddz71c37cbpX2GtbIzjPcuzOSda7C3iDNK po0RAf1rPqgBisK6Gshq/5bNB2A4iwd0xiqd8qmlVPH1eDj5LpHUwRBqsIlXD9rJn3EK RXBxAB0Mp4od1LV/3Scj46f7blREfwkdR9MxEcAv9daIq/jjNgZY25tMQepC3Tvq0PGO cgefSfVU4Zh/cizHFakvWfT1+MNXyjw2ARqoCZMNk2oo6DpLYtp2tIlY2Pc5U19YBLgP wN5OsVGWAhisMKcgR/R8wIMSBrlZDn7NkSBx3zEpf2zWS1Fq2jeASxI01Ph+MU2kP4Qe 0g== 
Received: from stntexhc11.cis.neustar.com ([156.154.17.216]) by mx0a-0018ba01.pphosted.com with ESMTP id 2bqf5te4af-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT) for <modern@ietf.org>; Tue, 18 Jul 2017 05:42:27 -0400
Received: from STNTEXMB11.cis.neustar.com ([169.254.1.47]) by stntexhc11.cis.neustar.com ([::1]) with mapi id 14.03.0279.002; Tue, 18 Jul 2017 05:42:26 -0400
From: "McGarry, Tom" <Tom.McGarry@team.neustar>
To: Modern List <modern@ietf.org>
Thread-Topic: Comments on draft-peterson-modern-teri-03
Thread-Index: AQHS/6opXhv5ceAJck+0nvw88CJe3Q==
Date: Tue, 18 Jul 2017 09:42:25 +0000
Message-ID: <D593503D.42C5B%tom.mcgarry@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-originating-ip: [10.96.9.117]
Content-Type: multipart/alternative; boundary="_000_D593503D42C5Btommcgarryneustarbiz_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-07-18_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1707180157
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/tAaQH4AoReqdApLw9sQ4Q5WvoX8>
Subject: [Modern] Comments on draft-peterson-modern-teri-03
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jul 2017 09:42:30 -0000

--_000_D593503D42C5Btommcgarryneustarbiz_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Jon, there are a few places where you need more text, e.g., 4.2.1.1, 4.2.1.=
1.1, 4.2.1.6, and 4.2.2.  I'll work with you on that.

Tom McGarry

--_000_D593503D42C5Btommcgarryneustarbiz_
Content-Type: text/html; charset="us-ascii"
Content-ID: <0A26B752F3785E47A34290163E8ECF9C@neustar.biz>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Jon, there are a few places where you need more text, e.g., 4.2.1.1, 4=
.2.1.1.1, 4.2.1.6, and 4.2.2. &nbsp;I'll work with you on that. &nbsp;</div=
>
<div><br>
</div>
<div>Tom McGarry</div>
</body>
</html>

--_000_D593503D42C5Btommcgarryneustarbiz_--


From nobody Fri Jul 21 01:14:13 2017
Return-Path: <srdonovan@usdonovans.com>
X-Original-To: modern@ietfa.amsl.com
Delivered-To: modern@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0134C131748 for <modern@ietfa.amsl.com>; Fri, 21 Jul 2017 01:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level: 
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] 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 2leARzwaWcaM for <modern@ietfa.amsl.com>; Fri, 21 Jul 2017 01:14:11 -0700 (PDT)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [23.235.209.16]) (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 108A012EB2B for <modern@ietf.org>; Fri, 21 Jul 2017 01:14:11 -0700 (PDT)
Received: from dhcp-8344.meeting.ietf.org ([31.133.131.68]:51897) by biz131.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <srdonovan@usdonovans.com>) id 1dYT4P-003Rc3-5b for modern@ietf.org; Fri, 21 Jul 2017 01:14:10 -0700
To: modern@ietf.org
References: <d7d2a38d-965e-e908-fd0c-862a5f339ff2@usdonovans.com> <D5828B13.1E1D4F%jon.peterson@neustar.biz> <BY2PR06MB1800530A5BD8217ABADAF5AFC6A10@BY2PR06MB1800.namprd06.prod.outlook.com> <cbbd1d7c-03ac-7cda-46e1-fd18ca2f49ed@nostrum.com>
From: Steve Donovan <srdonovan@usdonovans.com>
Message-ID: <4444ef07-0224-91a4-2e8a-a0f49ef41eb9@usdonovans.com>
Date: Fri, 21 Jul 2017 10:13:48 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <cbbd1d7c-03ac-7cda-46e1-fd18ca2f49ed@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-OutGoing-Spam-Status: No, score=-0.2
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srdonovan@usdonovans.com
X-Authenticated-Sender: biz131.inmotionhosting.com: srdonovan@usdonovans.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/modern/8C0X6ksWiUyHjhA9cYMMwfJyxOE>
Subject: Re: [Modern] End of WGLC on draft-ietf-modern-problem-framework-02
X-BeenThere: modern@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Managing, Ordering, Distributing, Exposing, & Registering telephone Numbers non-WG discussion list" <modern.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/modern>, <mailto:modern-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/modern/>
List-Post: <mailto:modern@ietf.org>
List-Help: <mailto:modern-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/modern>, <mailto:modern-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2017 08:14:12 -0000

Natalie,

In this specific case, you are correct, with a new version of the draft 
submitted concurrently with the WGLC, we can consider the document 
re-opened.

As Robert said, comments are welcome at any time, but there will be a 
new WGLC on the new version of the document.  And, of course, you do not 
need to wait until the new WGLC to submit comments.

Steve

On 7/18/17 8:00 AM, Robert Sparks wrote:
> Natalie -
>
> WGLC is just one step for a document on its way to publication. It is 
> a tool the chairs use to determine that there is consensus in the 
> working group to ask the IESG to review the document for publication.
>
> There will be more reviews and opportunity to comment going forward, 
> the most visible being an IETF-wide Last call (IETF LC).
>
> Comments are welcome at any time. Early comments are better than late 
> comments.
>
> RjS
>
>
> On 7/18/17 6:40 AM, McNamer, Natalie wrote:
>> I apologize, I am still trying to gain an understanding of the 
>> process flows of the IETF -
>>
>> Please clarify what this means?  I had thought comments needed to be 
>> made within the Last Call timeframe?
>>
>> Below, Steve states as a co-chair of the group that the WGLC 
>> completed without comment.  I assumed that meant it was final - now 
>> am I correct that it is "reopened"?
>>
>> Please advise.
>>
>> Thanks
>> Natalie McNamer
>>
>> -----Original Message-----
>> From: Modern [mailto:modern-bounces@ietf.org] On Behalf Of Peterson, Jon
>> Sent: Monday, July 17, 2017 6:58 AM
>> To: Steve Donovan <srdonovan@usdonovans.com>; modern@ietf.org
>> Subject: Re: [Modern] End of WGLC on 
>> draft-ietf-modern-problem-framework-02
>>
>>
>> We did in fact get some private comments, and based on those I made a 
>> few changes to the document for this version. Given all the interest 
>> in credentials in STIR and ACME, it made sense to introduce a 
>> "credential authority" role in the MODERN framework. One could say 
>> that the MODERN framework now gives an overall picture of how we 
>> imagine a lot of the components surrounding STIR could come together 
>> - which might not be a bad destiny for the MODERN work.
>>
>> Jon Peterson
>> Neustar, Inc.
>>
>> On 6/28/17, 10:13 AM, "Modern on behalf of Steve Donovan"
>> <modern-bounces@ietf.org on behalf of srdonovan@usdonovans.com> wrote:
>>
>>> All,
>>>
>>> The two week WGLC has completed without comment.  We will talk about
>>> next steps for the draft during the MODERN session in Prague.
>>>
>>> Regards,
>>>
>>> Steve
>>>
>>> _______________________________________________
>>> Modern mailing list
>>> Modern@ietf.org
>>> https://www.ietf.org/mailman/listinfo/modern
>> _______________________________________________
>> Modern mailing list
>> Modern@ietf.org
>> https://www.ietf.org/mailman/listinfo/modern
>>
>> _______________________________________________
>> Modern mailing list
>> Modern@ietf.org
>> https://www.ietf.org/mailman/listinfo/modern
>
> _______________________________________________
> Modern mailing list
> Modern@ietf.org
> https://www.ietf.org/mailman/listinfo/modern

