Session Peering Use Cases for Federations David Schwartz – Kayote Networks Eli Katz - XConnect Jeremy Barkan - Digitalshtick draft-schwartz-speermint-use-cases-federations-00.txt.

Slides:



Advertisements
Similar presentations
1 An Update on Multihoming in IPv6 Report on IETF Activity IPv6 Technical SIG 1 Sept 2004 APNIC18, Nadi, Fiji Geoff Huston.
Advertisements

© 2006 NEC Corporation - Confidential age 1 November SPEERMINT Security Threats and Suggested Countermeasures draft-ietf-speermint-voipthreats-01.
THIS IS THE WAY ENUM Variants Jim McEachern Carrier VoIP Standards Strategy THIS IS.
1 CCSDS Security Architecture Key Management 13 th April 2005 Athens.
SIP issues with S/MIME and CMS Rohan Mahy SIP, SIPPING co-chair.
Security in VoIP Networks Juan C Pelaez Florida Atlantic University Security in VoIP Networks Juan C Pelaez Florida Atlantic University.
Key Negotiation Protocol & Trust Router draft-howlett-radsec-knp ABFAB, IETF March, Prague.
September 19, 2006speermint interim1 VoIP Threats and Attacks Alan Johnston.
Media Description for IKE in SDP draft-saito-mmusic-sdp-ike-01 Makoto Saito Dan Wing
Multihop Federations draft-mrw-abfab-multihop-fed-01.txt Margaret Wasserman
July 16, 2003AAA WG, IETF 571 AAA WG Meeting IETF 57 Vienna, Austria Wednesday, July 16,
Copyright © 2006 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 draft-penno- message-flows-02 Reinaldo Penno, Daryl Malas, Adam Uzelac,
DNS.
Document IPW-41 IP and Telecoms Interworking Workshop N umbering, Naming Addressing and Routing IETF EMUM WG Proposal International Telecommunication Union.
Ingate & Dialogic Technical Presentation SIP Trunking Focused.
ENUM? “ Telephone Number Mapping (ENUM or Enum, from TElephone NUmber Mapping) is a suite of protocols to unify the telephone numbering system E.164 with.
1 Open Pluggable Edge Services OPES Abbie Barbir, Ph.D.
1 XConnect Confidential Bridging the VoIP Islands with Federated Peering and ENUM Presentation to the SIPSIG Infrastructure ENUM Workshop Den Haag, NL.
Application-Layer Anycasting By Samarat Bhattacharjee et al. Presented by Matt Miller September 30, 2002.
ENUM Update for voipeer BOF Richard Shockey ENUM co-chair IETF 63 Paris.
Cosc 4765 SSL/TLS and VPN. SSL and TLS We can apply this generally, but also from a prospective of web services. Multi-layered: –S-http (secure http),
Session Initiation Protocol (SIP). What is SIP? An application-layer protocol A control (signaling) protocol.
IETF54 Charter Issues Dealt with since IETF53 PANA WG Meeting Basavaraj Patil.
Unrestricted Connection Manager MIF WG IETF 79, Beijing Gaétan Feige - Cisco Pierrick Seïté, France Telecom - Orange
Hemant Sengar, George Mason University
Draft-khan-ip-serv-peer-arch-03.txt SPEERMINT Peering Architecture IETF-66, Montreal, Canada Sohel Khan, Ph.D. Technology Strategist.
1 Barriers to Enum What VoIP providers ask about Enum Dr. Dorgham Sisalem.
IP Network Clearinghouse Solutions ENUM IP-Enabling The Global Telephone Directory Frank Estes Vice President , ext 224
SPEERMINT Terminology Draft th IETF - Chicago Editors: Daryl Malas David Meyer.
Dynamic Virtual Networks (DVNE) Margaret Wasserman & Paddy Nallur November 11, 2010 IETF Beijing, China.
1January 2006Richard Stastny Developments around Infrastucture ENUM and their relevance on NGNs Workshop on NGN Interconnection and Numbering TRIS – TISPAN.
1 Security Protocols in the Internet Source: Chapter 31 Data Communications & Networking Forouzan Third Edition.
Media Gateway Figure 8-1 Comparing PSTN and VoIP voice call setup.
Peering Considerations for Directory Assistance and Operator Services - John Haluska Telcordia SPEERMINT, IETF 68 Prague, Czech Republic 20 March 2007.
DNS SRV and NAPTR Use for SPEERMINT - Tom Creighton, Gaurav Khandpur Comcast SPEERMINT Intermin Meeting Philadelphia Sept
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.
Call signaling/Media control
SEC Identity_of_registrar_CSE Identity of Registrar CSE Group Name: SEC, ARC and PRO Source:FUJITSU Meeting Date: Agenda Item: Authentication.
1 SPEERMINT Use Cases for Cable IETF 66 Montreal 11 JULY 2006 Presented by Yiu L. Lee.
Draft-newton-speermint-itsp- problem-statement Andrew Newton 19 - September SPEERMINT WG Interim Meeting Philadelphia, PA, US.
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.
Securing Data Transmission and Authentication. Securing Traffic with IPSec IPSec allows us to protect our network from within IPSec secures the IP protocol.
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
Cryptography and Network Security Chapter 16 Fifth Edition by William Stallings Lecture slides by Lawrie Brown.
Presentation at ISMS WG Meeting1 ISMS – March 2005 IETF David T. Perkins.
IETF 67 – SPEERMINT WG Presence Use Cases draft-houri-speermint-usecase-presence-00 Avshalom Houri – IBM Edwin Aoki – AOL LLC Sriram Parameswar - Microsoft.
IPSec is a suite of protocols defined by the Internet Engineering Task Force (IETF) to provide security services at the network layer. standard protocol.
Design Considerations for the Common MIH Protocol Functions draft-hepworth-mipshop-mih-design-considerations-01 Ele Hepworth (*), Robert Hancock, Srinivas.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
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.
Securing Access to Data Using IPsec Josh Jones Cosc352.
DOTS Requirements Andrew Mortensen November 2015 IETF 94 1.
IP Telephony (VoIP).
THIS IS THE WAY ENUM Variants Jim McEachern
IP-NNI Joint Task Force Status Update
IEEE 802 OmniRAN Study Group: SDN Use Case
The Domain Policy DDDS Application
Session Initiation Protocol (SIP)
Media Independent Handover Services and Interoperability
An Update on Multihoming in IPv6 Report on IETF Activity
IEEE 802 Scope of OmniRAN Abstract
Software interoperability in the NGN Service layer
Ingate & Dialogic Technical Presentation
Discussion Issues on IMS-based NGN
Presentation transcript:

