Re: Local and Remote Descriptor IP type
"Schwarz, Albrecht (Albrecht)" <[email protected]> Fri, 24 Feb 2012 09:47:05 +0100
| Newsgroups | gmane.ietf.megaco |
|---|---|
| Message-ID | <5F7BCCF5541B7444830A2288ABBEBC9621625F9D34@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> |
--===============1367474093506708377== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_5F7BCCF5541B7444830A2288ABBEBC9621625F9D34FRMRSSXCHMBSD_" --_000_5F7BCCF5541B7444830A2288ABBEBC9621625F9D34FRMRSSXCHMBSD_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Abhijit, 1st: there isn't any RFC, you got to use the ITU-T H.248.x-series of Recomm= endations concerning MEGACO protocol. 2nd: the H.248 stream is fundamentally a bidirectional construct, i.e., cov= ering two unidirectional media (or control) flows. However, each traffic direction may be different than the reverse direction= , sometimes called asymmetrical media (flows). Thus, it's definetely not a failure situation per se your use case. You may= use different IP protocol versions for each traffic direction! You may also use different media formats (e.g. different video or audio cod= ecs) for each traffic direction. Etc. -Albrecht ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of= Deepak Bissa Sent: Freitag, 24. Februar 2012 04:49 To: Abhijit Dutta; [email protected] Subject: Re: [Megaco] Local and Remote Descriptor IP type Hi, Megaco protocol does not impose such restrictions on SDP internals and it i= s possible to have such situation. MGCs "might not" look into these details and just tunnel it to respective M= Gs and then MG has to apply or reject such media connection. H.248.8 provides list of error codes that can be exchanged between MG and M= GC. "Not Implemented" could be one of the candidate. Regards, Deepak Bissa From: [email protected] [mailto:[email protected]] On Behalf Of= Abhijit Dutta Sent: Thursday, February 23, 2012 12:38 AM To: [email protected] Subject: [Megaco] Local and Remote Descriptor IP type Hi, Sorry for this na=EFve question - I am posting it since there is no clear = indication in the RFC. Can local and remote descriptor contain differ IP address types - one say = IPv4 and another IPv6. If not, what should the MGC return (error code) in r= eply during such situations. ~Thanx Abhijit =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D --_000_5F7BCCF5541B7444830A2288ABBEBC9621625F9D34FRMRSSXCHMBSD_ 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:x =3D=20 "urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20 "urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20 "urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20 "uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20 "uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20 "urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =3D= =20 "urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20 "urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20 "urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =3D=20 "urn:schemas-microsoft-com:office:odc" xmlns:oa =3D=20 "urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20 "http://www.w3.org/TR/REC-html40" xmlns:q =3D=20 "http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =3D=20 "http://microsoft.com/officenet/conferencing" XMLNS:D =3D "DAV:" XMLNS:Repl= =3D=20 "http://schemas.microsoft.com/repl/" xmlns:mt =3D=20 "http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =3D=20 "http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =3D=20 "http://www.passport.com/NameSpace.xsd" xmlns:ois =3D=20 "http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20 "http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20 "http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20 "http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20 "http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20 "http://www.w3.org/2001/XMLSchema" xmlns:sub =3D=20 "http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =3D= =20 "http://www.w3.org/2001/04/xmlenc#" xmlns:sp =3D=20 "http://schemas.microsoft.com/sharepoint/" xmlns:sps =3D=20 "http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20 "http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =3D=20 "http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =3D=20 "http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =3D=20 "http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =3D=20 "http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =3D=20 "http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =3D=20 "http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =3D=20 "http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mv= er =3D=20 "http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =3D=20 "http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20 "http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp = =3D=20 "http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =3D=20 "http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =3D= =20 "http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl = =3D=20 "http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =3D= =20 "http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksServ= ice"=20 XMLNS:Z =3D "urn:schemas-microsoft-com:" xmlns:st =3D "=01"><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"= > <META content=3D"MSHTML 6.00.2900.6169" name=3DGENERATOR> <STYLE> <!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal; font-family:"Calibri","sans-serif"; color:windowtext;} span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.Section1 {page:Section1;} --> </STYLE> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></HEAD> <BODY lang=3DEN-US vLink=3Dpurple link=3Dblue> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2>Abhijit,</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2>1st: there isn't any RFC, you got to use the ITU-T= =20 H.248.x-series of Recommendations concerning MEGACO=20 protocol.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2>2nd: the H.248 stream is fundamentally a bidirecti= onal=20 construct, i.e., covering two unidirectional media (or control)=20 flows.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2>However, each traffic direction may be different t= han the=20 reverse direction, sometimes called asymmetrical media=20 (flows).</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2>Thus, it's definetely not a failure situation per = se your=20 use case. You may use different IP protocol versions for each traffic= =20 direction!</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2>You may also use different media formats (e.g. dif= ferent=20 video or audio codecs) for each traffic direction. Etc.</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2>-Albrecht</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D562024208-24022012><FONT face=3D"= Courier New"=20 color=3D#800000 size=3D2></FONT></SPAN> </DIV><BR> <BLOCKQUOTE=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px soli= d; MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> [email protected]=20 [mailto:[email protected]] <B>On Behalf Of </B>Deepak=20 Bissa<BR><B>Sent:</B> Freitag, 24. Februar 2012 04:49<BR><B>To:</B> Abhij= it=20 Dutta; [email protected]<BR><B>Subject:</B> Re: [Megaco] Local and Remote=20 Descriptor IP type<BR></FONT><BR></DIV> <DIV></DIV> <DIV class=3DSection1> <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Hi,<o:p></o:p></SPAN>= </P> <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Megaco protocol does = not=20 impose such restrictions on SDP internals and it is possible to have such= =20 situation.<o:p></o:p></SPAN></P> <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">MGCs =93might not=94 = look into=20 these details and just tunnel it to respective MGs and then MG has to app= ly or=20 reject such media connection.<o:p></o:p></SPAN></P> <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p> </o:p></SP= AN></P> <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">H.248.8 provides list= of error=20 codes that can be exchanged between MG and MGC. =93Not Implemented= =94 could=20 be one of the candidate.<o:p></o:p></SPAN></P> <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p> </o:p></SP= AN></P> <DIV> <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Regards,<o:p></o:p></= SPAN></P> <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d">Deepak=20 Bissa<o:p></o:p></SPAN></P></DIV> <P class=3DMsoNormal><SPAN style=3D"COLOR: #1f497d"><o:p> </o:p></SP= AN></P> <DIV> <DIV=20 style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4= df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium n= one; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none"> <P class=3DMsoNormal><B><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN= ></B><SPAN=20 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20 [email protected] [mailto:[email protected]] <B>On Behalf Of= =20 </B>Abhijit Dutta<BR><B>Sent:</B> Thursday, February 23, 2012 12:38=20 AM<BR><B>To:</B> [email protected]<BR><B>Subject:</B> [Megaco] Local and Re= mote=20 Descriptor IP type<o:p></o:p></SPAN></P></DIV></DIV> <P class=3DMsoNormal><o:p> </o:p></P> <P class=3DMsoNormal><SPAN lang=3DEN-IN>Hi,<o:p></o:p></SPAN></P> <P class=3DMsoNormal><SPAN lang=3DEN-IN><o:p> </o:p></SPAN></P> <P class=3DMsoNormal><SPAN lang=3DEN-IN>Sorry for this na=EFve question -= I am=20 posting it since there is no clear indication in the=20 RFC.<o:p></o:p></SPAN></P> <P class=3DMsoNormal><SPAN lang=3DEN-IN><o:p> </o:p></SPAN></P> <P class=3DMsoNormal><SPAN lang=3DEN-IN>Can local and remote descriptor c= ontain=20 differ IP address types - one say IPv4 and another IPv6. If not, wh= at=20 should the MGC return (error code) in reply during such=20 situations.<o:p></o:p></SPAN></P> <P class=3DMsoNormal><SPAN lang=3DEN-IN><o:p> </o:p></SPAN></P> <P class=3DMsoNormal><SPAN=20 lang=3DEN-IN>~Thanx<BR>Abhijit<o:p></o:p></SPAN></P></DIV><BR><FONT face= =3DArial=20 color=3Dgray=20 size=3D2><BR><BR><BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>Please=20 refer to http://www.aricent.com/legal/email_disclaimer.html<BR>for import= ant=20 disclosures regarding this electronic=20 communication.<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR></BLOCKQUOTE></FONT></BODY></HTML> --_000_5F7BCCF5541B7444830A2288ABBEBC9621625F9D34FRMRSSXCHMBSD_-- --===============1367474093506708377== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Megaco mailing list [email protected] https://www.ietf.org/mailman/listinfo/megaco --===============1367474093506708377==--