Internet Engineering Task Force (IETF)                           J. Polk
Request for Comments: 7135                                 Cisco Systems
Category: Informational                                         May 2014
ISSN: 2070-1721
        
Internet Engineering Task Force (IETF)                           J. Polk
Request for Comments: 7135                                 Cisco Systems
Category: Informational                                         May 2014
ISSN: 2070-1721
        

Registering a SIP Resource Priority Header Field Namespace for Local Emergency Communications

为本地紧急通信注册SIP资源优先级标头字段命名空间

Abstract

摘要

This document creates the new Session Initiation Protocol (SIP) Resource Priority header field namespace 'esnet' and registers this namespace with IANA. The new header field namespace allows for local emergency session establishment to a public safety answering point (PSAP), between PSAPs, and between a PSAP and first responders and their organizations.

本文档创建新的会话启动协议(SIP)资源优先级头字段名称空间“esnet”,并向IANA注册此名称空间。新的标题字段名称空间允许在公共安全应答点(PSAP)、PSAP之间以及PSAP和第一响应者及其组织之间建立本地紧急会话。

Status of This Memo

关于下段备忘

This document is not an Internet Standards Track specification; it is published for informational purposes.

本文件不是互联网标准跟踪规范;它是为了提供信息而发布的。

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.

本文件是互联网工程任务组(IETF)的产品。它代表了IETF社区的共识。它已经接受了公众审查,并已被互联网工程指导小组(IESG)批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准;见RFC 5741第2节。

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7135.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息,请访问http://www.rfc-editor.org/info/rfc7135.

Copyright Notice

版权公告

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

版权所有(c)2014 IETF信托基金和确定为文件作者的人员。版权所有。

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本,并提供简化BSD许可证中所述的无担保。

Table of Contents

目录

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Rules of Usage of the Resource Priority Header Field . . . . .  4
   3.  "esnet" Namespace Definition . . . . . . . . . . . . . . . . .  6
     3.1.  Namespace Definition Rules and Guidelines  . . . . . . . .  6
     3.2.  The 'esnet' Namespace  . . . . . . . . . . . . . . . . . .  6
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
     4.1.  IANA Resource-Priority Namespace Registration  . . . . . .  7
     4.2.  IANA Priority-Value Registrations  . . . . . . . . . . . .  7
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  8
   7.  Normative References . . . . . . . . . . . . . . . . . . . . .  9
        
   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Rules of Usage of the Resource Priority Header Field . . . . .  4
   3.  "esnet" Namespace Definition . . . . . . . . . . . . . . . . .  6
     3.1.  Namespace Definition Rules and Guidelines  . . . . . . . .  6
     3.2.  The 'esnet' Namespace  . . . . . . . . . . . . . . . . . .  6
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
     4.1.  IANA Resource-Priority Namespace Registration  . . . . . .  7
     4.2.  IANA Priority-Value Registrations  . . . . . . . . . . . .  7
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  8
   7.  Normative References . . . . . . . . . . . . . . . . . . . . .  9
        
1. Introduction
1. 介绍

This document creates the new Session Initiation Protocol (SIP) Resource Priority header (RPH) field namespace 'esnet' for local emergency usage and registers this namespace with IANA. The SIP Resource-Priority header field is defined in RFC 4412 [RFC4412]. The new 'esnet' namespace is to be used for inbound calls towards a public safety answering point (PSAP), between PSAPs, and between a PSAP and first responders or their organizations within managed IP networks. This namespace is not for use on the open public Internet because it can be trivially forged.

本文档创建新的会话启动协议(SIP)资源优先级头(RPH)字段命名空间“esnet”以供本地紧急使用,并向IANA注册此命名空间。SIP资源优先级头字段在RFC 4412[RFC4412]中定义。新的“esnet”命名空间将用于向公共安全应答点(PSAP)、PSAP之间以及PSAP与托管IP网络中的第一响应者或其组织之间的入站呼叫。此名称空间不可在开放的公共Internet上使用,因为它可以被轻易伪造。

