Subject: Re: ephemeral Identifiers

From: Brian Rosen <[email-masked]>
Date: Tue, 9 Nov 1999 14:51:22 -0500

> Hello Madhubabu,
>
> Although it is addressed to Brian, I am giving my
> interpretation of the things. Hope
> it helps.
>
> > 1) Considering the virtual MG case where the network
> interface is shared by more
> > than one MGC, If two different MGCs specify the same
> ephemeral identifier to be
> > added to context what is the action to be taken at MG? Is
> it that one MGC
> > request is processed and for other MGC an "terminationId is
> already in Context"
> > error message is generated?
>
> While adding ephemeral terminations to a context, CHOOSE
> termination id is used, MG
> creates the ephemeral termination and gives the exact
> termination id in its reply to
> MGC. As specific ephemeral ids can not be specifed in the Add
> command, therefore, it
> will not be possible for two MGCs to specify the same
> ephemeral id in the "Add"
> command.
I agree, the MG assigns ALL terminationIDs, and specifically,
ephemeral terminationIds.  You must use CHOOSE when Adding an
ephemeral.
>
> > 2) What is the method of differentiating ephemeral
> termination identifier with
> > the physical termination identifiers, without looking into
> the body of the
> > message.
>
> Since termination ids are assigned by the MG, there can be an
> implementation
> dependant way of differentiating ephemeral termination ids
> from the physical
> termination ids based on the name / structure of termination id.
>
Of course one must ask, in what way do you need to differentiate?
Generally, you know, because you ask for one to be created and you
get it's name back.  You can audit to find out other information.

Brian