draft-khan-ip-serv-peer-arch-03.txt

SPEERMINT Peering Architecture IETF-66, Montreal, Canada

Sohel Khan, Ph.D.Technology Strategist

2

Status

• New authors Reinaldo Penno, Juniper Network Daryl Malas, Level 3 Sohel Khan, Sprint Adam Uzelac, Global Crossing Mike Hammer, Cisco

• Important Contributor Otmar Lendl

• Signification revision as per the input from the IETF-65 meeting the mailing list

• Since, there are significant changes, we will go over the whole draft once again

Sohel Khan, Ph.D., Sprint-Nextel

3

Introduction

• The Draft Defines

a reference SPEERMINT architecture

functional components

and peering interface functions

Sohel Khan, Ph.D., Sprint-Nextel

4

Peering Network Context

Public (L3)

Private (L3)

L3 Peering Point(out of scope)

EnterpriseProvider A (L5)

EnterpriseProvider B (L5)

ServiceProvider C (L5)

ServiceProvider D (L5)

EnterpriseProvider E (L5)

ServiceProvider G (L5)

EnterpriseProvider F (L5)

ServiceProvider H (L5)

Public Peering Function/Federation Entity Location Function

Sohel Khan, Ph.D., Sprint-Nextel

Private Peering Function/Federation Entity Location Function

5

Federation

• A providers' group that has contractual agreements on various aspects of

peering relationship such as common:

administrative policy, settlement, and terminating calls.

• The members of a federation may jointly use a set of entities such as:

location function, application servers, subscriber databases, SIP proxies , and/or platforms that synthesize various SIP and non-

SIP based applications.

Sohel Khan, Ph.D., Sprint-Nextel

6

Reference Peering Architecture

Enables media paths interconnection between endpoints MF

SF

Enables discovery of SF or exchanges policy/parameters to be used by SF OF

Enables discovery of the SF or OFLF

PurposeRef.

Security

QF Negotiates and reserves bandwidth resources, as well as polices/provides measurements for media paths

SIP Service Provider Y

SIP Service Provider X

OF OF

SF SF

MF MF

QF QF

AFAF

Security

Sohel Khan, Ph.D., Sprint-Nextel

LF LFLF

Enables discovery of endpoints, assists in discovery and exchange of parameters to be used with the MF

AF Application Function: TBD or deleted

7

Location Function (LF)

• Enables discovery of the next hop peering signaling function (SF) or operation function (OF)

• Provides trusted registry database service• Can be Internal or external to a federation if a federation exists

• Examples: ENUM DNS Global Public Database (if hierarchical system exists ) SIP Redirect Server

• Out of scope Number portability Mobility Function

Sohel Khan, Ph.D., Sprint-Nextel

8

Location Function Examples

ENUM: o Input: E.164 o Output: SIP AoR of a next hop Signaling Function (SF) or OF.

DNS: o Input: Domain Name from the AoR of an end user o Output: SIP AoR of the next hop Signaling Function (SF)

Global Public Database (if hierarchical system exists): o Input:

Local Signaling address (local context) The domain name of an end user the domain name of a destination service provider

o Output: The next hop reachable address.

SIP Redirect Server o Input: E.164 address or domain Name from the AoR of an end user o Output: SIP AoR of the next hop Signaling Function (SF)

Sohel Khan, Ph.D., Sprint-Nextel

9

Operation Function (OF)

• Enables discovery of SF • Exchanges policy/parameters to be used by SF

• Implementation is optional

• Examples Dynamic subscribe, notify, and exchange of policy information and parameters among providers SLA Exchange Accounting Data Exchange

Sohel Khan, Ph.D., Sprint-Nextel

10

Signaling Function (SF)

• Performs L5 peering function Enables discovery of endpoints, Assists in discovery and exchange of parameters to be used

with the MF

• Examples of main components: SIP Proxy, SIP B2BUA as per SIP RFCs

• Other examples (optional) Session Admission Control (SAC) SIP DoS Protection SIP Topology Hiding SIP Security, Privacy, and Encryption

Sohel Khan, Ph.D., Sprint-Nextel

11

Media Function (MF)

• Enables media paths interconnection between endpoints

• Examples: Transcoding of one voice coding to other

e.g., G.711 to EvRC RTP Relay Media security

Sohel Khan, Ph.D., Sprint-Nextel

12

QoS Function (QF)

• Negotiates and reserves bandwidth resources, as well as polices/provides measurements for media paths

• Ensures incoming and outgoing packets are marked correctly according to federation and peer policy Implementation is Optional unless government regulation

mandates Various standard body should agree on a compatible set of SIP

priority header mapping with particular attention to ETS/WPS

Sohel Khan, Ph.D., Sprint-Nextel

13

Application Function (AF)

• Do we need it?

• If we need it Please write use cases in the discussion list

Sohel Khan, Ph.D., Sprint-Nextel

14

Deployment Option

SIP Service Provider Y

SIP Service Provider X

SF

MF

SFMF

SIP

RTP

• Composed or Decomposed: SF and MF• Centralized or Distributed: whether logical and physical functions are in one geographical point• or functions are distributed among multiple geographical locations

When one SF controls multiple MFs, which MF (IP address) the media should beforwarded to?

Sohel Khan, Ph.D., Sprint-Nextel

15

Next Step

• Continue to improve the draft

• Accept the draft as a working group item

Sohel Khan, Ph.D., Sprint-Nextel