Adding an RPH with the 'esnet' namespace can be differentiated from the marking of an emergency call using a service URN as defined in [RFC5031] in that the RPH specifically requests preferential treatment in networks that honor it, while the marking merely identifies an emergency call without necessarily affecting resources allocated to it. It is appropriate to use both where applicable. RPH with 'esnet' may also be used within public safety networks for SIP sessions that are not emergency calls and thus not marked per RFC 5031.

添加带有“esnet”名称空间的RPH与使用[RFC5031]中定义的服务URN标记紧急呼叫的区别在于,RPH特别要求在尊重它的网络中给予优惠待遇,而标记仅识别紧急呼叫,而不一定影响分配给它的资源。在适用的情况下,两者都可以使用。带有“esnet”的RPH也可在公共安全网络中用于非紧急呼叫的SIP会话,因此未按照RFC 5031进行标记。

This new namespace is included in SIP requests to provide an explicit priority indication within controlled environments, such as an IP Multimedia Subsystem (IMS) infrastructure or Emergency Services network (ESInet) where misuse can be reduced to an acceptable level because these types of networks have controls in place. The function facilitates differing treatment of emergency SIP requests according to local policy, or more likely, a contractual agreement between the network organizations. This indication is used solely to differentiate certain SIP requests, transactions, or dialogs from other SIP requests, transactions, or dialogs that do not have the need for priority treatment. If there are differing, yet still understandable and valid Resource-Priority header values in separate

此新名称空间包含在SIP请求中,以在受控环境(如IP多媒体子系统(IMS)基础设施或紧急服务网络(ESInet))中提供明确的优先级指示,在这些环境中,误用可以减少到可接受的水平,因为这些类型的网络具有适当的控制。该功能有助于根据本地策略,或者更可能是网络组织之间的合同协议,对紧急SIP请求进行不同的处理。此指示仅用于区分某些SIP请求、事务或对话框与不需要优先处理的其他SIP请求、事务或对话框。如果存在不同但仍然可以理解且有效的资源优先级标头值,请在单独的

SIP requests, then this indication can be used by local policy to determine which SIP request, transaction, or dialog receives which treatment (likely better or worse than another).

SIP请求,则本地策略可以使用此指示来确定哪个SIP请求、事务或对话接收到哪个处理(可能比另一个更好或更差)。

Application Service Providers (ASPs) that are securely connected to an ESInet may have sufficient controls policing the header, and a trust relationship with the entities inside the ESInet. SIP requests from such ASPs could make use of this 'esnet' namespace for appropriate treatment when requests are passed from the ASP to the ESInet.

安全连接到ESInet的应用程序服务提供商(ASP)可能有足够的控制来管理标头,并与ESInet内的实体建立信任关系。当请求从ASP传递到ESInet时,来自此类ASP的SIP请求可以使用此“esnet”命名空间进行适当处理。

The 'esnet' namespace may also be used on calls from a PSAP or other public safety agency on an ESInet towards a private or public network, ASP or User Agent ("call back") when priority is needed. Again, the request for priority is not for use on the public Internet due to the ease of forging the header.

当需要优先级时,“esnet”命名空间也可用于PSAP或esnet上的其他公共安全机构向专用或公用网络、ASP或用户代理(“回拨”)发出的呼叫。同样,由于易于伪造报头,优先级请求不可在公共互联网上使用。

This document merely creates the namespace, per the rules within [RFC4412] as updated by [RFC7134], which necessitates that new RPH namespaces and their relative priority-value order be IETF reviewed before being registered with IANA.

本文档仅根据[RFC7134]更新的[RFC4412]中的规则创建名称空间,这要求在向IANA注册之前,新的RPH名称空间及其相对优先级值顺序必须经过IETF审查。

There is the possibility that within emergency services networks, Multilevel Precedence and Preemption (MLPP)-like behavior can be achieved (likely without the 'preemption' part), provided the local policy supports enabling this function. For example, calls placed between law enforcement agents could be marked similarly to MLPP systems used by military networks, and some of those calls could be handled with higher priority than an emergency call from an ordinary user. Therefore, the 'esnet' namespace is given five priority-levels instead of just one. This document does not define MLPP-like SIP signaling for emergency calls like those using emergency service numbers (such as 911, 112, and 999), but it is not prevented either.

