[Enum] Carrier ENUM

["Stastny Richard" <Richard.Stastny at oefeg.at>]

Dear all,
 
After finally adopting "Carrier" ENUM in ENUM WG, the discussion
at the voipeer mailing list shows that there is a problem with the
term "carrier" and VoiP Peering and want to replace the term
with something else, e.g. RTCSP
 
So doe we now have RTCSP ENUM?
 
No
 
VoIP peering is basically be talking about peering
between SIP servers and the routing is done naturally
via sip URI.. You do not need an E.164 number to do so.
 
User and Carrier ENUM is controlled from the E.164 end
and so you have to play along the rules of E.164.
 
User ENUM is for End User (the entity who has
the right to "use" the number.
 
Carrier ENUM is for "Carriers" (I am also
not very happy with this term - so another
term may be also here necessary)
but this MUST NOT be the same term
be used in voipeer. the term
MUST indicate the linkage to
E.164 numbers, that is for entities
which give E.164 numbers to end-users
and which are "hosting" the related services for 
the End-users.
 
This is clear for geo-graphic numbers, for
service numbers there is some additional
discussion necessary, e.g. 800 numbers
or corporate numbers can (e.g. in Austria) assigened from
the regulator either via a "Carrier" or DIRECTLY 
to the End-user, e.g. an enterprise To use these
numbers on the PSTN , the enterprise needs to find
a carrier hosting these numbers.
 
Q: the enterprise of course has the right to opt-in in
user ENUM, but what about carrier ENUM?
 
In the sinnreich.com case discussed. Henry may voippeer
with MCI directly, the situation in ENUM is depending on
the E.164 numbers he wants to use
 
-regards
Richard
 
_____________________________________________________________________________ List Archive: http://darkwing.uoregon.edu/~llynch/voipeer/ User Tools: http://darkwing.uoregon.edu/~llynch/voipeer.html 

_______________________________________________
enum mailing list
enum at ietf.org
https://www1.ietf.org/mailman/listinfo/enum