: Diameter redirect
"Paulo Rolo" <[email protected]> Thu, 20 Jul 2006 09:59:35 +0100
| Newsgroups | gmane.ietf.aaa |
|---|---|
| Message-ID | <75D349FBF7C131408F5061B7168072C30332A1BA@INOAVREX06.ptin.corpPT.com> |
This is a multi-part message in MIME format.
------_=_NextPart_001_01C6ABDA.D372E7A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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_01C6ABDA.D372E7A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Verdana;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Hello,<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>We are currently =
developing
a set of Diameter interfaces and some doubts have arise, concerning SLF =
usage.<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>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. =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>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.=A0 =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>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.<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Thanks in =
advance,<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Paulo =
Rolo<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Network and =
Protocols Unit<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Intelligent =
Networks
Department<o:p></o:p></span></font></p>
<p class=3DMsoNormal style=3D'text-autospace:none'><st1:country-region =
w:st=3D"on"><st1:place
w:st=3D"on"><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier =
New"'>Portugal</span></font></st1:place></st1:country-region><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>
Telecom Inova=E7=E3o, S.A<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span lang=3DPT =
style=3D'font-size:
11.0pt;font-family:Verdana'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C6ABDA.D372E7A0--