在应急服务网络中,如果本地策略支持启用此功能,则有可能实现类似多级优先和抢占(MLPP)的行为(可能没有“抢占”部分)。例如,执法人员之间的呼叫可以类似于军事网络使用的MLPP系统进行标记,其中一些呼叫可以比普通用户的紧急呼叫具有更高的优先级。因此,“esnet”命名空间被赋予五个优先级,而不是一个。本文档没有为使用紧急服务号码(如911、112和999)的紧急呼叫定义类似MLPP的SIP信令,但也没有阻止。

Within the ESInet, there will be emergency calls requiring different treatments, according to the type of call. Does a citizen's call to a PSAP require the same, a higher, or a lower relative priority than a PSAP's call to a police department or the police chief? What about either relative to a call from within the ESInet to a national government's department responsible for public safety, disaster relief, national security/defense, etc.? For these additional reasons, the 'esnet' namespace has multiple priority levels.

在ESInet内,根据呼叫类型,将有需要不同处理的紧急呼叫。公民对PSAP的呼叫是否需要与PSAP对警察局或警察局长的呼叫相同、更高或更低的相对优先级?与ESInet内部向负责公共安全、救灾、国家安全/国防等的国家政府部门发出的电话相关的情况如何。?出于这些其他原因,“esnet”命名空间具有多个优先级。

This document does not define any of these behaviors, outside of reminding readers that the rules of RFC 4412 apply - though examples of usage are included for completeness. This document registers the 'esnet' RPH namespace with IANA for use within any emergency services networks, not just of those from citizens to PSAPs.

除了提醒读者RFC4412的规则适用之外,本文档没有定义任何这些行为——尽管为了完整起见,还包括了使用示例。本文件向IANA注册了“esnet”RPH名称空间,以便在任何应急服务网络中使用,而不仅仅是在从公民到PSAP的网络中使用。

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。

2. Rules of Usage of the Resource Priority Header field
2. 资源优先级标头字段的使用规则

This document retains the behaviors of the SIP Resource Priority header field, defined in [RFC4412], when choosing between the treatment options surrounding this new 'esnet' namespace. Given the environment this is to be used within (i.e., within an ESInet), the usage of the 'esnet' namespace does not have a 'normal' or routine call level; that is left for local jurisdictions to define within their respective parts of the ESInet, which could be islands of local administration.

本文档保留了[RFC4412]中定义的SIP资源优先级标头字段在围绕新“esnet”命名空间选择处理选项时的行为。考虑到将在(即,在ESInet内)中使用的环境,“esnet”命名空间的使用没有“正常”或例程调用级别;这将留给地方司法管辖区在其各自的ESInet部分内进行定义,ESInet可能是地方行政管理的孤岛。

The 'esnet' namespace MUST only be used where at least one end of the signaling, setting aside the placement of B2BUAs (Back-to-Back User Agents), is within a local emergency organization. In other words, if either the originating human caller's User Agent (UA) or the destination human callee's UA is part of the local emergency organization, this is a valid use of 'esnet'.

“esnet”名称空间只能在本地应急组织内至少有一个信令端(不考虑B2BUA(背靠背用户代理)的位置)的情况下使用。换句话说,如果发起人工呼叫者的用户代理(UA)或目标人工呼叫者的UA是本地应急组织的一部分,则这是“esnet”的有效使用。

The 'esnet' namespace has 5 priority-values, in a specified relative priority order, and is registered as a queue-based namespace in compliance with [RFC4412]. SIP entities that support preemption treatment (see Section 5 of [RFC4412]) can be configured according to local policy. Display names for the 'esnet' values displayed can likewise be set according to local policy.

