The Session Initiation Protocol (SIP) P-Private-Network-Indication Private-Header (P-Header)
draft-vanelburg-sipping-private-network-indication-03
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Keith Drage , Hans Erik van Elburg | ||
Last updated | 2009-07-21 (Latest revision 2009-02-19) | ||
Replaced by | draft-vanelburg-dispatch-private-network-ind | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-vanelburg-dispatch-private-network-ind | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes why a private network indication is needed. A private network indication allows other nodes in a network to treat private network traffic to a different set of rules then public network traffic. The indication also distinguishes one private network from another private network.
Authors
Keith Drage
Hans Erik van Elburg
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)