IETF Logo Mail Archive

RE: [Speermint] Updated Draft: SPEERMINT Peering Architecture

"Francois D. Menard" <fmenard@xittelecom.com> Sat, 27 May 2006 01:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjnbI-0003y5-7l; Fri, 26 May 2006 21:28:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjnbH-0003y0-Pd for speermint@ietf.org; Fri, 26 May 2006 21:28:19 -0400
Received: from [205.151.208.34] (helo=fw.tr.xittelecom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FjnbG-0002Bi-Gp for speermint@ietf.org; Fri, 26 May 2006 21:28:19 -0400
Received: from [192.168.2.139] (helo=gestionfm) by fw.tr.xittelecom.com with esmtp (Exim 3.36 #1 (Debian)) id 1Fv2t2-0002kR-00; Mon, 26 Jun 2006 22:01:08 -0400
From: "Francois D. Menard" <fmenard@xittelecom.com>
To: 'Patrick Melampy' <PMelampy@acmepacket.com>, 'Otmar Lendl' <lendl@nic.at>
Subject: RE: [Speermint] Updated Draft: SPEERMINT Peering Architecture
Date: Fri, 26 May 2006 21:25:52 -0400
Message-ID: <01d201c6812c$84974c90$8b02a8c0@gestionfm>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <03b101c680e4$3e963cd0$0202fea9@acmepacket.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: AcaAyUyv8ZiW0Tq0QsyFoiRh/84djAAGORqAABJ4vrA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: "'Khan, Sohel Q [CTO]'" <Sohel.Q.Khan@sprint.com>, speermint@ietf.org
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
Errors-To: speermint-bounces@ietf.org

Patrick Melampy wrote:

> An issue does arise when thinking about PSTN numbers. Since many carriers
will have an interface to the PSTN, these are not owned by any domain. Thus
we may need to expand support for PSTN reachable numbers somehow? One idea
would be to also perform subscribe and notify for partial E.164 numbers
similar to how it was proposed in the TRIP protocol. 

I would motion that SPEERMINT only deals with E.164 numbers that are
acessible across a SIP NNI. Any E.164 numbers that are also reacheable over
TDM is out of scope.

F.






-----Original Message-----
From: Otmar Lendl [mailto:lendl@nic.at]
Sent: Friday, May 26, 2006 9:36 AM
To: Patrick Melampy
Cc: 'Michael Hammer (mhammer)'; 'Khan, Sohel Q [CTO]'; speermint@ietf.org
Subject: Re: [Speermint] Updated Draft: SPEERMINT Peering Architecture

On 2006/05/24 17:05, Patrick Melampy <PMelampy@acmepacket.com> wrote:
> Subscriptions have other beneficial attributes -- as they can work 
> across network boundaries and have context. Subscribe/Notify can 
> deliver a policy that corresponds to a reverse flow of SIP traffic. 
> Plus the Notification
can
> provide near real time changes. Also very contextual data can be 
> included
in
> the notification -- providing a nice mechanism for automatic 
> congestion control.
> 
> I like DNS providing LOCATION only, and I like the notion of all other 
> attributes that have a contextual base to be delivered in a contextual
way.

I think I can see your point.

I still have a serious problem regarding how to bootstrap such a system as

* Carriers seem to hate to expose their SIP ingress elements to the open
  Internet. They firewall, use private address spaces (e.g. GRX) or
  otherwise block incoming SIP calls before they reach the SIP stack.

* we want to avoid a mandatory bilateral configuration of peerings.
  
Could you sketch how a dynamic peering discovery could work with a SIP
subscription model?

/ol
--
< Otmar Lendl (lendl@nic.at) | nic.at Systems Engineer >


_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint


_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint

v2.23.0 | Report a Bug | By Email