1 / 16

DOIC Status

DOIC Status. DOIC Status. Restructuring complete Some cleanup in to be in -04 version 13 open issue remaining. Open Issues. #23 DOIC behavior for realm overload #25 Section 3.1.5 Diameter Agent Behavior #26 Overload Control Endpoints under specified

menefer
Télécharger la présentation

DOIC Status

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. DOIC Status

  2. DOIC Status • Restructuring complete • Some cleanup in to be in -04 version • 13 open issue remaining

  3. Open Issues #23DOIC behavior for realm overload #25Section 3.1.5 Diameter Agent Behavior #26Overload Control Endpoints under specified #27Behavior of agent acting on behalf of Client that does not support DOIC #35additional report types are proposed #43Overstated guidance on session-ending requests. #48Setting M-Bit gives wrong semantics #55Lack of overload control for realm overload condition #57Handling of "Realm-Routed" Overload report type #58Multiple Reporting Nodes for realm-routed-request type reports #60Agent Overload Report Handling considerations #61Agent Capability Announcement Considerations #66Non-Supporting Agent Changing Origin-Host

  4. #23 DOIC behavior for realm overload • Proposal from last meeting: • Change name from realm report to realm-routed-request • Effects only realm-routed requests • Separate extension for a report that controls all traffic to the realm, independent of the request type

  5. #25 Section 3.1.5 Diameter Agent Behavior • Proposed behavior in ietf-donovan-doic-agent-cases.txt

  6. #26 Overload Control Endpoints under specified • Proposed behavior in ietf-donovan-doic-agent-cases.txt

  7. #27 Behavior of agent acting on behalf of Client that does not support DOIC • Proposed behavior in ietf-donovan-doic-agent-cases.txt

  8. #35 additional report types are proposed • Proposal to allow for overload reports to be targeted to a single client • Current proposal is for this to be addressed in a separate extension

  9. #43 Overstated guidance on session-ending requests. • Minor wording change requested. • Will be incorporated into -04.

  10. #48 Setting M-Bit gives wrong semantics • Proposal – explicit guidance that M-bit should never be set.

  11. #55 Lack of overload control for realm overload condition • Proposal to address in a DOIC extension

  12. #57 Handling of "Realm-Routed" Overload report type • Proposal to close based on behavior currently in draft (need to verify correct wording exists)

  13. #58 Multiple Reporting Nodes for realm-routed-request type reports • Needs to be addressed. • Proposal • Allow for multiple reporting nodes for the RRR/Realm report type • Client only listens to source of first received report until it expires or is removed • Question – Do we need to attribute who sent the report?

  14. #60 Agent Overload Report Handling considerations • Proposed behavior in ietf-donovan-doic-agent-cases.txt

  15. #61 Agent Capability Announcement Considerations • Proposed behavior in ietf-donovan-doic-agent-cases.txt

  16. #66 Non-Supporting Agent Changing Origin-Host • Needs to be addressed

More Related