Re: [Speermint] New Draft: SIP Interconnect Guideline
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Speermint] New Draft: SIP Interconnect Guideline



Title: [Speermint] New Draft: SIP Interconnect Guideline
Daryl:
David:
 
I took a quick look at the I-D and want to be sure I understand what's being said about  called user identification. In Section 4.2.1 is the identification of the rn in  the case of a ported number just for sub subsequent interworking back to SS7/circuit switched networks or something else? I tend to think of ENUM-based routing mechanisms as being portability corrected to begin with so number portability info should only be required where subsequent interworking has to take place.
 thanks,
 
Penn Pfautz
AT&T Access Management
+1-732-420-4962
 


From: speermint-bounces at ietf.org [mailto:speermint-bounces at ietf.org] On Behalf Of Daryl Malas
Sent: Wednesday, March 04, 2009 6:38 PM
To: speermint at ietf.org
Cc: David Hancock
Subject: [Speermint] New Draft: SIP Interconnect Guideline

All,

We have submitted a new draft beginning a process for defining a SIP interconnect guideline for peering.   Of the operators I have spoken with regarding their experiences with peering, SIP interworking is the most challenging process to work through.  Establishing a guideline will be a fundamental step in enabling SSPs to peer quickly, efficiently, and dynamically.

A New Internet-Draft is available from the on-line Internet-Drafts directories.

    Title           : draft-hancock-sip-interconnect-guidelines-00
    Author(s)       : D. Hancock, D. Malas
    Filename        : draft-hancock-sip-interconnect-guidelines-00.txt
    Pages           : 25
    Date            : 2009-03-04

As Session Initiation Protocol (SIP) peering becomes more widely
accepted by service providers the need to define an interconnect
guideline becomes of greater value.  This document takes into
consideration the SIP and commonly used SIP extensions, and it
defines a fundamental set of requirements for SIP Service Providers
(SSPs) to implement within their signaling functions (SFs) or
Signaling Path Border Elements (SBEs) for peering.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-hancock-sip-interconnect-guidelines-00.txt

Regards,

Daryl

-----------------
Daryl Malas
CableLabs
(o) +1 303 661 3302
(f) +1 303 661 9199
mailto:d.malas at cablelabs.com


Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.