1 / 11

DIME WG IETF-69

DIME WG IETF-69. Quality of Service Attributes for Diameter and RADIUS draft-ietf-dime-qos-attributes-01 July, 2007 Jouni Korhonen. What this I-D is about.

anson
Download Presentation

DIME WG IETF-69

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. DIME WGIETF-69 Quality of Service Attributes for Diameter and RADIUS draft-ietf-dime-qos-attributes-01 July, 2007 Jouni Korhonen

  2. What this I-D is about.. • This I-D extends the functionality of the Diameter Base protocol and other Diameter applications with respect to their ability to convey QoS information • A number of AVPs are defined to convey QoS information as part of the e.g. network access authentication (NASREQ, EAP, ...) • The AVPs defined in this document are also available for RADIUS (not quite yet though..) • The QoS may be pre-provisioned or NAS asking for authorization of QoS request • The I-D also defines a simple QoS capability announcement functionality

  3. Current status • draft-korhonen-dime-qos-attributes got adopted as a WG draft -> draft-dime-qos-attributes • New AVPs identified • Example signaling scenarios described • RADIUS compatibility part is missing! • More concrete examples needed

  4. New AVPs • QoS-ID AVP • Type of Unsigned32 and references the QSPEC. • QoS-Flow-State AVP • Type of Enumerated. The AVP gives an indication as to how the flow must be treated. This AVP provides additional information about the treatment • Currently a single value is defined • 0 Pending: The filter rules are not installed but kept pending. Subsequent signaling is necessary to active them

  5. New AVPs cont’d • QSPEC AVP • Type of OctetString and contains QoS parameters. These parameters are defined in the [ietf-dime-qos-parameters] • QoS-Resources AVP • Type of Grouped and includes description of the resources that have been authorized or requested. More than one QoS-Resources AVP MAY be included in a single message QoS-Resources ::= < AVP Header: XXX > 1* [ Extended-QoS-Filter-Rule ] 1* [ QoS-Parameter ] [ QoS-Flow-State ] * [ AVP ]

  6. New AVPs cont’d.. • QoS-Parameter AVP • Type of Grouped and ties the QoS-ID AVP together to the QSPEC AVP. All parameters followed by the QSPEC-Type AVP refer to the same QoS model/profile • QSPEC-Type AVP • Type of Unsigned32 and contains the supported QoS model or QoS profile. The value of 0 refers to the QoS parameters described in [ietf-dime-qos-parameters] QoS-Parameter ::= < AVP Header: XXX > { QoS-ID } { QSPEC-Type } 1* [ QSPEC ] * [ AVP ]

  7. New AVPs cont’d... • Extended-QoS-Filter-Rule AVP • Type of Grouped. The QoS filter rule associated with the QoS-ID re-uses the RADIUS NAS-Traffic-Rule AVP. This AVP ties a specific filter to a QoS-ID that in turn refers to a specific QoS-Parameter Extended-QoS-Filter-Rule ::= < AVP Header: XXX > { QoS-ID } { NAS-Traffic-Rule } * [ AVP ]

  8. New AVPs last • QoS-Capability AVP • Type Grouped and contains a list of supported QSPEC-Types and respective AVPs. The NAS should include this AVP to indicate the support for this specification and for the specific QoS models. QoS-Capability ::= < AVP Header: XXX > 1* { QSPEC-Type } * [ AVP ]

  9. Example of pre-provisioned QoS as part of EAP End Diameter Diameter Host Client server | (initiate EAP) | | |<------------------------------>| | | | Diameter-EAP-Request | | | EAP-Payload(EAP Start) | | | QoS-Capability | | |------------------------------->| | | | | | Diameter-EAP-Answer | | Result-Code=DIAMETER_MULTI_ROUND_AUTH | | | EAP-Payload(EAP Request #1) | | |<-------------------------------| | EAP Request(Identity) | | |<-------------------------------| | : : : : <<<more message exchanges>>> : : : : | EAP Response #N | | |------------------------------->| | | | Diameter-EAP-Request | | | EAP-Payload(EAP Response #N) | | |------------------------------->| | | | | | Diameter-EAP-Answer | | | Result-Code=DIAMETER_SUCCESS | | | EAP-Payload(EAP Success) | | | (authorization AVPs) | | | QoS-Resources | | |<-------------------------------| | EAP Success | | |<-------------------------------| | | | |

  10. Open Issues and next steps • RADIUS compatibility! • More concrete examples showing actual encodings of QoS parameters • Review is needed from RADEXT folks

  11. Questions? Feedback?

More Related