Re: [RAI] [Technical Errata Reported] RFC3680 (3494)

[Gonzalo Camarillo <[e-mail]>]

Hi,

I have just verified (i.e., approved) this one.

Cheers,

Gonzalo


On 22/03/2013 5:17 PM, Robert Sparks wrote:
> (I'm doing a sweep of the outstanding reported RAI errata to help
> Richard and Gonzalo process them)
> 
> This is on the border between Hold For Document Update and Approve for me,
> (This falls into the errors in examples that won't introduce substantive
> confusion), but
> I recommend Approval.
> 
> RjS
> 
> On 2/24/13 10:03 AM, RFC Errata System wrote:
>> The following errata report has been submitted for RFC3680,
>> "A Session Initiation Protocol (SIP) Event Package for Registrations".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=3680&eid=3494
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Brett Tate <[e-mail]>
>>
>> Section: 6
>>
>> Original Text
>> -------------
>>     NOTIFY sip:app.example.com SIP/2.0
>>     Via: SIP/2.0/UDP server19.example.com;branch=z9hG4bKnasaii
>>     From: sip:[e-mail];tag=xyzygg
>>     To: sip:app.example.com;tag=123aa9
>>     Call-ID: [e-mail]
>>     CSeq: 1288 NOTIFY
>>     Contact: sip:server19.example.com
>>     Event: reg
>>     Max-Forwards: 70
>>     Content-Type: application/reginfo+xml
>>     Content-Length: ...
>>
>>     NOTIFY sip:app.example.com SIP/2.0
>>     Via: SIP/2.0/UDP server19.example.com;branch=z9hG4bKnasaij
>>     From: sip:[e-mail];tag=xyzygg
>>     To: sip:app.example.com;tag=123aa9
>>     Call-ID: [e-mail]
>>     CSeq: 1289 NOTIFY
>>     Contact: sip:server19.example.com
>>     Event: reg
>>     Max-Forwards: 70
>>     Content-Type: application/reginfo+xml
>>     Content-Length: ...
>>
>>
>> Corrected Text
>> --------------
>>     NOTIFY sip:app.example.com SIP/2.0
>>     Via: SIP/2.0/UDP server19.example.com;branch=z9hG4bKnasaii
>>     From: sip:[e-mail];tag=xyzygg
>>     To: sip:app.example.com;tag=123aa9
>>     Call-ID: [e-mail]
>>     CSeq: 1288 NOTIFY
>>     Contact: sip:server19.example.com
>>     Event: reg
>>     Subscription-State:active;expires=3600
>>     Max-Forwards: 70
>>     Content-Type: application/reginfo+xml
>>     Content-Length: ...
>>
>>     NOTIFY sip:app.example.com SIP/2.0
>>     Via: SIP/2.0/UDP server19.example.com;branch=z9hG4bKnasaij
>>     From: sip:[e-mail];tag=xyzygg
>>     To: sip:app.example.com;tag=123aa9
>>     Call-ID: [e-mail]
>>     CSeq: 1289 NOTIFY
>>     Contact: sip:server19.example.com
>>     Event: reg
>>     Subscription-State:active;expires=3000
>>     Max-Forwards: 70
>>     Content-Type: application/reginfo+xml
>>     Content-Length: ...
>>
>>
>> Notes
>> -----
>> The two NOTIFY examples are missing mandatory Subscription-State header.
>>
>> Instructions:
>> -------------
>> This errata is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC3680 (draft-ietf-sipping-reg-event-00)
>> --------------------------------------
>> Title               : A Session Initiation Protocol (SIP) Event
>> Package for Registrations
>> Publication Date    : March 2004
>> Author(s)           : J. Rosenberg
>> Category            : PROPOSED STANDARD
>> Source              : Session Initiation Proposal Investigation
>> Area                : Real-time Applications and Infrastructure
>> Stream              : IETF
>> Verifying Party     : IESG
> 
>