Two documents at /0105_Por

OKUBO Sakae okubo at GITI.WASEDA.AC.JP
Sat Apr 21 23:58:15 EDT 2001


Hi Chern,

  According to my understanding, when you say "Context Transfer", it refers
to some protocol having procedures and methods to trasfer the "Context". And
in IM and Presence, this context is the relevant IM and Presence
information.
Is that understanding correct?
If yes, then the H.MMS.3 will define the methods and procedures in H.323
protocol
to enable H.323 to act as a "Context Transfer" protocol.(Like SIP defines
new
methods SUBSCRIBE etc. to act as transport protocol for IM and Presence).
I think the concept of IM and Presence shall be derived from IETF IMPP, but
work
needs to be done to define their mapping in context of H.323 signalling.
Could you elaborate when you said "Hopefully some meaningful protocol name
would be link to it.Example (M.RCTP - Robust Context Transfer Protocol)".

thanks
Manoj.


-----Original Message-----
From: cny [mailto:cny at DCS.SHEF.AC.UK]
Sent: Saturday, April 21, 2001 12:58 PM
To: ITU-SG16 at mailbag.cps.INTEL.COM
Subject: Re: H.MMS.3: Presence and IM for H.323 Mobile systems.


Hi all,

May I know how much this thing will link to
IETF BXXP (Blocks Extensible Exchange Protocol), and
IETF IMPP (Instant Messaging and Presence Protocol) ?????

As for the new protocol mentioned below,
I suppose what is normally involved  is known as Context Transfer,
Hopefully some meaningful protocol name would be link to it.
Example (M.RCTP - Robust Context Transfer Protocol)

When is the dead line for the Brazil Meeting,
I am still rushing out some spec of this new protocol.

Cheers
Chern Nam Yap

----- Original Message -----
From: "Roy, Radhika R, ALCOO" <rrroy at ATT.COM>
To: <ITU-SG16 at mailbag.cps.intel.com>
Sent: Tuesday, April 17, 2001 3:24 PM
Subject: Re: H.MMS.3: Presence and IM for H.323 Mobile systems.


> Hi, Manoj:
>
> I am providing a very quick comment. It is a good proposal and you are
> assuming that H.MMS.1 will be the base protocol to be used.
>
> With respect to H.MMS.1 protocol, I like to mention that the mobility
> management part of H.MMS.1 will be "called" a NEW protocol and will NOT be
> called as "H.225.0 Annex G or its extension."

>
> Based on this assumption, probably you can start your work.
>
> As time goes on, more comments will be provided.
>
> I appreciate your work.
>
> Best regards,
> Radhika R. Roy
> AT&T
>
> -----Original Message-----
> From: Paul, Manoj [mailto:mpaul at TRILLIUM.COM]
> Sent: Monday, April 16, 2001 10:28 PM
> To: ITU-SG16 at MAILBAG.INTEL.COM
> Subject: H.MMS.3: Presence and IM for H.323 Mobile systems.
>
>
>   Hi All,
>     The purpose of this mail is to initiate work on H.MMS.3 standard,
which
> is
> a part of H.MMS series for H.323 mobility systems. H.MMS.3 will address
> Presence
> and Instant Messaging services in H.323 Mobility multimedia systems.
>     H.MMS.3 standard shall address the architecture, procedures and new
> message/
> information elements to enable H.323 as the transport protocol for
Presence
> and
> Instant Messaging in mobile environment.
>     As editor of H.MMS.3 document, I solicit contributions and discussions
> to
> begin work in this area. Enclosed is the Scope and Terms of Reference
> document
> that was presented in SG16 Launceston meeting for H.MMS.3.
>
> thanks
> Manoj Paul.
> Trillium Digital Systems, (an Intel company).
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> For help on this mail list, send "HELP ITU-SG16" in a message to
> listserv at mailbag.intel.com
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> For help on this mail list, send "HELP ITU-SG16" in a message to
> listserv at mailbag.intel.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv at mailbag.intel.com



More information about the sg16-avd mailing list