Shepherd writeup

1. Summary

draft-ietf-stir-certificates defines protocol and is intended for publication
as Proposed Standard. From the abstract:

   In order to prevent the impersonation of telephone numbers on the
   Internet, some kind of credential system needs to exist that
   cryptographically asserts authority over telephone numbers.  This
   document describes the use of certificates in establishing authority
   over telephone numbers, as a component of a broader architecture for
   managing telephone numbers as identities in protocols like SIP.

This document is a component of a toolset for combating robocalling. In the
US, the FCC is applying significant pressure to the industry to deter
robocalling (with deadlines in the last part of 2016). An industry-led strike
force is moving towards deployment of a solution that uses that toolset. The
ATIS/SIP Forum IPNNI Task Force's SHAKEN solution relies on the toolset defined
by STIR and profiles it for deployment in the North American market.

2. Review and Consensus

This document has undergone heavy review. Interoperability testing at the SIPit
in September identified issues leading to the introduction of the JWT Claim
Constraints, shifting where LOA assertions are made.

The document suite has been through three working group last calls, the third
of which was abbreviated to one week. The first last call stimulated
significant discussion, some of which was heated. 

3. Intellectual Property

The authors have each confirmed that any IPR they are aware of has been
disclosed. There are no IPR disclosures currently registered for this document

4. Other Points

There are three normative downreferences. Two (3447 and 5912) are
already in the downref registry. The other, 7093, should be called out in

The document provides an ASN.1 module. The module was verified by Russ Housley
and Sean Turner.

The document requires several actions from IANA. They are concretely described
in the document text. Note that the group intended to request pre-allocation of
a few of the codepoints discussed there, but the pre-allocation request was not