datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespaces
RFC 5478

Network Working Group                                            J. Polk
Request for Comments: 5478                                 Cisco Systems
Category: Standards Track                                     March 2009

       IANA Registration of New Session Initiation Protocol (SIP)
                      Resource-Priority Namespaces

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents in effect on the date of
   publication of this document (http://trustee.ietf.org/license-info).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Abstract

   This document creates additional Session Initiation Protocol (SIP)
   Resource-Priority namespaces to meet the requirements of the US
   Defense Information Systems Agency, and places these namespaces in
   the IANA registry.

Polk                        Standards Track                     [Page 1]
RFC 5478            New SIP RPH Namespaces for DISA           March 2009

Table of Contents

   1. Introduction ....................................................2
      1.1. Conventions Used in This Document ..........................3
   2. New SIP Resource-Priority Namespaces Created ....................3
   3. IANA Considerations .............................................4
      3.1. IANA Resource-Priority Namespace Registration ..............4
      3.2. IANA Priority-Value Registrations ..........................6
   4. Security Considerations .........................................6
   5. Acknowledgments .................................................6
   6. Normative References ............................................6

1.  Introduction

   The US Defense Information Systems Agency (DISA) is rolling out their
   Session Initiation Protocol (SIP) based architecture at this time.
   This network will require more Resource-Priority namespaces than were
   defined, and IANA registered, in RFC 4412 [RFC4412].  The purpose of
   this document is to define these additional namespaces.  Each will be
   preemptive in nature, as defined in RFC 4412, and will have the same
   10 priority-values.

   DISA has a requirement to be able to assign different Resource-
   Priority namespaces to differing groups of differing sizes throughout
   their networks.  Examples of this may be

   - namespaces as large as each branch of service (Army, Navy, Air
     Force, Marines, Coast Guard)

   - namespaces for some departments within the government (for example,
     Homeland Security)

   - namespaces that are temporary assignments to individual units of
     varying sizes (from battle groups to patrol groups or platoons)

   These temporary assignments might be combinations of smaller units
   involving several branches of service operating as one unit (say, one
   task force, which is separate than the branch of service), or a
   single commando unit requiring special treatment for a short period
   of time, making it appear separate from the branch of service they
   are from.

   Providing DISA with a pool of namespaces for fine-grained
   assignment(s) allows them the flexibility they need for their mission
   requirements.  One can imagine due to their sheer size and separation
   of purpose, they can easily utilize a significant number of
   namespaces within their networks.  This is the reason for the

Polk                        Standards Track                     [Page 2]
RFC 5478            New SIP RPH Namespaces for DISA           March 2009

[include full document text]