IP Interconnection Profile

Slides:



Advertisements
Similar presentations
SIP Interconnect Guidelines draft-hancock-sip-interconnect-guidelines-02 David Hancock, Daryl Malas.
Advertisements

© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Addressing the Network – IPv4 Network Fundamentals – Chapter 6.
1 Network Architecture and Design Advanced Issues in Internet Protocol (IP) IPv4 Network Address Translation (NAT) IPV6 IP Security (IPsec) Mobile IP IP.
Differentiated Services. Service Differentiation in the Internet Different applications have varying bandwidth, delay, and reliability requirements How.
COS 420 Day 20. Agenda Group Project Discussion Protocol Definition Due April 12 Paperwork Due April 29 Assignment 3 Due Assignment 4 is posted Last Assignment.
An Architecture for Differentiated Services
Introduction to SIP Speaker: Min-Hua Yang Advisor: Ho-Ting Wu Date:2005/3/29.
SIP Interconnect Guidelines draft-hancock-sip-interconnect-guidelines-03 David Hancock, Daryl Malas.
Session-ID Requirements for IETF84 draft-ietf-insipid-session-id-reqts-00 1 August 2012 Paul Jones, Gonzalo Salgueiro, James Polk, Laura Liess, Hadriel.
Integrated Services (RFC 1633) r Architecture for providing QoS guarantees to individual application sessions r Call setup: a session requiring QoS guarantees.
RIPE64 Enum Working Group DE-CIX NGN Services.
Implementing ISA Server Publishing. Introduction What Are Web Publishing Rules? ISA Server uses Web publishing rules to make Web sites on protected networks.
Basic Transition Mechanisms for IPv6 Hosts and Routers -RFC 4213 Kai-Po Yang
© 2006 Cisco Systems, Inc. All rights reserved. Optimizing Converged Cisco Networks (ONT) Module 4: Implement the DiffServ QoS Model.
1 Network Security Lecture 8 IP Sec Waleed Ejaz
IPV6-VOIP ANIL K NARAM A1263 CN426-SVU. Introduction IPV4 IPV6 VOIP IPV4 to IPV6 Migration of VOIP to IPV6.
Draft-khan-ip-serv-peer-arch-03.txt SPEERMINT Peering Architecture IETF-66, Montreal, Canada Sohel Khan, Ph.D. Technology Strategist.
Draft-rosen-ecrit-emergency- framework-00 Brian Rosen NeuStar CPa
Karlstad University IP security Ge Zhang
Border Gateway Protocol (BGP) W.lilakiatsakun. BGP Basics (1) BGP is the protocol which is used to make core routing decisions on the Internet It involves.
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.
IP Security.  In CERTs 2001 annual report it listed 52,000 security incidents  the most serious involving:  IP spoofing intruders creating packets.
1 SPEERMINT Use Cases for Cable IETF 66 Montreal 11 JULY 2006 Presented by Yiu L. Lee.
All Rights Reserved © Alcatel-Lucent 2006, ##### 2G IMS CAVE Based Security Replay Protection Alec Brusilovsky, Zhibi Wang Alcatel-Lucent, July 24, 2007.
Session Initiation Protocol (SIP) Chapter 5 speaker : Wenping Zhang data :
SIP Interconnect Guidelines draft-hancock-sip-interconnect-guidelines-01 David Hancock, Daryl Malas.
CSC 600 Internetworking with TCP/IP Unit 5: IP, IP Routing, and ICMP (ch. 7, ch. 8, ch. 9, ch. 10) Dr. Cheer-Sun Yang Spring 2001.
An end-to-end usage of the IPv6 flow label
Chapter 8 IP Security MSc. NGUYEN CAO DAT Dr. TRAN VAN HOAI.
IP security Ge Zhang Packet-switched network is not Secure! The protocols were designed in the late 70s to early 80s –Very small network.
July 2014Rüdiger Geib draft-geib-tsvwg-diffserv-intercon IETF 90, Toronto Presented by: David Black Private discussions David Black, Fred Baker and Ruediger.
CSE5803 Advanced Internet Protocols and Applications (14) Introduction Developed in recent years, for low cost phone calls (long distance in particular).
SIP-H.323 Interworking Group RRR-1 IETF-48 SIP-H.323 Interworking Requirements draft-agrawal-sip-h323-interworking-reqs-00.txt Hemant.
1 VLANs Relates to Lab 6. Short module on basics of VLAN switching.
RFC3261 (Almost) Robert Sparks. SIPiT 10 2 Status of the New SIP RFC Passed IETF Last Call In the RFC Editor queue Author’s 48 hours review imminent IMPORTANT:
Cryptography and Network Security (CS435) Part Thirteen (IP Security)
Lect 8 Tahani al jehain. Types of attack Remote code execution: occurs when an attacker exploits a software and runs a program that the user does not.
D Janet Gunn, CSC Dennis Berg, CSC Pat McGregor, Nyquetek Richard Kaczmarek,
Bearer Control for VoIP and VoMPLS Control Plane Francois Le Faucheur Bruce Thompson Cisco Systems, Inc. Angela Chiu AT&T March 30, 2000.
Securing Access to Data Using IPsec Josh Jones Cosc352.
IP Security (IPSec) Matt Hermanson. What is IPSec? It is an extension to the Internet Protocol (IP) suite that creates an encrypted and secure conversation.
Lecture 10 Page 1 CS 236 Online Encryption and Network Security Cryptography is widely used to protect networks Relies on encryption algorithms and protocols.
Jim McEachern Senior Technology Consultant ATIS July 8, 2015.
VPNs & IPsec Dr. X Slides adopted by Prof. William Enck, NCSU.
UNIT 7- IP Security 1.IP SEC 2.IP Security Architecture
IPSecurity.
Internet Protocol Version 6 Specifications
Link Layer 5.1 Introduction and services
sip-identity-04 Added new response codes for various conditions
Encryption and Network Security
IP-NNI Joint Task Force Status Update
Chapter 18 IP Security  IP Security (IPSec)
ECRIT Interim: SIP Location Conveyance
Global Standards Collaboration (GSC) GSC-15
Session Initiation Protocol (SIP)
CSE565: Computer Security Lecture 23 IP Security
IP-NNI Joint Task Force Status Update
Verstat Related Best Practices
Reference Architecture and Call Flow Example for SIP RPH Signing
Routing and Switching Essentials v6.0
Security Protocols in the Internet
Virtual Private Networks (VPNs)
Chapter 15. Internet Protocol
Architecture and Protocols
CIS679: Two Planes and Int-Serv Model
OSI Reference Model Unit II
OSI Model 7 Layers 7. Application Layer 6. Presentation Layer
Congestion Control Comments Resolution
Chapter 8 – Data switching and routing
Presentation transcript:

