IETF 67

1
IETF 67 San Diego

• SIP Peering Use Case for VSPs
• Adam Uzelac
• adam.uzelac_at_globalcrossing.com
• Skype voiploser
• draft-uzelac-speermint-use-cases-00.txt

2
Use Cases

• Typical internet protocol interconnection
  scenarios for SIP signaled VOIP
• Peering in varied inter-domain and trust contexts
• Pre-established contract between administrative
  domains
• Signaling and media designed to enable and
  enforce call admission, policy, quality and
  security for traversing the network boundary.

3
The context for these Use Cases

• Signaling and media collapsed symmetrical
  across the administrative boundary.
• Transcoding, if required, is accomplished at the
  first point of recognized media incompatibility.
• There is assumed IP reachability
• There is no specific requirement or presumption
  of private (RFC1918) or public address space use.

4
Proxy(o) to SBC(o) to Proxy(t)
Legend ltanythinggt(o) originating ltanythinggt(t)
terminating ltanythinggt(T) transit
Signaling
Next-hop lookups
VSP (o)
VSP (t)
5
Proxy(o) to SBC(o) to SBC(t) to Proxy(t)
Legend ltanythinggt(o) originating ltanythinggt(t)
terminating ltanythinggt(T) transit
Signaling
Next-hop lookups
VSP (o)
VSP (t)
6
Proxy(o) to SBC(T) to SBC(T) to Proxy(t)
Legend ltanythinggt(o) originating ltanythinggt(t)
terminating ltanythinggt(T) transit
Signaling
Next-hop lookups
VSP (o)
VSP (t)
VSP (T)
7
Proxy(o) to SBC(o) to SBC(T) to SBC(T) to SBC(t)
Proxy(t)
Legend ltanythinggt(o) originating ltanythinggt(t)
terminating ltanythinggt(T) transit
Signaling
Next-hop lookups
VSP (o)
VSP (t)
VSP (T)
8
Something to noodle on

• BASIC REQUIREMENT (from Stastny_voipeer_BOF_IETF_
  63.ppt)
• Any connection that originates on IP and
  terminates on IP should stay on IP end-to-end
• No additional cost for PSTN by-pass
• Improved QoS for native IP connections
• improved functionality (BB codecs, IM, video,
  conferencing, presence, )
• Each use case was end to end IP, but was basic
  requirement met?!?!

9
Finally

• Proposal - There are 4 IDs of Use Case We
  should consolidate into a single ID.
• Need to investigate and document why these use
  cases exist in the way they do today, add to WG
  requirements (if applicable) once hashed out on
  mailing list.

10
!? Questions/Comments/Concerns ?!