1 / 12

RADIUS Chargeable User Identity

RADIUS Chargeable User Identity. draft-adrangi-radius-chargeable-user-identity-02.txt. Farid Adrangi Avi Lior Jouni Korhonen. Current Issues. Next Step. Should this be WG item? Is this a valid problem? If yes, resolve issues by next IETF. RADIUS Redirection.

brandonmendez
Download Presentation

RADIUS Chargeable User Identity

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. RADIUS Chargeable User Identity draft-adrangi-radius-chargeable-user-identity-02.txt Farid Adrangi Avi Lior Jouni Korhonen

  2. Current Issues

  3. Next Step • Should this be WG item? • Is this a valid problem? • If yes, resolve issues by next IETF

  4. RADIUS Redirection draft-lior-radius-redirection-01 Avi Lior Farid Adrangi

  5. Need Review • No activity in this period. • Please review and give us comments.

  6. RADIUS Bandwidth Capability draft-adrangi-radius-bandwidth-capability-01.txt F. Adrangi, Intel P. Congdon and C. Black, Hewlett Packard A. Lior, Bridgewater Systems F. Bari, Cingular Wireless

  7. Slightly new approach • Previously the draft reflected a single model for expressing/negotiating bandwidth. • Found out that there are many ways to do this. • Lots of different attributes etc… • The best approach would be to define a framework that can support these different models.

  8. Bandwidth Attributes • Bandwidth attribute • E.g. Ingress-QoS-Blob, Egress-QoS-Blob • Would be encoded as a string • First octet(s) would define the type of information in the blob. • We can standardize some methods in this document: • Tell us which? • Others can define new approach • IANA registration of “blob-type-codes”

  9. Example • Assuming 001 represents IngressQosBlob for RFC2697. String format: 001XXXXXXXXYYYYYYYYZZZZZZZZAAAAAA..... , where • XXXX... is unsigned32 Committed Information Rate (CIR) • YYYY... is unsigned32 Committed Burst Size (CBS) • ZZZZ... Is unsigned32 Excess Burst Size (EBS) • AAAA....is action code which expresses what to do in this case with green yellow and red packets • For example, a service may discard all red packets, because they exceeded both the committed and excess burst sizes, forward yellow packets as best effort, and forward green packets with a low drop probability..

  10. Bandwidth ID • This was missing from previous work • Same concept as Filter-Id • Handle to Bandwidth Blob in the NAS ( provisioned statically or available dynamically) • If provisioned statically - yes, it does not scale!!! • But it is nevertheless useful. Not every environment needs to scale. • Bandwidth ID can allow for very precise bandwidth control. • But Bandwidth-ID can also refer to a Bandwidth Blob provisioned dynamically or that can be retrieved from somewhere and hence it does scale.

  11. Backup Slides ….

  12. Example use of Bandwidth Id in Dynamic Situations 1: UE and AF negotiate QoS E.g., SIP UE AF Token 3: UE Requests “Flows” 2: AF request QoS Token Token Access Request Bandwidth-ID NAS PolicyDecision Function Access Accept QoS Blob Token placed in Bandwidth-Id and is used as a handle to fetch the QoS Blob

More Related