RE: : Diameter redirect
"MORAND Lionel RD-CORE-ISS" <[email protected]> Fri, 21 Jul 2006 01:38:59 +0200
| Newsgroups | gmane.ietf.aaa |
|---|---|
| Message-ID | <7DBAFEC6A76F3E42817DF1EBE64CB02603A9E4CC@FTRDMEL2.rd.francetelecom.fr> |
This is a multi-part message in MIME format. ------_=_NextPart_001_01C6AC55.AD4FEAB4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ********************RESEND*********************************** ________________________________ De : MORAND Lionel RD-CORE-ISS=20 Envoy=E9 : jeudi 20 juillet 2006 11:55 =C0 : 'Paulo Rolo'; [email protected] Objet : RE: [AAA-WG]: Diameter redirect Hi Paulo, =20 Over the 3GPP Cx interface, the Public-Identity AVP is optional for SAR = because there are specific cases for which the presence of the User-Name = AVP is enough (please refer to the 3GPP spec for further details). So, it was decided not to mandate the presence of the Public-Identity = AVP in the SAR with the following limitation: at least one of the = identity types shall be present in the SAR i.e. either a Public-Identity = AVP or a User-Name AVP (of course, both AVPs may be present in the = command). =20 If at least one identity is present in the command, it is always = possible to perform a user identity to HSS resolution, as either = Public-Identity or User-Name can be used as SLF key entry to retrieve = the correct HSS name. =20 Hope this helps! =20 Lionel ________________________________ De : [email protected] [mailto:[email protected]] De la part = de Paulo Rolo Envoy=E9 : jeudi 20 juillet 2006 11:00 =C0 : [email protected] Objet : [AAA-WG]: Diameter redirect Hello, =20 We are currently developing a set of Diameter interfaces and some doubts = have arise, concerning SLF usage. =20 On ETSI TS 123 228 (IP Multimedia Subsystem (IMS)) at section 5.8.1 = (User identity to HSS resolution) it is suggested that a Public User = Identity should be selected and used as input to SLF_QUERY, in order to = resolve to the correct HSS name.=20 =20 Also at section 6.1.2 (S-CSCF registration/deregistration notification) = of TS 129 228 (IP Multimedia (IM) Subsystem Cx and Dx Interfaces), it is = suggested that if Routing Information is not available for SAR (S-CSCF = registration/deregistration), it should be routed to next diameter node, = for example SLF. =20 =20 The issue is that on TS 129 229 (Cx and Dx interfaces based on the = Diameter protocol) at section 6.1.3 (Server-Assignment-Request (SAR) = Command) the Public-Identity is presented as an optional attribute. If = it is not present how should be SLF_QUERY performed? All the other = messages (UAR, LIR, MAR) have Public-Identity as mandatory. =20 =20 Thanks in advance, Paulo Rolo =20 Network and Protocols Unit Intelligent Networks Department Portugal Telecom Inova=E7=E3o, S.A =20 ------_=_NextPart_001_01C6AC55.AD4FEAB4 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20 "urn:schemas-microsoft-com:vml" xmlns:o =3D=20 "urn:schemas-microsoft-com:office:office" xmlns:w =3D=20 "urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20 "urn:schemas-microsoft-com:office:smarttags"><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR><o:SmartTagType = namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"=20 name=3D"country-region"></o:SmartTagType><o:SmartTagType=20 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"=20 name=3D"place"></o:SmartTagType><!--[if !mso]> <STYLE>st1\:* { BEHAVIOR: url(#default#ieooui) } </STYLE> <![endif]--> <STYLE>@font-face { font-family: Verdana; } @page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt 72.0pt = 90.0pt; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman" } A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: purple; TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline } SPAN.EmailStyle17 { FONT-WEIGHT: normal; COLOR: windowtext; FONT-STYLE: normal; = FONT-FAMILY: Verdana; TEXT-DECORATION: none; mso-style-type: = personal-compose } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=3DEN-US vLink=3Dpurple link=3Dblue> <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff = size=3D2><SPAN=20 class=3D479303823-20072006>********************RESEND********************= ***************</SPAN></FONT></DIV><BR> <DIV class=3DOutlookMessageHeader lang=3Dfr dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>De :</B> MORAND Lionel RD-CORE-ISS=20 <BR><B>Envoy=E9 :</B> jeudi 20 juillet 2006 = 11:55<BR><B>=C0 :</B> 'Paulo=20 Rolo'; [email protected]<BR><B>Objet :</B> RE: [AAA-WG]: Diameter=20 redirect<BR></FONT><BR></DIV> <DIV></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Hi Paulo,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Over the 3GPP Cx interface, the Public-Identity = AVP is=20 optional for SAR because there are specific cases for which the = presence of=20 the User-Name AVP is enough (please refer to the 3GPP spec for further=20 details).</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2>So, it was decided not to mandate the presence = of the=20 Public-Identity AVP in the SAR with the following limitation: at least = one of=20 the identity types shall be present in the SAR i.e. either a = Public-Identity AVP=20 or a User-Name AVP (of course, both AVPs may be present in the=20 command).</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2>If at least one identity is present in the = command, it is=20 always possible to perform a user identity to HSS resolution, as either=20 Public-Identity or User-Name can be used as SLF key entry to retrieve = the=20 correct HSS name.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Hope this helps!</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D862174209-20072006><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Lionel</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> </DIV> <DIV dir=3Dltr align=3Dleft><FONT face=3DTahoma = size=3D2><B>De :</B>=20 [email protected] [mailto:[email protected]] <B>De la part = de</B>=20 Paulo Rolo<BR><B>Envoy=E9 :</B> jeudi 20 juillet 2006=20 11:00<BR><B>=C0 :</B> [email protected]<BR><B>Objet :</B> = [AAA-WG]:=20 Diameter redirect<BR></FONT><BR></DIV> <DIV></DIV> <DIV class=3DSection1> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier = New'">Hello,<o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier = New'"><o:p> </o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">We are currently = developing=20 a set of Diameter interfaces and some doubts have arise, concerning SLF=20 usage.<o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier = New'"><o:p> </o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">On ETSI TS 123 228 = (IP=20 Multimedia Subsystem (IMS)) at section 5.8.1 (User identity to HSS = resolution)=20 it is suggested that a Public User Identity should be selected and used = as input=20 to SLF_QUERY, in order to resolve to the correct HSS name.=20 <o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier = New'"><o:p> </o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Also at section = 6.1.2=20 (S-CSCF registration/deregistration notification) of TS 129 228 (IP = Multimedia=20 (IM) Subsystem Cx and Dx Interfaces), it is suggested that if Routing=20 Information is not available for SAR (S-CSCF = registration/deregistration), it=20 should be routed to next diameter node, for example SLF. =20 <o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier = New'"><o:p> </o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">The issue is that = on TS 129=20 229 (Cx and Dx interfaces based on the Diameter protocol) at section = 6.1.3=20 (Server-Assignment-Request (SAR) Command) the Public-Identity is = presented as an=20 optional attribute. If it is not present how should be SLF_QUERY = performed? All=20 the other messages (UAR, LIR, MAR) have Public-Identity as=20 mandatory.<o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier = New'"><o:p> </o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier = New'"><o:p> </o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Thanks in=20 advance,<o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Paulo=20 Rolo<o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier = New'"><o:p> </o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Network and = Protocols=20 Unit<o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Intelligent = Networks=20 Department<o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><st1:country-region w:st=3D"on"><st1:place = w:st=3D"on"><FONT=20 face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier = New'">Portugal</SPAN></FONT></st1:place></st1:country-region><FONT=20 face=3D"Courier New" size=3D2><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"> Telecom = Inova=E7=E3o,=20 S.A<o:p></o:p></SPAN></FONT></P> <P class=3DMsoNormal><FONT face=3DVerdana size=3D2><SPAN lang=3DPT=20 style=3D"FONT-SIZE: 11pt; FONT-FAMILY: = Verdana"><o:p> </o:p></SPAN></FONT></P></DIV></BODY></HTML> ------_=_NextPart_001_01C6AC55.AD4FEAB4--