[sipcore] PR (pre-01): draft-ietf-sipcore-multiple-reasons-latest

[Robert Sparks <[e-mail]>]

I've posted a pull-request at

https://github.com/rjsparks/draft-ietf-sipcore-multiple-reasons/pull/1

that, I believe, captures the result of the conversation during working 
group adoption.

If there are no substantive changes requested by tomorrow around this 
time, I'll merge it and post -01 to the repository.

(I'll straighten out the markdown to make the changelog look better 
before then).

An easy way to look at the changes is here:

https://www.ietf.org/rfcdiff?url1=https://rjsparks.github.io/draft-ietf-sipcore-multiple-reasons/draft-ietf-sipcore-multiple-reasons.txt&url2=https://rjsparks.github.io/draft-ietf-sipcore-multiple-reasons/becausestir/draft-ietf-sipcore-multiple-reasons.txt

RjS

On 7/25/22 5:05 PM, Robert Sparks wrote:
> Resending from the correct address:
>
> On 7/25/22 4:07 PM, Robert Sparks wrote:
>> Hello sipcore:
>>
>> This is just the renaming of draft-sparks-sipcore-multiple-reasons to 
>> draft-ietf-sipcore-multiple-reasons.
>>
>> There has been a lot of feedback about some short things to add, and 
>> I am working on those as a 01. This -00 is here to make comparisons 
>> later easier.
>>
>> Right now, I'm keeping the source at 
>> https://github.com/rjsparks/draft-ietf-sipcore-multiple-reasons. PRs 
>> are welcome. I'm happy to move that repo to a sipcore github 
>> organization should the group choose to have one.
>>
>> RjS
>>
>> On 7/25/22 3:31 PM, [e-mail] wrote:
>>> A New Internet-Draft is available from the on-line Internet-Drafts 
>>> directories.
>>> This draft is a work item of the Session Initiation Protocol Core WG 
>>> of the IETF.
>>>
>>>          Title           : Multiple SIP Reason Header Field Values
>>>          Author          : Robert Sparks
>>>    Filename        : draft-ietf-sipcore-multiple-reasons-00.txt
>>>    Pages           : 4
>>>    Date            : 2022-07-25
>>>
>>> Abstract:
>>>     The SIP Reason Header Field as defined in RFC 3326 allows only one
>>>     Reason value per protocol value.  Practice shows it is useful to
>>>     allow multiple values with the same protocol value.  This update to
>>>     RFC 3326 allows multiple values for an indicated registered 
>>> protocol
>>>     when that protocol defines what the presence of multiple values
>>>     means.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-sipcore-multiple-reasons/
>>>
>>> There is also an HTML version available at:
>>> https://www.ietf.org/archive/id/draft-ietf-sipcore-multiple-reasons-00.html 
>>>
>>>
>>>
>>> Internet-Drafts are also available by rsync at 
>>> rsync.ietf.org::internet-drafts
>>>
>>>
>