1 / 8

MIDCOM Protocol Semantics 56 th IETF

This document outlines the changes made to the MIDCOM protocol's semantics, primarily focusing on the restructuring of address tuple sections, removal of explicit group lifetime specifications, and the introduction of implicit handling of group transactions. Key updates include mandatory requirements for session establishment and termination, the introduction of optional policy rule transactions, and open issues regarding IP wildcarding and security considerations. The document aims to clarify the operational functionality and compliance necessary for effective session control management.

frieda
Télécharger la présentation

MIDCOM Protocol Semantics 56 th IETF

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MIDCOM Protocol Semantics56th IETF Martin Stiemerling, Jürgen Quittek, Tom Taylor {stiemerling|quittek}@ccrle.nec.de taylor@nortelnetwork.com 20030318

  2. Changes in –01 Draft • Address tuple section • Moved from PER/PRR sections into new section • Structured wildcarding text • IP addresses and port numbers • Currently no IP wildcarding supported • Adapted example section • Changed group transactions • Now imlplicit handling • See next slide • Conformance statements

  3. Group Transactions • Groups are created implicit by PER/PRR • No explicit group lifetime anymore • Group is deleted when last member Policy Rule is deleted • Removed transactions • Group Establishment (GE) • Asynchronous Group Deletetion (AGD)

  4. Conformance Statements • Session Control Transactions – All Mandatory • Session Establishment (SE) mandatory • Session Termination (ST) mandatory • Asynchronous Session Termination (AST) mandatory • Policy Rule Group Transactions – All Optional • Group Lifetime Change (GLC) optional • Group List (GL) optional • Group Status (GS) optional • Policy Rule Transactions • Policy Reserve Rule (PRR) mandatory • Policy Enable Rule (PER) mandatory • Policy Rule Lifetime Change (RLC) mandatory • Policy Rule Status (PRS) optional • Asynchronous Policy Rule Deletion (ARD) mandatory

  5. Open Issues(1) • Is IP wildcarding required? • What would be application scenarios for IP wildcarding? • Further elaborate the capability information sent from the middlebox to the agent at session setup. • What further capability information should be sent? • Is there a need to support enabling ICMP, IGMP, RSVP, ...? • Should the middlebox reply with a list of supported encryption methods in SE failure reply?

  6. Open Issues(2) • Further elaborate section on security considerations. • Shall the agent be able to specify parameters for protection against denial of service attacks, like: • maximum total number of TCP connection setups allowed • maximum number of TCP connection setups per minute • maximum number of UDP packets per minute • maximum bit rate • etc.

  7. INVITE(listen on port X*) INVITE(listen on Port x) 200 OK (listen on Port E) 200 OK (listen on Port E) User I Internal SIP Telephone User E External SIP Telephone Private Network NAPT Reserve External Address and Port X Enable All OK, NAT mapped address and port X* Enabling SIP Calls orWhy do we need PRR? I wanna call User E

  8. Thank you!

More Related