Mob ad hoc group progress
Roy, Radhika R, ALARC
rrroy at ATT.COM
Tue Apr 4 08:31:07 EDT 2000
Paul:
Thanks for clarifications.
In the last conf call, we even cannot complete the simple intra-zone
(intra-network, inter-network) scenarios first. You are right that we should
concentrate on the scenarios (Registration procedures, Gatekeeper discovery,
Location update, Call establishment, Mid-Call scenarios (e.g. supplementary
services, user interaction, Call release).
Definitely, we can go further: Inter-Zone (intra-domain) scenarios as well
if we can agree on the first one. AT&T contributions already contain many of
those aspects. Hope to bring new contributions explaining further in both
scenarios.
Best regards,
Radhika R. Roy
AT&T
> -----Original Message-----
> From: Guram Paul-LPG019 [SMTP:lpg019 at EMAIL.MOT.COM]
> Sent: Sunday, April 02, 2000 3:52 PM
> To: ITU-SG16 at MAILBAG.INTEL.COM
> Subject: Re: Mob ad hoc group progress
>
> Radhika,
>
> Conf call is for Annex H only as before...nothing has changed...change can
> only take place when the group agrees. Please do not read into the email
> more than what it says. I was only trying to highlight, in a high level
> report, the plight of Annex I since nothing much has moved in it, and it
> is
> an Annex which together with Annex H covers the mobility aspects. As far
> as
> Annex E is concerned, the point was that the mapping was the work of one
> individual or one company, thus could have errors or omissions (more than
> likely)...again only highlighting to people to check out this mapping.
>
> Contributions for next conf call to be for All H.323 intra-network
> scenario
> for:
> Registration procedures, Gatekeeper discovery, Location
> update, Call establishment, Mid-Call scenarios (e.g.
> supplementary services,
> user interaction), Call release. Also contributions on
> any
> impacts on the already specified architecture in the light of the present
> work are welcome.
>
> Paul
>
>
>
> -----Original Message-----
> From: Roy, Radhika R, ALARC [mailto:rrroy at ATT.COM]
> Sent: 01 April 2000 00:00
> To: ITU-SG16 at mailbag.cps.intel.com
> Subject: Re: Mob ad hoc group progress
>
> Hi, Paul and Mobility Group:
>
> I like to see that it should be clarified via emails
> whether
> H.323 Annex I
> and H.246 Annex E will be a part of the conference call.
> My
> personal
> preference is not to discuss annexes I and E during the
> conference call
> although email discussions will be preferred.
>
> If Annex I and E are included in the conference call, I
> like
> to see the
> actual time in the agenda when these items will be
> discussed
> so that people
> can best use their time in joining the particular time
> slot
> for each Annex.
>
> The proposal is as follows:
>
> 1. The upcoming conference call to be dedicated for H.323
> Annex H.
> 2. Let both editors of H.323 Annex I and H.246 Annex E
> propose via emails
> whether any issues to addressed.
> 3. If annex I and E are included in the agenda of the
> upcoming conference
> call, I like to the time slots when these annexes will be
> discussed so that
> people can join the particular time slots of interest.
> Alternatively,
> separate conference calls can be arranged for annexes I
> and
> E.
> 4. Are editors or any members of the mobility group sure
> what would be the
> scope of work (I guess that Annex E is stable for now -
> thanks to the
> editor) for those annexes?
>
> Paul: Would you please clarify what specific area that we
> need to discuss
> for the next conference call for H.323 Annex H? My guess
> is
> that we may
> start with intra-zone communication first. I am planning
> to
> bring
> contribution(s) describing this for mobility management:
> Discovery,
> Registration, Location Updates, and Call Establishment.
>
> I would appreciate comments form all members.
>
> Best regards,
>
> Radhika R. Roy
> AT&T
> H.323 Ad Hoc Mobility Group
>
More information about the sg16-avd
mailing list