IP Interconnection Profile Consensus Points 6/17/2014

Protocol Technical Items Carrier's MUST support the History-Info Header and SHOULD support of the SIP Diversion header for a period of time in order facilitate interoperability. When both headers are sent, the sender MUST ensure that they are semantically identical. Carrier's May support redirection across the NNI, based on bilateral agreement. The redirection MAY be performed with a 3XX or REFER message. Carrier's MUST support P-Early-Media as defined in RFC 5009. Resource Priority Header (RPH) MUST be supported by NS/EP compliant networks, and MUST be transparently passed by non- NS/EP compliant networks. VOICE-ADMIT Forwarding Per-Hop Behaviour per RFC 5865

Protocol Technical Items Specified the exact presentations of Fully Qualified Domain Names in “From:”, “To:” and “PAI” fields. The originating Carrier network MUST provide the calling number of the originating user in the P-Asserted-Identity header field of dialog-initiating requests. If the originating user wants to remain anonymous, the originating Carrier network MUST include a Privacy header field containing the value "id" as specified in [RFC 3323] and [RFC 3325].

Protocol Technical Items Carrier's MUST support SIP Overload Control with mandatory support of the default algorithm, for SIP congestion control. Carrier's MAY optional support the Rate Based algorithm based on bilateral agreement between two carriers. Government Priority Services are exempt from overload controls An Carrier network MAY impose limits on the number of simultaneous calls, and the incoming rate at which it will accept calls, from a peer. On receiving a dialog-initiating request that exceeds such limits, the receiving Carrier network MUST respond with a 503 (Service Unavailable) response. An Carrier network MAY periodically send an OPTIONS request containing a Max-Forwards header field set to a value of '0' to detect the availability of a peer’s ingress point.

Protocol Technical Items Distinguishing traffic classes In order to distinguish between traffic classes, the use of the DSCP marking scheme in Behavior Aggregation mode Same DSCP for Voice and Media VOICE-ADMIT Forwarding Per-Hop Behavior per RFC 5865 for NS/EP traffic It is the responsibility of the IPv6 Carrier network to perform the IPv4/IPv6 interworking function when interworking with an IPv4 Carrier network. Peer Carrier networks SHOULD support the RTP Loopback Test procedures Carrier networks that support the RTP Loopback procedures will provide a SIP URI that identifies a media endpoint within the Carrier network that performs the loopback functions. Ideally, this "loopback" media endpoint would be located near the ingress point of the peer Carrier network.

Mandatory and optional narrowband and wideband codecs, including codec/packetization period use and transcoding guidelines

Security The VoIP traffic, from the border element in one carrier’s domain to the border element in another carrier’s domain, shall be secured, either physically or logically, from Internet Transit traffic. This security can be achieved: physically: by implementing separated and dedicated networks for the traffic. logically: by implementing mechanism such as Virtual Private Networks (either layer 2, e.g., VLANs, or layer 3, e.g., MPLS-VPN) and Tunneling (e.g. IP Sec).