Subject: [Sipping] FW: [AAA-WG]: [AAA] Comments on Diameter SIP application

From: "Roy, Radhika \(AEAD\)" <[email-masked]>
Date: Thu, 13 Oct 2005 09:52:17 -0400

Hi, all:
 
I draw your attention to the last call (October 24) of the Diameter SIP application draft. It is a very useful work as people are using Radius/Diameter server for implementation of SIP.
 
Like me, kindly provide your comments to the AAA WG.
 
Best regards,
Radhika

________________________________

From: [email-masked] on behalf of Roy, Radhika (AEAD)
Sent: Wed 10/12/2005 10:26 AM
To: [email-masked]
Subject: [AAA-WG]: [AAA] Comments on Diameter SIP application

Hi, all:

I am sorry to see that the last day for providing comments (editorial) had expired on September 24, 2005. Since comments are techno-editorial, probably RFC editor might see those assuming that it might be helpful.

Techno-Editorial Comments on http://people.nokia.net/~miguel/drafts/draft-ietf-aaa-diameter-sip-app-07-to-09-wide.html draft

1.	Title: Let us modify as "Diameter SIP Application." The reason as follows: 

*         The word "...protocol-application .." does NOT sound correct.

*         Note: The word "... application-protocol .." makes sense, but not the reverse one.

2.	Abstract: Change "Diameter Session Initiation Protocol (SIP) Application" to "Diameter SIP Application." The reason is stated in item 1. Note: The following sentence has already spelled "SIP" as "Session Initiation Protocol." 
3.	Section 3: Remove the 3rd paragraph because it is incomplete when we see the 4th paragraph and replace it with the global statement as follows: 

*         "The Diameter SIP application is not related to and does not require other Diameter applications."

4.	Figure 1: Within boxes put "SIP Server/Node" or "SIP Entity" instead of only "SIP." Also put numbers like 1, 2, 3, ... etc. within the boxes to be in consistent with texts written in describing Figure 1. 
5.	Section 5.3: 4th Paragraph - In the end of 2nd sentence, add as follows, .." with the help of Diameter server." This is due to the fact that SIP server 1 cannot locate SIP server 2 all by itself unless Diameter server provides the address of SIP server 2. 
6.	Section 5.3: 4th Paragraph - Clarify by adding texts that "SIP server 1 needs to find SIP server 2 to route the SIP call to the destination." 
7.	 Section 5.4: 9th Paragraph - Clarify by adding texts "What SIP server 2 does if credentials are not valid." 
8.	Sections 5.5 and 5.6: General comments - These sections show only one SIP server in all figures where as the previous sections show two SIP servers (edge, within network). Some clarifications need to be added whether or not the Diameter message flows will be different if it is edge SIP server or network-based SIP server. 
9.	Section 5.10: 2nd Paragraph - Make it clear that "it is an 'assumption' that all information/profile/data related to one user remains only in 'one' Diameter server." (Note: It may or may not always be true for different implementation schemes of the large-scale network where Diameter servers will deal with a variety of data. For example, implementation may be such that all users of all applications including SIP may only contact always a "single" logical Diameter server, but all diameter servers will physically distributed across the entire network for providing scalability enhancing performance.) 

Best regards,

Radhika

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP