RFC 3521 (rfc3521) - Page 2 of 25

Framework for Session Set-up with Media Authorization

RFC 3521        Session Set-up with Media Authorization       April 2003


Table of Contents

   1.  Introduction....................................................2
   2.  Conventions used in this document...............................3
   3.  Definition of terms.............................................4
   4.  The Coupled Model...............................................5
       4.1   Coupled Model Message Flows...............................6
       4.2   Coupled Model Authorization Token.........................8
       4.3   Coupled Model Protocol Impacts............................8
   5.  The Associated Model >................8
       5.1   Associated Model Message Flows
             >...............................9
       5.2   Associated Model Authorization Token
             >..............................11
       5.3   Associated Model Protocol Impacts
             >..............................11
       5.4   Associated Model Network Impacts
             >..............................12
   6.  The Associated Model >..............12
       6.1   Associated Model Message Flows
             >.............................13
       6.2   Associated Model Authorization Token
             >.............................15
       6.3   Associated Model Protocol Impacts
             >.............................16
   7. The Non-Associated Model........................................16
       7.1   Non-Associated Model Message Flow........................17
       7.2   Non-Associated Model Authorization Token.................19
       7.3   Non-Associated Model Protocol Impacts....................19
   8.  Conclusions....................................................20
   9.  Security Considerations........................................21
   10. Normative References...........................................22
   11. Informative References.........................................23
   12. Acknowledgments................................................23
   13. Authors' Addresses.............................................24
   14. Full Copyright Statement.......................................25

1. Introduction

   Various mechanisms have been defined through which end hosts can use
   a session management protocol (e.g., SIP [6]) to indicate that QoS
   requirements must be met in order to successfully set up a session.
   However, a separate protocol (e.g., RSVP [7]) is used to request the
   resources required to meet the end-to-end QoS of the media stream.
   To prevent fraud and to ensure accurate billing, some linkage is






Hamer, et al.                Informational