Session Peering Use Cases for Federations David Schwartz – Kayote Networks Eli Katz - XConnect Jeremy Barkan - Digitalshtick draft-schwartz-speermint-use-cases-federations-00.txt IETF 67 – San Diego, November 2006

Different types of peering architectures found in real world Much discussion about kinds of peering Need for a catalog of real use cases Need a model [ pattern ] to talk about these use cases Use cases express different kinds of business relationships and drives in the VoIP peering space Use Cases and Patterns for VoIP Peering

IETF 67 – SPEERMINT WG

L (Location) – Location of termination Voice Service Provider I (Interoperability) – Signaling/media compatibility with T-VSP S (Security) – Security of transport, authenticity of VSPs T (Trust) – Privacy, Identity, Auth management, SPIT R (Routing) – Priority based traffic management C (Cost) – Cost of call six functions or services associated with call setup across peering networks:

IETF 67 – SPEERMINT WG Content – Declaration of policy requirements Negotiation – Method for peers to reach a policy instance that meets the policy requirements of both peers Enforcement – application of policy requirements at run time, such as in the call set up Each peering function has a policy framework associated with it consisting of :

IETF 67 – SPEERMINT WG Location Function Policy Content Examples Query mechanism/format of data (NAPTR, SIP 3XX) Location of authoritative information (Remote, Local) Type of data returned (Domain, IP) Resolution of domain (static, DNS SRV) Whose location returned (T-VSP, Intermediary) O-VSP has access to (All data, Selected peers) Data retrieval (Unlimited, Rate limited)

IETF 67 – SPEERMINT WG Security Function Policy Content Examples Type (IPSec, TLS) Symmetric (IPSec IKE, mutual TLS) Asymmetric (TLS + Digest)

IETF 67 – SPEERMINT WG Logical network entity providing one or more of the six peering functions described above. May be co-located at one of the peered VSPs, or it may be a separate, independent entity. Peering Service Provider

IETF 67 – SPEERMINT WG Direct – Peering Service Provider

IETF 67 – SPEERMINT WG Complexity associated with Direct model

IETF 67 – SPEERMINT WG Dealing with complexity Limit functionalityFarm out to 3rd party

IETF 67 – SPEERMINT WG Indirect – Peering Service Provider

IETF 67 – SPEERMINT WG Putting it all together

IETF 67 – SPEERMINT WG factoring out location function Handling non location functions for some relationships Using 3 rd party for these non location functions in others Conclusions: Different relationships require different peering models Direct peering does not scale very well There is need for more than just location function One solution is to “farm out” all functionality to 3 rd party Another solution involves

Questions?