[Speermint] SPEERMINT Peering Architecture - LF - OF - SF
"Stastny Richard" <Richard.Stastny@oefeg.at> Tue, 23 May 2006 21:04 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fie3e-0005im-HY; Tue, 23 May 2006 17:04:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fie3d-0005ib-HG for speermint@ietf.org; Tue, 23 May 2006 17:04:49 -0400
Received: from mail.oefeg.at ([62.47.121.5]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fie3a-0003fy-3J for speermint@ietf.org; Tue, 23 May 2006 17:04:49 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 May 2006 23:08:51 +0200
Message-ID: <32755D354E6B65498C3BD9FD496C7D462C4A62@oefeg-s04.oefeg.loc>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: SPEERMINT Peering Architecture - LF - OF - SF
Thread-Index: AcZ55c9pook8AV07QCuSGZUVJZHNwAAALQwwAAMtGwAAALabEAAtwXjAAPK/xLAAAMWBMAAFEnSQAADsacAAAXIwMAAAWSswAAMILuAAATumxg==
From: Stastny Richard <Richard.Stastny@oefeg.at>
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>, Brian Rosen <br@brianrosen.net>, "Francois D. Menard" <fmenard@xittelecom.com>, "Khan, Sohel Q [CTO]" <Sohel.Q.Khan@sprint.com>, David Meyer <dmm@1-4-5.net>, speermint@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc:
Subject: [Speermint] SPEERMINT Peering Architecture - LF - OF - SF
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
Folks, One general statement in advance: Coming from the VON Europe last week with discussions about walled garden and IMS, my overall expression is that this draft in IMS in text-mode. I have another question for clarification to this draft, because I am confused: I do not understand that the LF is discovering the OF o Location Function (LF): Purpose is to enable discovery of the OF peering point. o Operation Function (OF): Purpose is to enable discovery and exchange of policy and parameters to be used in with the SF peering point. o Signaling Function (SF): Purpose is to enable the discovery of endpoints and assist in discovery and exchange of parameters to be used with the MF peering point. I always had the naive idea (also triggered by the SPEERMINT chartert that e.g. ENUM is a LF and discovering the SIP URIs uses in the SF How is now OF coming in between thsi, especially what is listed in the draft, especially CALEA, Accounting and Applications? "Operational data mediation: TBD o CALEA implementation: TBD o Accounting: Call Detail Record's (CDR's) MAY be collected to be utilized by the peering operators. Based on the application, the format should be an open standard for common consumption of billing systems. Operators may use this data for a number of reasons, including billing in the event the peering relationship becomes asymmetric (unbalanced traffic flow) or there is a Tier 1 to Tier 2 relationship. In order to limit the potential for billing systems to impact the OF, a separate server should be created to maintain all records collected from a single interconnection to any number of OF's. An OF can also be a special function that contains bi-laterally disclosed information about the application servers and databases of each IP service provider. An example of this function is to allow a session to select a better suited application server from a set of application servers located inside both service providers' network. " Richard _______________________________________________ Speermint mailing list Speermint@ietf.org https://www1.ietf.org/mailman/listinfo/speermint
- [Speermint] SPEERMINT Peering Architecture - LF -… Stastny Richard
- [Speermint] RE: SPEERMINT Peering Architecture - … Michael Hammer (mhammer)
- [Speermint] RE: SPEERMINT Peering Architecture - … Stastny Richard
- [Speermint] RE: SPEERMINT Peering Architecture - … Michael Hammer (mhammer)
- Re: [Speermint] RE: SPEERMINT Peering Architectur… Stastny Richard
- Re: [Speermint] RE: SPEERMINT Peering Architectur… Stastny Richard
- Re: [Speermint] RE: SPEERMINT Peering Architectur… Stastny Richard
- RE: [Speermint] RE: SPEERMINT Peering Architectur… Michael Hammer (mhammer)