Few questions on IMPP
"sivaram" <[email protected]> Thu, 15 May 2003 17:11:28 +0530
| Newsgroups | gmane.ietf.impp |
|---|---|
| Message-ID | <004001c31ad6$ecacb190$97b2a8c0@ec1103984> |
This is a multi-part message in MIME format. ------=_NextPart_000_0041_01C31B05.0664ED90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, I am new to the IMP area, so I am sorry if some of these questions sound naive. I found it difficult searching thru the archives for answers, so I thought I may as well ask these questions on this list. 1) While reading through CPIM doc (draft-ietf-impp-im-02), I found the MESSAGE operation being invoked from appl (refers to SENDER of RFC2778, I think) to the service. Why is there no invokation from service to the instant inbox (to deliver the message) ? Is it because, we assume the inbox is internal to the service (I thought inbox here would be part of whatever IM s/w, a end user is having). 2) CPP doc (draft-ietf-impp-pres-02): A similar question to the above. Why is there no operation from the presentity to the service to send the presence info ? 3) draft-ietf-impp-cpim-msgfmt-08.txt: Does this doc apply to only sending of IMs or is it for sending presence info as well ? If it is only for IM, why isn't there any document for conveying presence info (or why can't the same one be used for any info including presence) ? Thanks & Regards, Sivaram. **************************Disclaimer************************************ Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. *************************************************************************** ------=_NextPart_000_0041_01C31B05.0664ED90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset= =3Diso-8859-1"> <META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD> <BODY> <DIV><FONT face=3D"Courier New" size=3D2><SPAN=20 class=3D631140211-15052003>Hi,</SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN=20 class=3D631140211-15052003></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN class=3D631140211-15052003>I= am new to=20 the IMP area, so I am sorry if some of these questions sound naive. I found= it=20 difficult searching thru the archives for answers, so I thought I may as= well=20 ask these questions on this list. </SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN=20 class=3D631140211-15052003></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN class= =3D631140211-15052003>1) While=20 reading through CPIM doc (<SPAN lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language:= AR-SA">draft-ietf-impp-im-02),=20 I found the MESSAGE operation being invoked from appl (refers to SENDER of= =20 RFC2778, I think) to the service. Why is there no invokation from service= to the=20 instant inbox (to deliver the message) ? Is it because, we assume the inbox= is=20 internal to the service (I thought inbox here would be part of whatever IM= s/w,=20 a end user is having).</SPAN></SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN class= =3D631140211-15052003><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language:= AR-SA"></SPAN></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN class= =3D631140211-15052003><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language: AR-SA">2)=20 CPP doc (<SPAN lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language:= AR-SA">draft-ietf-impp-pres-02):=20 A similar question to the above. Why is there no operation from the= presentity=20 to the service to send the presence info= ?</SPAN></SPAN></SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN class= =3D631140211-15052003><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language:= AR-SA"></SPAN></SPAN></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN class= =3D631140211-15052003><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language: AR-SA">3)=20 <SPAN lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language:= AR-SA">draft-ietf-impp-cpim-msgfmt-08.txt:=20 Does this doc apply to only sending of IMs or is it for sending presence= info as=20 well ? If it is only for IM, why isn't there any document for conveying= presence=20 info (or why can't the same one be used for any info including presence)=20 ?</SPAN></SPAN></SPAN></SPAN></FONT></DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN class= =3D631140211-15052003><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language:= AR-SA"></SPAN></SPAN></SPAN></SPAN></FONT> </DIV> <DIV><FONT face=3D"Courier New" size=3D2><SPAN class= =3D631140211-15052003><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20 lang=3DEN-GB=20 style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman';= mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-GB;= mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Thanks=20 &=20 Regards,<BR>Sivaram.</SPAN></SPAN></SPAN></SPAN></FONT></DIV></BODY></HTML> <table><tr><td bgcolor=3D#ffffff><font color= =3D#000000><pre>**************************Disclaimer***********************= ************* Information contained in this E-MAIL being proprietary to Wipro Limited is= =20 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying= =20 or dissemination of the information contained in the E-MAIL in any manner=20 whatsoever is strictly prohibited. *************************************************************************** </pre></font></td></tr></table> ------=_NextPart_000_0041_01C31B05.0664ED90-- [reminder: [email protected] for non-technical discussions, please]