Done.
-MSK
On Fri, Dec 1, 2023 at 10:14 AM Robert Sparks <rjsparks@xxxxxxxxxxx> wrote:
Author and long-time facilitator of the SIPit interop events here:
This Errata should be rejected.
The existing text explains and it is _intentional_ that the diagram claims that no media is sent.
Here's the text from the top of page 7:
In this scenario, Alice calls Bob, then Bob places the call on hold. Bob then takes the call off hold, then Alice hangs up the call. Note that hold is unidirectional in nature. However, a UA that places the other party on hold will generally also stop sending media, resulting in no media exchange between the UAs. Older UAs may set the connection address to 0.0.0.0 when initiating hold. However, this behavior has been deprecated in favor or using the a=inactive SDP attribute if no media is sent, or the a=sendonly attribute if media is still sent. Also note the use of the rendering feature tag defined in RFC 4235 [RFC4235] used in F10 and F11 to indicate that Bob's UA is no longer rendering media to Bob, i.e., that Bob has placed the call on hold.RjS
On 12/1/23 12:03 PM, Rebecca VanRheenen wrote:
Hi Murray and Francesca, We are unable to verify this erratum that the submitter marked as editorial. Please note that we have changed the “Type” of the following errata report to “Technical”. As Stream Approver, please review and set the Status and Type accordingly (see the definitions at https://www.rfc-editor.org/errata-definitions/). You may review the report at: https://www.rfc-editor.org/errata/eid7718 Note: We are sending this to you as ADs of the ART area as the sipping Working Group (was part of the RAI Area) has concluded. Please see https://www.rfc-editor.org/how-to-verify/ for further information on how to verify errata reports. Further information on errata can be found at: https://www.rfc-editor.org/errata.php Thank you. RFC Editor/rvOn Dec 1, 2023, at 8:27 AM, RFC Errata System <rfc-editor@xxxxxxxxxxxxxx> wrote: The following errata report has been submitted for RFC5359, "Session Initiation Protocol Service Examples". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7718 -------------------------------------- Type: Editorial Reported by: Fabien R. <rocherfabien@xxxxxxxx> Section: 2.1 Call Hold Original Text ------------- In the diagram: | No RTP Sent! | Corrected Text -------------- | One way RTP | |<==============================| Notes ----- If we follow the explanation next to the diagram, the RTP flow should be 'unidirectionnal' after the hold because F10 is using a=sendonly and F12 a=recvonly. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC5359 (draft-ietf-sipping-service-examples-15) -------------------------------------- Title : Session Initiation Protocol Service Examples Publication Date : October 2008 Author(s) : A. Johnston, Ed., R. Sparks, C. Cunningham, S. Donovan, K. Summers Category : BEST CURRENT PRACTICE Source : Session Initiation Proposal Investigation Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG
_______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
