From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "stir@ietf.org" <stir@ietf.org>
Thread-Topic: STIR update
Thread-Index: AQHRhfDFE/m+CHVjFkWEf09fp8QOYA==
Date: Thu, 24 Mar 2016 17:15:31 +0000
Message-ID: <D3196EC1.183BC1%jon.peterson@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.5.7.151005
Content-Type: multipart/alternative;
 boundary="_000_D3196EC1183BC1jonpetersonneustarbiz_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/stir/d_ZdJ8AcAEH3-ufPWfT4KwqnSr4>
Subject: [stir] STIR update
Precedence: list

--_000_D3196EC1183BC1jonpetersonneustarbiz_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


In advance of the Buenos Aires meeting, Chris and I have updated the core S=
TIR specifications. rfc4474bis and stir-passport are now in closer alignmen=
t, though I'm sure there are still a few remaining places where synchroniza=
tion is needed. We tried to make the extensibility model much clearer: what=
 used to be "spec" or "type" is now "ppt", and front-line extensibility is =
largely based on using the "ppt" attribute to signal that you've gone beyon=
d the "bare minimum." Also, do note that the new rfc4474bis introduced a sm=
all fix in order to handle networks that alter the Date header in transit (=
if you do that, your network is bad and you should feel bad, btw). But ther=
e shouldn't be any shocking changes in here, this is pretty much just conti=
nuing the alignment process that the last revisions started.

Sean and I also issued a new version of stir-certs. I think this version do=
es a better job of explaining the various ways to use certs with STIR, and =
explicitly leaves open doors that people seem to want to use.

Finally, to demonstrate how we think the extensibility model is supposed to=
 work, Chris and I wrote a draft that extends STIR with a "cna" parameter t=
hat can secure the display name of a caller. That spec is draft-peterson-st=
ir-cnam. Securing display name is specifically out of scope of the STIR wor=
king group, a provision we created when there was an active "cnit" effort u=
nderway, but we're not necessarily seeking a charter update at this point -=
 we just want to make sure that we at least understand how extensibility is=
 supposed to work, and this example seemed like the lowest-hanging fruit.

Happy to talk about this here on the list, or in Buenos Aires.

Jon Peterson
Neustar, Inc.

--_000_D3196EC1183BC1jonpetersonneustarbiz_
Content-Type: text/html; charset="us-ascii"
Content-ID: <4B1751F78BF8E542A76FA90D16ABE8BF@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>In advance of the Buenos Aires meeting, Chris and I have updated the c=
ore STIR specifications. rfc4474bis and stir-passport are now in closer ali=
gnment, though I'm sure there are still a few remaining places where synchr=
onization is needed. We tried to
 make the extensibility model much clearer: what used to be &quot;spec&quot=
; or &quot;type&quot; is now &quot;ppt&quot;, and front-line extensibility =
is largely based on using the &quot;ppt&quot; attribute to signal that you'=
ve gone beyond the &quot;bare minimum.&quot; Also, do note that the new rfc=
4474bis
 introduced a small fix in order to handle networks that alter the Date hea=
der in transit (if you do that, your network is bad and you should feel bad=
, btw). But there shouldn't be any shocking changes in here, this is pretty=
 much just continuing the alignment
 process that the last revisions started.</div>
<div><br>
</div>
<div>Sean and I also issued a new version of stir-certs. I think this versi=
on does a better job of explaining the various ways to use certs with STIR,=
 and explicitly leaves open doors that people seem to want to use.</div>
<div><br>
</div>
<div>Finally, to demonstrate how we think the extensibility model is suppos=
ed to work, Chris and I wrote a draft that extends STIR with a &quot;cna&qu=
ot; parameter that can secure the display name of a caller. That spec is dr=
aft-peterson-stir-cnam. Securing display name
 is specifically out of scope of the STIR working group, a provision we cre=
ated when there was an active &quot;cnit&quot; effort underway, but we're n=
ot necessarily seeking a charter update at this point - we just want to mak=
e sure that we at least understand how extensibility
 is supposed to work, and this example seemed like the lowest-hanging fruit=
.</div>
<div><br>
</div>
<div>Happy to talk about this here on the list, or in Buenos Aires.</div>
<div><br>
</div>
<div>Jon Peterson</div>
<div>Neustar, Inc.</div>
</body>
</html>

--_000_D3196EC1183BC1jonpetersonneustarbiz_--