Brian,
Concerning your comment:
""The main information is conveyed by the Rw interface:
o Resources reservation and/or allocation request for media flows;
o QoS handling request such as packet marking and policing to use;
o Gate control (opening/closing) request for a media flow;
o NAPT and NAT traversal requesting the necessary address mapping
information;
o Resource usage information request and report for media flows"
The IANA Considerations of RFC3588 says:
"Diameter is not intended as a general purpose protocol, and
allocations SHOULD NOT be made for purposes unrelated to
authentication, authorization or accounting."
I would like to ask whether there has been discussion of the apparent
conflict between these two statements. It doesn't seem that the Rw
interface
is primarily a AAA interface; the resource reservation, QOS policy and
NAT
traversal signaling in particular do not seem to be AAA functions.
I think the draft should at least explain why it is OK to ignore
the SHOULD NOT in RFC3588."
In fact, the Diameter is being extended for a variety of applications
that do not look like a pure AAA functions, for example, in the IETF
DIME, we are developing a similar document for QoS application.
Moreover, to some extent, the Rw interface can be viewed as sort of
authorization interface in the context of the AAA.
Does it help answer your question?
Regards,
Dong Sun
Alcatel-Lucent
Chief Technology Office
600 Mountain Ave
Murray Hill, NJ 07974 USA
Tel/Fax: +1 908-582-2617
Email: [EMAIL PROTECTED]
-----Original Message-----
From: Brian E Carpenter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2008 4:30 AM
To: General Area Review Team
Cc: Dan Romascanu; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Gen-ART LC review of draft-sun-dime-itu-t-rw-01.txt
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
