RE: [Dime] Diameter QoS Strawman Proposal (UNCLASSIFIED)

["Nguyen, An P CIV NCS NC2" <an.p.nguyen at dhs.gov>]

Title: Diameter QoS Strawman Proposal

Classification: UNCLASSIFIED

Caveats: NONE

Sorry I meant IMS-based NGN architecture that has Cx and Dx interfaces.

 

An

-----Original Message-----
From: Nguyen, An P CIV NCS NC2
Sent: Wednesday, June 21, 2006 10:25 AM
To: 'Tschofenig, Hannes'
Cc: dime at ietf.org
Subject: RE: [Dime] Diameter QoS Strawman Proposal (UNCLASSIFIED)

Classification: UNCLASSIFIED

Caveats: NONE

Hannes,

 

Just a question: RFC 4412 defines  SIP header fields for communications resource priority. This RFC deals with different namespaces (e.g., ets.x, wps.x, etc.). How does your Diameter QoS draft take these namespaces into account when it comes to authentication and authorization?

 

The reason I am interested in this draft is that the Cx and Dx interfaces of the IMS architecture specifies DIAMETER.

 

Thanks,

 

An

-----Original Message-----
From: Tschofenig, Hannes [mailto:hannes.tschofenig at siemens.com]
Sent: Monday, June 19, 2006 8:07 AM
To: dime at ietf.org
Subject: [Dime] Diameter QoS Strawman Proposal

Hi all,

based on the thoughts by Avi about the Diameter QoS work, we (Mayutan Arumaithurai, Alan McNamee and myself) have produced a strawman proposal. I would like to particularly thank Mayutan since he had todo most of the work. Please find the draft at:

http://www.tschofenig.priv.at/svn/draft-tschofenig-dime-diameter-qos/diameter-qos-strawman-00.txt

This strawman proposal takes a lot of text from the previous draft version (draft-tschofenig-dime-diameter-qos-00.txt) and allows the QoS mechanisms to work with NASREQ, EAP and DCC.

This document is meant to be input for discussion. Hence, there is no plan to submit it.

Ciao
Hannes

Classification: UNCLASSIFIED

Caveats: NONE

Classification: UNCLASSIFIED

Caveats: NONE

_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime