Draft-khan-ip-serv-peer-arch-03.txt SPEERMINT Peering Architecture IETF-66, Montreal, Canada Sohel Khan, Ph.D. Technology Strategist.

Slides:



Advertisements
Similar presentations
dynamicsoft Inc. Proprietary VON Developers Conference 1/19/00 C O N N E C T I N G T H E W O R L D W I T H A P P L I C A T I O N S.
Advertisements

SIP Interconnect Guidelines draft-hancock-sip-interconnect-guidelines-02 David Hancock, Daryl Malas.
International Telecommunication Union ENUM Issues and Solutions Houlin Zhao Director Telecommunication Standardization Bureau International Telecommunication.
1 IP Telephony (VoIP) CSI4118 Fall Introduction (1) A recent application of Internet technology – Voice over IP (VoIP): Transmission of voice.
Early Media Authorization Under what conditions should negotiated media flow prior to 200 OK (INVITE)? Richard Ejzak.
Voice over IP Fundamentals
© 2006 Cisco Systems, Inc. All rights reserved. Optimizing Converged Cisco Networks (ONT) Module 2: Cisco VoIP Implementations.
Omniran GPP Trusted WLAN Access to EPC Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Peering Architecture IETF-63 VoIP Peering BOF Sohel Khan, Sprint, TR&D August 4, 2005 Copyright © Sprint All rights reserved.
Internet Telephony Helen J. Wang Network Reading Group, Jan 27, 99 Acknowledgement: Jimmy, Bhaskar.
Agenda Introduction to 3GPP Introduction to SIP IP Multimedia Subsystem Service Routing in IMS Implementation Conclusions.
Secure Telephony Enabled Middle-box (STEM) Maggie Nguyen Dr. Mark Stamp SJSU - CS 265 Spring 2003 STEM is proposed as a solution to network vulnerabilities,
SIP Interconnect Guidelines draft-hancock-sip-interconnect-guidelines-03 David Hancock, Daryl Malas.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
1 CCM Deployment Models Wael K. Valencia Community College.
Copyright © 2006 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 draft-penno- message-flows-02 Reinaldo Penno, Daryl Malas, Adam Uzelac,
DTLS-SRTP Handling in SIP B2BUAs draft-ram-straw-b2bua-dtls-srtp IETF-91 Hawaii, Nov 12, 2014 Presenter: Tirumaleswar Reddy Authors: Ram Mohan, Tirumaleswar.
December 5, 2003FG3 Report FOCUS GROUP 3 Interoperability Report to NRIC VI Council December 5, 2003 Cliff Naughton (Boeing)
1 NGN Issues - Numbering and Addressing Peter Darling ACIF NGN FOG No. 3.
RIPE64 Enum Working Group DE-CIX NGN Services.
Networks – Network Architecture Network architecture is specification of design principles (including data formats and procedures) for creating a network.
Benefits of VoIP Peering in a Challenging Economy (SP-10) Tuesday - 02/03/09 4:00-4:45pm Mark Benisz, VP Americas, XConnect Global Networks.
1 Which Standards are needed toward Future Wireline and Wireless IP Network ? Hee Chang Chung, Jun Kyun Choi
© Copyright 2007 Arbinet-thexchange, Inc. All Rights Reserved. Voice Peering Steve Heap Chief Technology Officer.
Session Initiation Protocol (SIP). What is SIP? An application-layer protocol A control (signaling) protocol.
© Copyright 2007 Arbinet-thexchange, Inc. All Rights Reserved. VoIP Peering Pilot Using the Internet2 Backbone.
DOCUMENT #: GSC15-GTSC8-06 FOR: Presentation SOURCE: ATIS AGENDA ITEM: GTSC8; 4.2 CONTACT(S): Art Reilly ATIS Cybersecurity.
Sridhar Ramachandran Chief Technology Officer Core Session Controller.
Virtual Private Ad Hoc Networking Jeroen Hoebeke, Gerry Holderbeke, Ingrid Moerman, Bard Dhoedt and Piet Demeester 2006 July 15, 2009.
SPEERMINT Terminology Draft th IETF - Chicago Editors: Daryl Malas David Meyer.
1January 2006Richard Stastny Developments around Infrastucture ENUM and their relevance on NGNs Workshop on NGN Interconnection and Numbering TRIS – TISPAN.
September 15, 2003FG3 Report FOCUS GROUP 3 Interoperability Report to NRIC VI Council September 15, 2003 Cliff Naughton (Boeing)
Université du Québec École de technologie supérieure Department of software and IT engineering Real-time multi-user transcoding for push to talk over cellular.
Vic Liu Liang Xia Zu Qiang Speaker: Vic Liu China Mobile Network as a Service Architecture draft-liu-nvo3-naas-arch-01.
1 Presentation_ID © 1999, Cisco Systems, Inc. Cisco All-IP Mobile Wireless Network Reference Model Presentation_ID.
The State of VoIP Peering Charles Studt Director of Product Management, VoEX.
7/6/20061 Speermint Use Case for Cable IETF 66 Yiu L. Lee JULY 2006.
1 SPEERMINT Use Cases for Cable IETF 66 Montreal 11 JULY 2006 Presented by Yiu L. Lee.
IMS 架構與話務分析 網路管理維運資源中心 日期 : 2013/07/25 網路管理維運資源中心 日期 : 2013/07/25 限閱.
Security, NATs and Firewalls Ingate Systems. Basics of SIP Security.
QoS framework (PR0002) Rev.0.5 (Work in progress).
Session Initiation Protocol (SIP) Chapter 5 speaker : Wenping Zhang data :
Peering: A Minimalist Approach Rohan Mahy IETF 66 — Speermint WG.
Requirements for SIP-based VoIP Interconnection (BCP) draft-natale-sip-voip-requirements-00.txt Bob Natale For Consideration by the.
SIP Interconnect Guidelines draft-hancock-sip-interconnect-guidelines-01 David Hancock, Daryl Malas.
Page 1 IETF Speermint Working Group Speermint Requirements/Guidelines for SIP session peering draft-ietf-speermint-requirements-02 IETF 69 - Monday July.
1 VoIP Peering Peering, it’s not just for IP anymore Kingsley Hill XConnect Global Networks, Ltd VP for Strategic Federations.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
September 28, 2006 Page 1 3GPP2 MMD Status for IMS Workshop Jack Nasielski
Introduction to Active Directory
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
End-to-middle Security in SIP draft-ono-sipping-end2middle-security-04 Kumiko Ono IETF62.
17 February 2016 SIPPING - IEPREP Joint Meeting Fred Baker - IEPREP co-chair Rohan Mahy - SIPPING co-chair.
1 Internet Telephony: Architecture and Protocols an IETF Perspective Authors:Henning Schulzrinne, Jonathan Rosenberg. Presenter: Sambhrama Mundkur.
International Telecommunication Union ENUM Organizational Perspectives Richard Hill, for Houlin Zhao Director Telecommunication Standardization Bureau.
Page 1 IETF DRINKS Working Group Data Model and Protocol Requirements for DRINKS IETF 72 - Thursday July Tom Creighton -
IETF-68draft-ietf-speermint-voip- consolidated-usecases.txt 1 SIP Call Flows Changes and Plan draft-ietf-speermint-voip-consolidated-usecases.txt Adam.
SPEERMINT Architecture - Reinaldo Penno Juniper Networks SPEERMINT, IETF 70 Vancouver, Canada 2 December 2007.
IEEE MEDIA INDEPENDENT HANDOVER DCN: hwnm Title: Thoughts on IEEE relation with IEEE Date Submitted: May 13, 2010.
J. Halpern (Ericsson), C. Pignataro (Cisco)
RTP Taxonomy & draft-lennox-raiarea-rtp-grouping-taxonomy-03 IETF 88 1.
1Security for Service Providers – Dave Gladwin – Newport Networks – SIP ’04 – 22-Jan-04 Security for Service Providers Protecting Service Infrastructure.
VoIP ALLPPT.com _ Free PowerPoint Templates, Diagrams and Charts.
IP Telephony (VoIP).
IP-NNI Joint Task Force Status Update
Teleconference Agenda
The Domain Policy DDDS Application
Session Initiation Protocol (SIP)
IP-NNI Joint Task Force Status Update
IP Interconnection Profile
Presentation transcript:

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) Enterprise Provider A (L5) Enterprise Provider B (L5) Service Provider C (L5) Service Provider D (L5) Enterprise Provider E (L5) Service Provider G (L5) Enterprise Provider F (L5) Service Provider 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 OF LF 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 SF MF QF AF Security Sohel Khan, Ph.D., Sprint-Nextel LF 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 SF MF 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 be forwarded 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