VS: [Speermint] Updated Draft: SPEERMINT Peering Architecture

["Nieminen Klaus" <[e-mail]>]

Hi folks,
 
Richard is right. From the charter:
 
> Issues that are out of scope for SPEERMINT include: 
>
> Routing of sessions which are not signaled using SIP. In
> particular, SPEERMINT is constrained to consider only those
> scenarios in which call routing is signaled using the SIP
> protocol and addressed by SIP or SIPS URIs. E.164 numbers and
> other national or private formats may only be used as defined
> within the SIP protocols, and 

So SPEERMINT is using only SIP/SIPS URIs, not E.164 numbers, so there is no number portability issue for SPEERMINT.
 
However, I understand that you need a mechanism to do cope with NP also in the SIP interconnection case and that can be done using infrastructure ENUM (in fact we are now discussing implementing one in Finland). The right place to discuss infrastructure ENUM is the ENUM WG.
 
I do not know if this is also out of our current scope, but I would like to discuss transferring charging/tariff information between providers in realtime. I want to raise this question, because at least in Finland we have been used to transferring charging information (pulse charging) in PSTN interconnection interface. This is for example used also in value added services that are billed by the caller's operator.

And I believe that we are not only ones that see this capability benefical. In fact it is required, if we want to enable SIP-based interconnection also for premium rate numbers and I consider it quite essential. 
 
Therefore, I want to ask that do you see that we need a mechanism to transfer charging data in SIP interconnection interface and do we have anything ready for that?
 
regards,
 
- Klaus -

________________________________

Lähettäjä: Stastny Richard [mailto:[e-mail]]
Lähetetty: su 28.5.2006 11:07
Vastaanottaja: Khan, Sohel Q [CTO]
Kopio: [e-mail]
Aihe: Re: [Speermint] Updated Draft: SPEERMINT Peering Architecture



I do not know how often I stated here that numbering issues
(and therefore also NUMBER Portability issues) are out-of-scope
in SPEERMINT

So NUMBER Portablility cannot ne addressed in SPEERMINT LF

Or we change the SPEERMINT charter

Richard

________________________________

Von: Khan, Sohel Q [CTO] [mailto:[e-mail]]
Gesendet: So 28.05.2006 06:48
An: Stastny Richard; Reinaldo Penno
Cc: [e-mail]
Betreff: RE: [Speermint] Updated Draft: SPEERMINT Peering Architecture



I think issues of mobility and number portability need to be addressed together in SPEERMINT LF.

Sohel Khan, Ph.D.
Sprint-Nextel

_______________________________________________
Speermint mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/speermint