Subject: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-name-addr-guidance-01.txt

From: Robert Sparks <[email-masked]>
Date: Tue, 27 Sep 2016 14:17:49 -0500

See my recent response on list to Brett for what led to these changes.

I think this is ready to go.

RjS

-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-sparks-sipcore-name-addr-guidance-01.txt
Date: 	Tue, 27 Sep 2016 12:14:41 -0700
From: 	[email-masked]
To: 	Robert Sparks <[email-masked]>

A new version of I-D, draft-sparks-sipcore-name-addr-guidance-01.txt
has been successfully submitted by Robert Sparks and posted to the
IETF repository.

Name:		draft-sparks-sipcore-name-addr-guidance
Revision:	01
Title:		Clarifications for when to use the name-addr production in SIP messages
Document date:	2016-09-27
Group:		Individual Submission
Pages:		6
URL:            https://www.ietf.org/internet-drafts/draft-sparks-sipcore-name-addr-guidance-01.txt
Status:         https://datatracker.ietf.org/doc/draft-sparks-sipcore-name-addr-guidance/
Htmlized:       https://tools.ietf.org/html/draft-sparks-sipcore-name-addr-guidance-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-sparks-sipcore-name-addr-guidance-01

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).

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.

The IETF Secretariat