“esnet”命名空间有5个优先级值,按照指定的相对优先级顺序,并按照[RFC4412]注册为基于队列的命名空间。支持抢占处理的SIP实体(参见[RFC4412]第5节)可以根据本地策略进行配置。同样,可以根据本地策略设置显示的“esnet”值的显示名称。

The following network diagram provides one example of local policy choices when using the 'esnet' namespace:

以下网络图提供了使用“esnet”命名空间时本地策略选择的一个示例:

                                                 |<-'esnet' namespace->|
                                                 |        is used      |
   'esnet' namespace                             |        ,-------.
   usage out of scope                            |      ,'         `.
      |<------------>|<---'esnet' namespace ---->|     /             \
   +----+            |       can be used      +-----+ |    ESInet     |
   | UA |---         |    --------------------|Proxy|-+    ------     |
   +----+   \        |   /                    +-----+ |               |
             \  ,-------+           ,-------.    |    |   +------+    |
   +----+     ,'         `.       ,'         `.  |    |   |PSAP-1|    |
   | UA |--- /  User       \     / Application \ |    |   +------+    |
   +----+   (    Network    +---+    Service    )|    |               |
             \             /     \   Provider  / |    |   +------+    |
   +----+    /`.         ,'       `.         .+-----+ |   |PSAP-2|    |
   | UA |----   '-------'           '-------' |Proxy|-+   +------+    |
   +----+            |                        +-----+ |               |
                     |                           |    |               |
   +----+            |                        +-----+ |   +------+    |
   | UA |---         |    --------------------|Proxy|-+   |PSAP-3|    |
   +----+   \        |   /                    +-----+ |   +------+    |
             \  ,-------+           ,-------.    |    |               |
   +----+     ,'         `.       ,'         `.  |    |               |
   | UA |--- /  User       \     / Application \ |    |   +------+    |
   +----+   (    Network    +---+    Service    )|    |   |PSAP-4|    |
             \             /     \   Provider  / |    |   +------+    |
   +----+    /`.         ,'       `.         .+-----+ |               |
   | UA |----   '-------'           '-------' |Proxy|-+    ANY can    |
   +----+            |                        +-----+ |   xfer/call   |
                     |                           |     \    | | |    /
                                                        `.  | | |  ,'
                                                          '-|-|-|-'
                                                            | | |
                                     Police  <--------------+ | |
                                              Fire <----------+ |
                                        National Agency <-------+
        
                                                 |<-'esnet' namespace->|
                                                 |        is used      |
   'esnet' namespace                             |        ,-------.
   usage out of scope                            |      ,'         `.
      |<------------>|<---'esnet' namespace ---->|     /             \
   +----+            |       can be used      +-----+ |    ESInet     |
   | UA |---         |    --------------------|Proxy|-+    ------     |
   +----+   \        |   /                    +-----+ |               |
             \  ,-------+           ,-------.    |    |   +------+    |
   +----+     ,'         `.       ,'         `.  |    |   |PSAP-1|    |
   | UA |--- /  User       \     / Application \ |    |   +------+    |
   +----+   (    Network    +---+    Service    )|    |               |
             \             /     \   Provider  / |    |   +------+    |
   +----+    /`.         ,'       `.         .+-----+ |   |PSAP-2|    |
   | UA |----   '-------'           '-------' |Proxy|-+   +------+    |
   +----+            |                        +-----+ |               |
                     |                           |    |               |
   +----+            |                        +-----+ |   +------+    |
   | UA |---         |    --------------------|Proxy|-+   |PSAP-3|    |
   +----+   \        |   /                    +-----+ |   +------+    |
             \  ,-------+           ,-------.    |    |               |
   +----+     ,'         `.       ,'         `.  |    |               |
   | UA |--- /  User       \     / Application \ |    |   +------+    |
   +----+   (    Network    +---+    Service    )|    |   |PSAP-4|    |
             \             /     \   Provider  / |    |   +------+    |
   +----+    /`.         ,'       `.         .+-----+ |               |
   | UA |----   '-------'           '-------' |Proxy|-+    ANY can    |
   +----+            |                        +-----+ |   xfer/call   |
                     |                           |     \    | | |    /
                                                        `.  | | |  ,'
                                                          '-|-|-|-'
                                                            | | |
                                     Police  <--------------+ | |
                                              Fire <----------+ |
                                        National Agency <-------+
        

A Possible Network Architecture Using the 'esnet' Namespace

使用“esnet”命名空间的可能网络体系结构

In the figure, the 'esnet' namespace is used within the ESInet on the right side of the diagram. How it is specifically utilized is out of scope for this document and is left to local jurisdictions to define. Whether preemption is implemented in the ESInet and the values displayed to the ESInet users is likewise out of scope. Adjacent ASPs to the ESInet may have a trust relationship that includes allowing this/these neighboring ASP(s) to use the 'esnet' namespace

在图中,“esnet”命名空间在图右侧的ESInet中使用。如何具体使用它超出了本文件的范围,由当地司法管辖区定义。是否在ESInet中实施抢占以及向ESInet用户显示的值同样超出范围。ESInet的相邻ASP可能具有信任关系,包括允许此/这些相邻ASP使用“esnet”命名空间

to differentiate SIP requests and dialogs within the ASP's network. The exact mapping between the internal and external sides of the edge proxy at the ESInet boundaries is out of the scope of this document.

区分ASP网络中的SIP请求和对话框。ESInet边界处边缘代理的内部和外部之间的精确映射不在本文档的范围内。

3. "esnet" Namespace Definition
3. “esnet”命名空间定义

The 'esnet' namespace is not generic for all emergencies because there are a lot of different kinds of emergencies, some on a military scale ([RFC4412] defines 3 of these), some on a national scale ([RFC4412] defines 2 of these), and some on an international scale. Each type of emergency can also have its own namespace(s); although there are many defined for other uses, more are possible -- so using the public emergency service number (such as 911, 112, or 999) to call for police officers, firefighters, or emergency medical technicians (etc.) does not have a monopoly on the word "emergency".

“esnet”名称空间不是所有紧急情况的通用名称空间,因为存在许多不同类型的紧急情况,一些是军事规模的紧急情况([RFC4412]定义了其中的3种),一些是国家规模的紧急情况([RFC4412]定义了其中的2种),还有一些是国际规模的紧急情况。每种类型的紧急情况也可以有自己的名称空间;尽管有许多定义用于其他用途,但还有更多可能——因此,使用公共紧急服务号码(如911、112或999)呼叫警察、消防员或紧急医疗技术人员(等)并不是“紧急”一词的专利。

The namespace 'esnet' has been chosen, roughly to stand for "Emergency Services NETwork", for a citizen's call for help from a public authority type of organization. This namespace will also be used for communications between emergency authorities, and it MAY be used by emergency authorities to call public citizens. An example of the latter is a PSAP operator calling back someone who previously called an emergency service number (such as 911, 112, or 999) and the communication was terminated before it -- in the PSAP operator's judgment -- should have been.

名称空间“esnet”被选定,大致代表“应急服务网络”,代表公民向公共权威机构类型的组织求助。该名称空间还将用于应急机构之间的通信,应急机构可使用该名称空间呼叫公共公民。后者的一个例子是,PSAP运营商回拨之前拨打过紧急服务号码(如911、112或999)的人,并且根据PSAP运营商的判断,在该号码应该被终止之前,通信被终止。

Below is an example of a Resource-Priority header field using the 'esnet' namespace:

下面是使用“esnet”命名空间的资源优先级标头字段的示例:

Resource-Priority: esnet.0

资源优先级:esnet.0

3.1. Namespace Definition Rules and Guidelines
3.1. 命名空间定义规则和指南

This specification defines one unique namespace for emergency calling scenarios, 'esnet' and registers this namespace with IANA. This IANA registration contains the facets defined in Section 9 of [RFC4412].

该规范为紧急呼叫场景定义了一个唯一的名称空间“esnet”,并向IANA注册该名称空间。本IANA注册包含[RFC4412]第9节中定义的方面。

3.2. The 'esnet' Namespace
3.2. “esnet”命名空间

Per the rules of [RFC4412], each namespace has a finite set of relative priority-value(s), listed (below) from lowest priority to highest priority. In an attempt to not limit this namespace's use in the future, more than one priority-value is assigned to the 'esnet' namespace. This document does not recommend which Priority-value is used where in which situation or scenario. That is for another document to specify. To be effective, the choice within a national

根据[RFC4412]的规则,每个名称空间都有一组有限的相对优先级值,从最低优先级到最高优先级(如下所示)。为了不限制此命名空间在将来的使用,将为“esnet”命名空间分配多个优先级值。本文档不建议在哪种情况或场景下使用哪种优先级值。这是另一个要指定的文档。为了有效,国家内部的选择

jurisdiction needs to be coordinated by all sub-jurisdictions to maintain uniform SIP behavior throughout an emergency calling system of that nation.

辖区需要由所有子辖区协调,以在该国的整个紧急呼叫系统中保持统一的SIP行为。

The relative priority order for the 'esnet' namespace is as follows:

“esnet”命名空间的相对优先级顺序如下所示:

(lowest) esnet.0 esnet.1 esnet.2 esnet.3 (highest) esnet.4

(最低)esnet.0 esnet.1 esnet.2 esnet.3(最高)esnet.4

The 'esnet' namespace will have priority queuing registrations for these levels per Section 4.5.2 of [RFC4412]. Although no preemption is specified in this document for any levels of 'esnet', local jurisdiction(s) MAY configure their SIP infrastructure to use this namespace with preemption, as defined in RFC 4412.

根据[RFC4412]第4.5.2节,“esnet”命名空间将具有这些级别的优先级队列注册。尽管本文档中没有为任何级别的“esnet”指定抢占权,但本地管辖区可将其SIP基础设施配置为使用此名称空间进行抢占,如RFC 4412中所定义。

The remaining rules that originated in RFC 4412 apply with regard to an RP actor who understands more than one namespace, and must maintain its locally significant relative priority order.

起源于RFC4412的其余规则适用于理解多个名称空间的RP参与者,并且必须保持其本地重要的相对优先级顺序。

4. IANA Considerations
4. IANA考虑
4.1. IANA Resource-Priority Namespace Registration
4.1. IANA资源优先级命名空间注册

The following entry has been added to the "Resource-Priority Namespaces" registry of the sip-parameters section of IANA (created by [RFC4412]):

以下条目已添加到IANA(由[RFC4412]创建)sip参数部分的“资源优先级名称空间”注册表中:

                                       Intended       New     New resp.
      Namespace  Levels   Algorithm     Code      warn-code   Reference
      ---------  ------  -----------  ---------   ---------   ---------
        esnet      5       queue         no          no       RFC 7135
        
                                       Intended       New     New resp.
      Namespace  Levels   Algorithm     Code      warn-code   Reference
      ---------  ------  -----------  ---------   ---------   ---------
        esnet      5       queue         no          no       RFC 7135
        
4.2. IANA Priority-Value Registrations
4.2. IANA优先级值注册

The following entry has been added to the "Resource-Priority Priority-values" registry of the sip-parameters section of IANA:

以下条目已添加到IANA sip参数部分的“资源优先级值”注册表中:

Namespace: esnet Reference: (this document) Priority-Values (least to greatest): "0", "1","2", "3", "4"

命名空间:esnet引用:(此文档)优先级值(从最小到最大):“0”、“1”、“2”、“3”、“4”

5. Security Considerations
5. 安全考虑

The Security considerations that apply to RFC 4412 [RFC4412] apply here.

适用于RFC 4412[RFC4412]的安全注意事项适用于此处。

For networks that act on the SIP Resource-Priority header field, incorrect use of namespaces can result in traffic that should have been given preferential treatment not receiving it, and vice versa. This document does not define a use case where an endpoint outside the ESInet marks its call for preferential treatment. Precautions need to be taken to prevent granting preferential treatment to unauthorized users not calling for emergency help even if they are in the ESInet, as well as to prevent misuse by callers outside the ESInet.

对于作用于SIP Resource Priority header字段的网络,名称空间的不正确使用可能会导致本应得到优先处理的流量无法接收,反之亦然。本文档未定义ESInet之外的端点标记其优先处理要求的用例。需要采取预防措施,以防止对未经授权的用户给予优惠待遇,即使他们在ESInet内也不需要紧急帮助,并防止ESInet外的呼叫者滥用。

A simple means of preventing this usage is to not allow traffic marked 'esnet' to get preferential treatment unless the destination is towards the local/regional ESInet. This is not a consideration for internetwork traffic within the ESInet, or generated out of the ESInet. Calling an emergency service number (such as 911, 112, or 999) is fairly local in nature, with a finite number of URIs that are likely to be considered valid within a portion of a network receiving SIP signaling.

防止这种使用的一种简单方法是不允许标记为“esnet”的流量获得优惠待遇,除非目的地朝向本地/区域ESInet。这不是ESInet内或ESInet外产生的网络间流量的考虑因素。呼叫紧急服务号码(如911、112或999)本质上是相当本地的,在接收SIP信令的网络的一部分中,有限数量的URI可能被认为是有效的。

This namespace is not intended for use on the Internet because of the difficulty in detecting abuse; specifically, it can trivially be forged and used on a non-emergency session to obtain resource priority. Some networks may determine that it can reasonably prevent abuse and/or that the consequences of undetected abuse is not significant. In such cases, use of 'esnet' on the Internet MAY be allowed.

该名称空间不打算在互联网上使用,因为难以发现滥用情况;具体来说,它可以被伪造并用于非紧急会话以获得资源优先级。一些网络可能确定它可以合理地防止滥用和/或未被发现的滥用的后果并不严重。在这种情况下,可能允许在互联网上使用“esnet”。

6. Acknowledgements
6. 致谢

Thanks to Ken Carlberg, Janet Gunn, Fred Baker, and Keith Drage for help and encouragement with this effort. Thanks to Henning Schulzrinne, Ted Hardie, Hannes Tschofenig, and Marc Linsner for constructive comments. A big thanks to Robert Sparks for being patient with the author and Brian Rosen for completing the final edits.

感谢Ken Carlberg、Janet Gunn、Fred Baker和Keith Drage对这一努力的帮助和鼓励。感谢Henning Schulzrinne、Ted Hardie、Hannes Tschofenig和Marc Linsner提出的建设性意见。非常感谢罗伯特·斯帕克斯对作者的耐心和布莱恩·罗森完成最后的编辑。

7. Normative References
7. 规范性引用文件

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC2119]Bradner,S.,“RFC中用于表示需求水平的关键词”,BCP 14,RFC 2119,1997年3月。

[RFC4412] Schulzrinne, H. and J. Polk, "Communications Resource Priority for the Session Initiation Protocol (SIP)", RFC 4412, February 2006.

[RFC4412]Schulzrinne,H.和J.Polk,“会话启动协议(SIP)的通信资源优先级”,RFC 4412,2006年2月。

[RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services", RFC 5031, January 2008.

[RFC5031]Schulzrinne,H.,“应急和其他知名服务的统一资源名称(URN)”,RFC 5031,2008年1月。

[RFC7134] Rosen, B., "The Management Policy of the Resource Priority Header (RPH) Registry Changed to "IETF Review"", RFC 7134, March 2014.

[RFC7134]Rosen,B.,“资源优先级头(RPH)注册表的管理策略更改为“IETF审查”,RFC 7134,2014年3月。

Author's Address

作者地址

James Polk Cisco Systems 3913 Treemont Circle Colleyville, TX 76034 USA

James Polk Cisco Systems 3913美国德克萨斯州Treemont Circle Colleyville 76034

   Phone: +1-817-271-3552
   EMail: jmpolk@cisco.com
        
   Phone: +1-817-271-3552
   EMail: jmpolk@cisco.com