%% You should probably cite draft-ietf-sipcore-name-addr-guidance instead of this I-D.
@techreport{sparks-sipcore-name-addr-guidance-01,
    number =    {draft-sparks-sipcore-name-addr-guidance-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-sparks-sipcore-name-addr-guidance/01/},
    author =    {Robert Sparks},
    title =     {{Clarifications for when to use the name-addr production in SIP messages}},
    pagetotal = 6,
    year =      2016,
    month =     sep,
    day =       27,
    abstract =  {RFC3261 constrained several SIP header fields whose grammar contains the "name-addr / addr-spec" alternative to use name-addr when certain characters appear. Unfortunately it expressed the constraints with prose copied into each header field definition, and at least one header field was missed. Further, the constraint has not been copied into documents defining extension headers whose grammar contains the alternative. This document updates RFC3261 to state the constraint generically, and clarifies that the constraint applies to all SIP header fields where there is a choice between using name-addr or addr-spec. It also updates those extension SIP header fields that use the alternative to clarify that the constraint applies (RFCs 3325, 3515, 3892, 4508, 5002, 5318, 5360, and 5502).},
}