Hi Todd I agree - the draft could provide few examples of where we would use SIP Reason header with multiple protocol values in the same SIP response Regards Ranjit -----Original Message----- From: sipcore <sipcore-bounces@xxxxxxxx> On Behalf Of Todd Herr via Datatracker Sent: Tuesday, October 4, 2022 9:51 AM To: art@xxxxxxxx Cc: draft-ietf-sipcore-multiple-reasons.all@xxxxxxxx; last-call@xxxxxxxx; sipcore@xxxxxxxx Subject: [sipcore] Artart last call review of draft-ietf-sipcore-multiple-reasons-01 Reviewer: Todd Herr Review result: Ready with Nits As someone unfamiliar with SIP Reason Header Fields, I'm of the opinion that perhaps an example of a header field with multiple values might be instructive as a contrast to the examples shown in RFC 3326, but I do not feel strongly enough about this to hold up the document. _______________________________________________ sipcore mailing list sipcore@xxxxxxxx https://www.ietf.org/mailman/listinfo/sipcore -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
