Private Network Indication

1
Private Network Indication

• draft-vanelburg-sipping-private-network-indication
  -01
• Hans Erik van Elburg
• Keith Drage

2
Why differentiate private network traffic?

• NGN/IMS defined for public network infrastructure
• Need to handle business communications
• Different handling applies to enterprise traffic
  that never leaves enterprise context allthough it
  is routed through public network infrastructure
  and handled by public network operator hosted
  functionality.
• Examples of potential different processing
  behaviours
• Routing
• Charging
• Required by regulation
• Transparency

3
Why is an explicit indication needed

• Whether a call is to be treated as private
  network traffic or public network traffic can not
  always be inferred from signalling.
• A call where both the originating and the
  terminating party are identified as enterprise
  users from the same enterprise, may still need to
  be handled as public network traffic.
• Calls pass several proxies that may need to act
  on whether a call is private network traffic or
  not. Provisioning all these different proxies
  with the same knowledge is not desirable.

4
Several solutions discussed and dismissed

• Resource-Priority header?
• P-Asserted-Service header?
• Request-Disposition header?
• P-Access-Network-Information header?

5
Proposed solution

• New header
• Private-Network-Indicator
• "Private-Network-Indicator" HCOLON
  PNI-value
• (SEMI
  PNI-param)
• PNI-param generic-param
• PNI-value hostname

6
Decision requested from SIPPING WG

• There is two directions that we can take with
  this solution
• Full SIP header field
• P- header field
• What does the meeting think is the most
  appropriate way forward?