Network Working Group J. Kempf
Request for Comments: 3154 C. Castelluccia
Category: Informational P. Mutaf
N. Nakajima
Y. Ohba
R. Ramjee
Y. Saifullah
B. Sarikaya
X. Xu
August 2001
Network Working Group J. Kempf
Request for Comments: 3154 C. Castelluccia
Category: Informational P. Mutaf
N. Nakajima
Y. Ohba
R. Ramjee
Y. Saifullah
B. Sarikaya
X. Xu
August 2001
Requirements and Functional Architecture for an IP Host Alerting Protocol
IP主机警报协议的要求和功能体系结构
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
Abstract
摘要
This document develops an architecture and a set of requirements needed to support alerting of hosts that are in dormant mode. The architecture and requirements are designed to guide development of an IP protocol for alerting dormant IP mobile hosts, commonly called paging.
本文档开发了支持处于休眠模式的主机警报所需的体系结构和一组需求。该体系结构和要求旨在指导IP协议的开发，该协议用于向休眠IP移动主机（通常称为寻呼）发出警报。
Table of Contents
目录
1. Introduction ...................................................3
2. Terminology ....................................................3
3. Security Considerations ........................................3
3.1. DoS Amplification .........................................3
3.2. Queue Overflow ............................................4
3.3. Selective DoS against Hosts ...............................4
4. Requirements ...................................................5
4.1. Impact on Power Consumption ...............................5
4.2. Scalability ...............................................5
4.3. Control of Broadcast/Multicast/Anycast ....................5
4.4. Efficient Signaling for Inactive Mode .....................6
4.5. No Routers ................................................6
4.6. Multiple Dormant Modes ....................................6
4.7. Independence of Mobility Protocol .........................6
4.8. Support for Existing Mobility Protocols ...................6
4.9. Dormant Mode Termination ..................................6
4.10. Network Updates ...........................................6
4.11. Efficient Utilization of L2 ...............................7
4.12. Orthogonality of Paging Area and Subnets ..................7
4.13. Future L3 Paging Support ..................................7
4.14. Robustness Against Failure of Network Elements ............7
4.15. Reliability of Packet Delivery ............................7
4.16. Robustness Against Message Loss ...........................7
4.17. Flexibility of Administration .............................7
4.18. Flexibility of Paging Area Design .........................8
4.19. Availability of Security Support ..........................8
4.20. Authentication of Paging Location Registration ............8
4.21. Authentication of Paging Area Information .................8
4.22. Authentication of Paging Messages .........................8
4.23. Paging Volume .............................................8
4.24. Parsimonious Security Messaging ...........................8
4.25. Noninterference with Host's Security Policy ...............8
4.26. Noninterference with End-to-end Security ..................9
4.27. Detection of Bogus Correspondent Nodes ....................9
5. Functional Architecture ........................................9
5.1. Functional Entities .......................................9
5.2. Interfaces ...............................................10
5.3. Functional Architecture Diagram ..........................12
6. Acknowledgements ..............................................12
7. References ....................................................13
8. Authors' Addresses ............................................13
9. Full Copyright Statement ......................................16
1. Introduction ...................................................3
2. Terminology ....................................................3
3. Security Considerations ........................................3
3.1. DoS Amplification .........................................3
3.2. Queue Overflow ............................................4
3.3. Selective DoS against Hosts ...............................4
4. Requirements ...................................................5
4.1. Impact on Power Consumption ...............................5
4.2. Scalability ...............................................5
4.3. Control of Broadcast/Multicast/Anycast ....................5
4.4. Efficient Signaling for Inactive Mode .....................6
4.5. No Routers ................................................6
4.6. Multiple Dormant Modes ....................................6
4.7. Independence of Mobility Protocol .........................6
4.8. Support for Existing Mobility Protocols ...................6
4.9. Dormant Mode Termination ..................................6
4.10. Network Updates ...........................................6
4.11. Efficient Utilization of L2 ...............................7
4.12. Orthogonality of Paging Area and Subnets ..................7
4.13. Future L3 Paging Support ..................................7
4.14. Robustness Against Failure of Network Elements ............7
4.15. Reliability of Packet Delivery ............................7
4.16. Robustness Against Message Loss ...........................7
4.17. Flexibility of Administration .............................7
4.18. Flexibility of Paging Area Design .........................8
4.19. Availability of Security Support ..........................8
4.20. Authentication of Paging Location Registration ............8
4.21. Authentication of Paging Area Information .................8
4.22. Authentication of Paging Messages .........................8
4.23. Paging Volume .............................................8
4.24. Parsimonious Security Messaging ...........................8
4.25. Noninterference with Host's Security Policy ...............8
4.26. Noninterference with End-to-end Security ..................9
4.27. Detection of Bogus Correspondent Nodes ....................9
5. Functional Architecture ........................................9
5.1. Functional Entities .......................................9
5.2. Interfaces ...............................................10
5.3. Functional Architecture Diagram ..........................12
6. Acknowledgements ..............................................12
7. References ....................................................13
8. Authors' Addresses ............................................13
9. Full Copyright Statement ......................................16
In [1], a problem statement was developed to explain why an IP protocol was desirable for alerting hosts in dormant mode, commonly called paging. In this document, a set of requirements is developed for guiding the development of an IP paging protocol. Based on the requirements, an architecture is developed to represent the functional relationships between logical functional entities involved.
在[1]中，开发了一个问题陈述来解释为什么IP协议需要在休眠模式（通常称为分页）下向主机发出警报。在本文档中，为指导IP寻呼协议的开发，开发了一组需求。基于需求，开发了一个体系结构来表示所涉及的逻辑功能实体之间的功能关系。
Please see [1] for definition of terms used in describing paging. In addition, this document defines the following terms:
有关描述分页时使用的术语的定义，请参见[1]。此外，本文件定义了以下术语：
Wide Casting - Either broadcasting or multicasting.
宽播-广播或多播。
Inactive Mode - The host is no longer listening for any packets, not even periodically, and not sending packets. The host may be in a powered off state, it may have shut down all interfaces to drastically conserve power, or it may be out of range of a radio access point.
非活动模式-主机不再侦听任何数据包，甚至不定期侦听，也不发送数据包。主机可能处于断电状态，可能已关闭所有接口以大幅节省电源，也可能超出无线电接入点的范围。
An IP paging protocol introduces new security issues. In this section, security issues with relevance to formulating requirements for an IP paging protocol are discussed.
IP寻呼协议引入了新的安全问题。在本节中，将讨论与制定IP寻呼协议要求相关的安全问题。
A DoS (Denial-of-Service) or DDoS (Distributed DoS) attack generally consists of flooding a target network with bogus IP packets in order to cause degraded network performance at victim nodes and/or routers. Performance can be degraded to the point that the network cannot be used. Currently, there is no preventive solution against these attacks, and the impacts can be very important.
DoS（拒绝服务）或DDoS（分布式DoS）攻击通常包括用虚假IP数据包淹没目标网络，从而导致受害节点和/或路由器的网络性能下降。性能可能会降低到无法使用网络的程度。目前，没有针对这些攻击的预防性解决方案，其影响可能非常重要。
In general a DoS attacker profits from a so-called "amplifier" in order to increase the damage caused by his attack. Paging can serve for an attacker as a DoS amplifier.
通常，DoS攻击者从所谓的“放大器”中获利，以增加其攻击造成的伤害。分页可以作为DoS放大器为攻击者服务。
An attacker (a malicious correspondent node) can send large numbers of packets pretending to be sent from different (bogus) correspondent nodes and destined for large numbers of hosts in inactive and dormant modes. This attack, in turn, will be amplified by the paging agent which wide casts paging messages over a paging area, resulting in more than one networks being flooded. Clearly, the damage can be
攻击者（恶意对应节点）可以发送大量数据包，假装从不同（伪造）对应节点发送，并以非活动和休眠模式发送给大量主机。这种攻击反过来又会被寻呼代理放大，寻呼代理在寻呼区域上广泛地投射寻呼消息，导致多个网络被淹没。显然，损害是可以避免的
more important in wireless networks that already suffer from scarce radio bandwidth.
更重要的是，在无线网络中，无线带宽已经非常有限。
Alternatively, an attacker can sort out a host which:
或者，攻击者可以对以下主机进行分类：
1. sends periodic messages declaring that it is in dormant mode,
1. 定期发送消息，声明其处于休眠模式，
2. never replies to paging requests.
2. 从不回复寻呼请求。
Such a node may be the attacker's node itself, or a second node participating in the attack.
此类节点可能是攻击者的节点本身，也可能是参与攻击的第二个节点。
That node is never in inactive mode because of behavior 1 above. In this case, the attacker can send large numbers of packets destined for that host which periodically declares that it is in dormant mode but never replies to paging messages. The impact will be the same as above however in this case the attack will be amplified indefinitely.
由于上述行为1，该节点从不处于非活动模式。在这种情况下，攻击者可以发送大量以该主机为目的地的数据包，该主机定期声明其处于休眠模式，但从不回复寻呼消息。影响与上述相同，但在这种情况下，攻击将无限期放大。
For reliability reasons, the paging protocol may need to make provisions for a paging queue where a paging request is buffered until the requested host replies by sending a location registration message.
出于可靠性原因，寻呼协议可能需要为寻呼队列做出规定，其中寻呼请求被缓冲，直到请求的主机通过发送位置注册消息进行响应。
An attacker can exploit that by sending large numbers of packets having different (bogus) correspondent node addresses and destined for one or more inactive hosts. These packets will be buffered in the paging queue. However, since the hosts are inactive, the paging queue may quickly overflow, blocking the incoming traffic from legitimate correspondent nodes. As a result, all registered dormant hosts may be inaccessible for a while. The attacker can re-launch the attack in a continuous fashion.
攻击者可以通过发送大量具有不同（伪造）对应节点地址且目的地为一个或多个非活动主机的数据包来利用此漏洞。这些数据包将在分页队列中缓冲。但是，由于主机处于非活动状态，分页队列可能会很快溢出，从而阻塞来自合法对应节点的传入流量。因此，所有已注册的休眠主机可能暂时无法访问。攻击者可以连续重新发起攻击。
An attacker together with a bogus host that fails to respond to pages can overflow the buffering provided to hold packets for dormant mode hosts. If the attacker keeps sending packets while the dormant mode host fails to reply, the buffer can overflow.
攻击者与无法响应页面的伪主机一起，可能会使为休眠模式主机保存数据包而提供的缓冲区溢出。如果攻击者在休眠模式主机无法应答时继续发送数据包，则缓冲区可能溢出。
The following vulnerabilities already exist in the absence of IP paging. However, they are included here since they can affect the correct operation of the IP paging protocol.
在没有IP分页的情况下，已经存在以下漏洞。但是，由于它们可能会影响IP寻呼协议的正确操作，因此此处将包括它们。
These vulnerabilities can be exploited by an attacker in order to eliminate a particular host. This, in turn, can be used by an attacker as a stepping stone to launch other attacks.
攻击者可以利用这些漏洞消除特定主机。这反过来又可以被攻击者用作发起其他攻击的垫脚石。
Forced Battery Consumption
强制电池消耗
An attacker can frequently send packets to a host in order to prevent that host from switching to dormant mode. As a result the host may quickly run out of battery.
攻击者可以频繁向主机发送数据包，以防止该主机切换到休眠模式。因此，主机可能会很快耗尽电池。
Bogus Paging Areas
假寻呼区
An attacker can periodically emit malicious packets in order to confuse one or more hosts about their actual locations. Currently, there is no efficient way to authenticate such packets.
攻击者可以定期发出恶意数据包，以便混淆一台或多台主机的实际位置。目前，没有有效的方法来验证这些数据包。
In the case of IP paging, these packets may also contain bogus paging area information. Upon receipt of such a packet, a host may move and send a location registration message pointing to a non-existing or wrong paging area. The functional entities of the IP paging protocol may loose contact with the host.
在IP寻呼的情况下，这些数据包还可能包含虚假的寻呼区域信息。在接收到这样的分组后，主机可以移动并发送指向不存在或错误的寻呼区域的位置注册消息。IP寻呼协议的功能实体可能与主机失去联系。
More importantly, this attack can serve for sorting out a host which shows the behaviors 1 and 2 described in Section 3.1.
更重要的是，此攻击可用于分类显示第3.1节中描述的行为1和2的主机。
Bogus Paging Agents
伪寻呼代理
An attacker can wide cast fake paging messages pretending to be sent by a paging agent. The impacts will be similar to the ones described in Sections 4.1 and 4.3.1. However, depending on how the IP paging protocol is designed, additional harm may be caused.
攻击者可以大范围投射假分页消息，假装由分页代理发送。影响将类似于第4.1节和第4.3.1节中所述的影响。但是，根据IP寻呼协议的设计方式，可能会造成额外的危害。
The following requirements are identified for the IP paging protocol.
针对IP寻呼协议确定了以下要求。
The IP paging protocol MUST minimize impact on the Host's dormant mode operation, in order to minimize excessive power drain.
IP寻呼协议必须将对主机休眠模式操作的影响降至最低，以最大限度地减少过多的功耗。
The IP paging protocol MUST be scalable to millions of Hosts.
IP寻呼协议必须可扩展到数百万台主机。
The protocol SHOULD provide a filter mechanism to allow a Host prior to entering dormant mode to filter which broadcast/multicast/anycast packets active a page. This prevents the Host from awakening out of dormant mode for all broadcast/multicast/anycast traffic.
该协议应提供一种过滤机制，以允许主机在进入休眠模式之前过滤页面上活动的广播/多播/选播数据包。这可防止主机从所有广播/多播/选播流量的休眠模式中唤醒。
The IP paging protocol SHOULD provide a mechanism for the Tracking Agent to determine whether the Host is in inactive mode, to avoid paging when a host is completely unreachable.
IP寻呼协议应为跟踪代理提供一种机制，以确定主机是否处于非活动模式，从而在主机完全无法访问时避免寻呼。
Since the basic issues involved in handling mobile routers are not well understood and since mobile routers have not exhibited a requirement for paging, the IP paging protocol MAY NOT support routers. However, the IP paging protocol MAY support a router acting as a Host.
由于对处理移动路由器涉及的基本问题没有很好的理解，并且由于移动路由器没有显示出寻呼要求，因此IP寻呼协议可能不支持路由器。然而，IP寻呼协议可以支持充当主机的路由器。
Recognizing that there are multiple possible dormant modes on the Host, the IP paging protocol MUST work with different implementations of dormant mode on the Host.
认识到主机上存在多种可能的休眠模式，IP寻呼协议必须与主机上不同的休眠模式实现协同工作。
Recognizing that IETF may support multiple mobility protocols in the future and that paging may be of value to hosts that do not support a mobility protocol, the IP paging protocol MUST be designed so there is no dependence on the underlying mobility protocol or on any mobility protocol at all. The protocol SHOULD specify and provide support for a mobility protocol, if the Host supports one.
认识到IETF将来可能支持多个移动协议，并且寻呼对不支持移动协议的主机可能有价值，因此IP寻呼协议的设计必须确保不依赖于基础移动协议或任何移动协议。如果主机支持移动协议，协议应指定并提供对移动协议的支持。
The IP paging protocol MUST specify the binding to the existing IP mobility protocols, namely mobile IPv4 [2] and mobile IPv6 [3]. The IP paging protocol SHOULD make use of existing registration support.
IP寻呼协议必须指定与现有IP移动协议的绑定，即移动IPv4[2]和移动IPv6[3]。IP分页协议应该利用现有的注册支持。
Upon receipt of a page (either with or without an accompanying L3 packet), the Host MUST execute the steps in its mobility protocol to re-establish a routable L3 link with the Internet.
在收到一个页面（有或没有随附的L3数据包）后，主机必须执行其移动协议中的步骤，以重新建立与Internet的可路由L3链路。
Recognizing that locating a dormant mode mobile requires the network to have a rough idea of where the Host is located, the IP paging protocol SHOULD provide the network a way for the Paging Agent to inform a dormant mode Host what paging area it is in and the IP paging protocol SHOULD provide a means whereby the Host can inform
认识到定位休眠模式移动设备需要网络大致了解主机的位置，IP寻呼协议应为网络提供寻呼代理通知休眠模式主机其所在寻呼区域的方式，IP寻呼协议应提供主机可以通知的方式
the Target Agent when it changes paging area. The IP paging protocol MAY additionally provide a way for the Host to inform the Tracking Agent what paging area it is in at some indeterminate point prior to entering dormant mode.
目标代理在更改分页区域时返回。IP寻呼协议还可以为主机提供一种方式，以便在进入休眠模式之前，在某个不确定的点上通知跟踪代理它所处的寻呼区域。
Recognizing that many existing wireless link protocols support paging at L2 and that these protocols are often intimately tied into the Host's dormant mode support, the IP paging protocol SHOULD provide support to efficiently utilize an L2 paging protocol if available.
认识到许多现有的无线链路协议支持二级寻呼，并且这些协议通常与主机的休眠模式支持紧密相连，因此IP寻呼协议应提供支持，以有效利用二级寻呼协议（如果可用）。
The IP paging protocol MUST allow an arbitrary mapping between subnets and paging areas.
IP寻呼协议必须允许子网和寻呼区域之间的任意映射。
Recognizing that future dormant mode and wireless link protocols may be designed that more efficiently utilize IP, the IP paging protocol SHOULD NOT require L2 support for paging.
认识到未来休眠模式和无线链路协议的设计可以更有效地利用IP，IP寻呼协议不应要求L2支持寻呼。
The IP paging protocol MUST be designed to be robust with respect to failure of network elements involved in the protocol. The self-healing characteristics SHOULD NOT be any worse than existing routing protocols.
IP寻呼协议必须设计为对协议中涉及的网络元件的故障具有鲁棒性。自愈特性不应比现有路由协议差。
The IP paging protocol MUST be designed so that packet delivery is reliable to a high degree of probability. This does not necessarily mean that a reliable transport protocol is required.
IP寻呼协议的设计必须确保数据包传输在很大程度上是可靠的。这并不一定意味着需要可靠的传输协议。
The IP paging protocol MUST be designed to be robust with respect to loss of messages.
IP寻呼协议必须设计为对消息丢失具有鲁棒性。
The IP paging protocol SHOULD provide a way to flexibly auto-configure Paging Agents to reduce the amount of administration necessary in maintaining a wireless network with paging.
IP寻呼协议应提供一种灵活地自动配置寻呼代理的方法，以减少维护具有寻呼功能的无线网络所需的管理量。
The IP paging protocol MUST be flexible in the support of different types of paging areas. Examples are fixed paging areas, where a fixed set of bases stations belong to the paging area for all Hosts, and customized paging areas, where the set of base stations is customized for each Host.
IP寻呼协议必须灵活地支持不同类型的寻呼区域。例如，固定寻呼区域（其中一组固定基站属于所有主机的寻呼区域）和定制寻呼区域（其中一组基站为每个主机定制）。
The IP paging protocol MUST have available authentication and encryption functionality at least equivalent to that provided by IPSEC [5].
IP寻呼协议必须具有可用的身份验证和加密功能，至少与IPSEC提供的功能相同[5]。
The IP paging protocol MUST provide mutually authenticated paging location registration to insulate against replay attacks and to avoid the danger of malicious nodes registering for paging.
IP寻呼协议必须提供相互认证的寻呼位置注册，以防止重播攻击，并避免恶意节点注册寻呼的危险。
The IP paging protocol MUST provide a mechanism for authenticating paging area information distributed by the Paging Agent.
IP寻呼协议必须提供一种机制，用于验证寻呼代理分发的寻呼区域信息。
The IP paging protocol MUST provide a mechanism for authenticating L3 paging messages sent by the Paging Agent to dormant mode Hosts. The protocol MUST support the use of L2 security mechanisms so implementations that take advantage of L2 paging can also be secured.
IP寻呼协议必须提供一种机制，用于验证寻呼代理发送到休眠模式主机的L3寻呼消息。协议必须支持二级安全机制的使用，这样利用二级分页的实现也可以得到安全保护。
The IP paging protocol SHOULD be able to handle large numbers of paging requests without denying access to any legitimate Host nor degrading its performance.
IP寻呼协议应该能够处理大量寻呼请求，而不会拒绝对任何合法主机的访问，也不会降低其性能。
The security of the IP paging protocol SHOULD NOT call for additional power consumption while the Host is in dormant mode, nor require excessive message exchanges.
当主机处于休眠模式时，IP寻呼协议的安全性不应要求额外的功耗，也不应要求过度的消息交换。
The IP paging protocol MUST NOT impose any limitations on a Host's security policies.
IP寻呼协议不得对主机的安全策略施加任何限制。
The IP paging protocol MUST NOT impose any limitations on a Host's ability to conduct end-to-end security.
IP寻呼协议不得对主机执行端到端安全的能力施加任何限制。
The IP paging protocol SHOULD make provisions for detecting and ignoring bogus correspondent nodes prior to paging messages being wide cast on behalf of the correspondent node.
IP寻呼协议应规定在代表对应节点广泛广播寻呼消息之前检测和忽略伪造的对应节点。
In this section, a functional architecture is developed that describes the logical functional entities involved in IP paging and the interfaces between them. Please note that the logical architecture makes absolutely no commitment to any physical implementation of these functional entities whatsoever. A physical implementation may merge particular functional entities. For example, the Paging Agent, Tracking Agent, and Dormant Monitoring Agent may all be merged into one in a particular physical implementation. The purpose of the functional architecture is to identify the relevant system interfaces upon which protocol development may be required, but not to mandate that protocol development will be required on all.
在本节中，将开发一个功能体系结构，描述IP分页中涉及的逻辑功能实体以及它们之间的接口。请注意，逻辑体系结构绝对不承诺这些功能实体的任何物理实现。物理实现可以合并特定的功能实体。例如，寻呼代理、跟踪代理和休眠监视代理都可以在特定的物理实现中合并为一个。功能架构（architecture）的目的是确定可能需要协议开发的相关系统接口，但不是要求所有系统都需要协议开发。
The functional architecture contains the following elements:
功能架构包含以下元素：
Host - The Host (H) is a standard IP host in the sense of [4]. The Host may be connected to a wired IP backbone through a wireless link over which IP datagrams are exchanged (mobile usage pattern), or it may be connected directly to a wired IP network, either intermittently (nomadic usage pattern) or constantly (wired usage pattern). The Host may support some type of IP mobility protocol (for example, mobile IP [2] [3]). The Host is capable of entering dormant mode in order to save power (see [1] for a detailed discussion of dormant mode). The Host also supports a protocol allowing the network to awaken it from dormant mode if a packet arrives. This protocol may be a specialized L2 paging channel or it may be a time-slotted dormant mode in which the Host periodically wakes up and listens to L2 for IP traffic, the details of the L2 implementation are not important. A dormant Host is also responsible for determining when its paging area has changed and for responding to changes in paging area by directly
主机-主机（H）是[4]意义上的标准IP主机。主机可以通过交换IP数据报的无线链路连接到有线IP骨干网（移动使用模式），或者可以间歇地（游牧使用模式）或持续地（有线使用模式）直接连接到有线IP网络。主机可以支持某种类型的IP移动协议（例如，移动IP[2][3]）。主机能够进入休眠模式以节省电源（有关休眠模式的详细讨论，请参阅[1]）。主机还支持一种协议，允许网络在数据包到达时将其从休眠模式唤醒。该协议可能是一个专用的二级寻呼信道，也可能是一种时隙休眠模式，在这种模式下，主机定期唤醒并侦听二级IP流量，二级实现的细节并不重要。休眠主机还负责确定其分页区域何时发生了更改，并直接响应分页区域中的更改
or indirectly informing the Tracking Agent about its location. Since routers are presumed not to require dormant mode support, a Host is never a router.
或间接通知跟踪代理其位置。因为假定路由器不需要休眠模式支持，所以主机永远不是路由器。
Paging Agent - The Paging Agent is responsible for alerting the Host when a packet arrives and the Host is in dormant mode. Alerting of the Host proceeds through a protocol that is peculiar to the L2 link and to the Host's dormant mode implementation, though it may involve IP if supported by the L2. Additionally, the Paging Agent maintains paging areas by periodically wide casting information over the Host's link to identify the paging area. The paging area information may be wide cast at L2 or it may also involve IP. Each paging area is served by a unique Paging Agent.
寻呼代理—寻呼代理负责在数据包到达且主机处于休眠模式时向主机发出警报。主机警报通过L2链路和主机休眠模式实现特有的协议进行，但如果L2支持，则可能涉及IP。此外，寻呼代理通过定期在主机的链路上广泛投射信息来标识寻呼区域，从而维护寻呼区域。寻呼区域信息可以在L2上进行宽广播，也可以涉及IP。每个分页区域都由一个唯一的分页代理提供服务。
Tracking Agent - The Tracking Agent is responsible for tracking a Host's location while it is in dormant mode or active mode, and for determining when Host enters inactive mode. It receives updates from a dormant Host when the Host changes paging area. When a packet arrives for the Host at the Dormant Monitoring Agent, the Tracking Agent is responsible for notifying the Dormant Monitoring Agent, upon request, what Paging Agent is in the Host's last reported paging area. There is a one to one mapping between a Host and a Tracking Agent.
跟踪代理—跟踪代理负责跟踪处于休眠模式或活动模式的主机的位置，并确定主机何时进入非活动模式。当主机更改分页区域时，它接收来自休眠主机的更新。当数据包到达休眠监视代理的主机时，跟踪代理负责根据请求通知休眠监视代理主机上一次报告的寻呼区域中的寻呼代理。主机和跟踪代理之间存在一对一映射。
Dormant Monitoring Agent - The Dormant Monitoring Agent detects the delivery of packets to a Host that is in Dormant Mode (and thus does not have an active L2 connection to the Internet). It is the responsibility of the Dormant Monitoring Agent to query the Tracking Agent for the last known Paging Agent for the Host, and inform the Paging Agent to page the Host. Once the Paging Agent has reported that a routable connection to the Internet exists to the Host, the Dormant Monitoring Agent arranges for delivery of the packet to the Host. In addition, the Host or its Tracking Agent may select a Dormant Monitoring Agent for a Host when the Host enters dormant mode, and periodically as the Host changes paging area.
休眠监控代理-休眠监控代理检测数据包传送到处于休眠模式的主机（因此没有到Internet的活动L2连接）。休眠监视代理负责向跟踪代理查询主机最后一个已知的寻呼代理，并通知寻呼代理寻呼主机。一旦寻呼代理报告主机存在到Internet的可路由连接，休眠监视代理将安排将数据包传送到主机。此外，当主机进入休眠模式时，主机或其跟踪代理可以为主机选择休眠监视代理，并且在主机改变分页区域时周期性地进行选择。
The functional architecture generates the following list of interfaces. Note that the interfaces between functional entities that are combined into a single network element will require no protocol development.
功能架构生成以下接口列表。请注意，合并到单个网元中的功能实体之间的接口将不需要协议开发。
Host - Paging Agent (H-PA) - The H-PA interface supports the following types of traffic:
主机-寻呼代理（H-PA）-H-PA接口支持以下类型的流量：
- Wide casting of paging area information from the Paging Agent.
- 从寻呼代理程序广泛广播寻呼区域信息。
- The Paging Agent alerting the Host when informed by the Dormant Monitoring Agent that a packet has arrived.
- 当休眠监视代理通知主机数据包已到达时，寻呼代理向主机发出警报。
Host - Tracking Agent (H-TA) - The H-TA interface supports the following types of traffic:
主机-跟踪代理（H-TA）-H-TA接口支持以下类型的流量：
- The Host informing the Tracking Agent when it has changed paging area, and, optionally, prior to entering dormant mode, in what paging area it is located.
- 主机在更改分页区域时通知跟踪代理，并且（可选）在进入休眠模式之前通知跟踪代理位于哪个分页区域。
- Optionally, the Host informs the Tracking Agent at a planned transition to inactive mode.
- （可选）主机在计划转换到非活动模式时通知跟踪代理。
Dormant Monitoring Agent - Tracking Agent (DMA-TA) - The DMA-TA interface supports the following types of traffic:
休眠监视代理-跟踪代理（DMA-TA）-DMA-TA接口支持以下类型的流量：
- A report from the Dormant Monitoring Agent to the Tracking Agent that a packet has arrived for a dormant Host for which no route is available.
- 从休眠监视代理发送给跟踪代理的一种报告，表明数据包已到达没有可用路由的休眠主机。
- A report from the Tracking Agent to the Dormant Monitoring Agent giving the Paging Agent to contact in order to page the Host.
- 从跟踪代理发送给休眠监视代理的报告，该报告允许寻呼代理联系以寻呼主机。
- A report from the Tracking Agent to the Dormant Monitoring Agent that a Host has entered inactive mode, if not provided directly by the Host
- 跟踪代理向休眠监视代理发送的报告，表明主机已进入非活动模式（如果主机未直接提供）
- A report from the Tracking Agent to the Dormant Monitoring Agent that a Host has entered dormant mode, if not provided directly by the Host.
- 跟踪代理向休眠监视代理发送的报告，表明主机已进入休眠模式（如果主机未直接提供）。
Dormant Monitoring Agent - Paging Agent (DMA-PA) - The DMA-PA interface supports the following types of traffic:
休眠监视代理-寻呼代理（DMA-PA）-DMA-PA接口支持以下类型的流量：
- A request from the Dormant Monitoring Agent to the Paging Agent to page a particular Host in dormant mode because a packet has arrived for the Host.
- 从休眠监视代理到寻呼代理的一种请求，用于在休眠模式下寻呼特定主机，因为数据包已到达该主机。
- Negative response indication from the Paging Agent if the Host does not respond to a page.
- 如果主机不响应页面，则寻呼代理会发出否定响应指示。
- Positive response from the Paging Agent indication if the Host does respond to a page.
- 寻呼代理的肯定响应指示主机是否响应某个页面。
- Delivery of the packet to the Host.
- 将数据包传送到主机。
Host - Dormant Monitoring Agent (H-DMA) - The H-DMA interface supports the following types of traffic:
主机-休眠监视代理（H-DMA）-H-DMA接口支持以下类型的流量：
- The Host registers to the Dormant Monitoring Agent prior to entering dormant mode, (if needed) with filtering information on which broadcast/multicast/anycast packets trigger a page.
- 主机在进入休眠模式之前（如果需要）向休眠监控代理注册，过滤广播/多播/选播数据包触发页面的信息。
- The Host informs the Dormant Monitoring Agent, when it directly deregisters from the Dormant Monitoring Agent due to a change from dormant mode to active or inactive mode.
- 当主机由于从休眠模式更改为活动或非活动模式而直接从休眠监控代理注销时，主机会通知休眠监控代理。
The functional architecture and interfaces lead to the following diagram.
功能架构和接口导致下图。
+------+ H-TA +----------+
| Host | <----------------------> | Tracking |
+------+ | Agent |
^ ^ +----------+
| | H-DMA ^
| +------------------------------+ |
| | | DMA-TA
| | |
| H-PA | |
v v v
+--------+ DMA-PA +------------+
| Paging | <--------------------> | Dormant |
| Agent | | Monitoring |
+--------+ | Agent |
+------------+
+------+ H-TA +----------+
| Host | <----------------------> | Tracking |
+------+ | Agent |
^ ^ +----------+
| | H-DMA ^
| +------------------------------+ |
| | | DMA-TA
| | |
| H-PA | |
v v v
+--------+ DMA-PA +------------+
| Paging | <--------------------> | Dormant |
| Agent | | Monitoring |
+--------+ | Agent |
+------------+
Figure 1 - Paging Functional Architecture
图1-分页功能架构
The authors would like to thank Arthur Ross for helpful comments on this memo.
作者要感谢Arthur Ross对本备忘录的有益评论。
[1] Kempf, J., "Dormant Mode Host Alerting ("IP Paging") Problem Statement", RFC 3132, June 2001.
[1] Kempf，J.，“休眠模式主机警报（“IP寻呼”）问题声明”，RFC3132，2001年6月。
[2] Perkins, C., ed., "IP Mobility Support", RFC 2002, October, 1996.
[2] Perkins，C.，编辑，“IP移动支持”，RFC 2002，1996年10月。
[3] Johnson, D., and Perkins, C., "Mobility Support in Ipv6", Work in Progress.
[3] Johnson，D.和Perkins，C.，“Ipv6中的移动支持”，正在进行中。
[4] Braden, R., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, October 1989.
[4] Braden，R.，“互联网主机的要求-通信层”，标准3，RFC 1122，1989年10月。
[5] Kent, S., and R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401, November 1998.
[5] Kent，S.和R.Atkinson，“互联网协议的安全架构”，RFC 2401，1998年11月。
James Kempf Sun Microsystems Laboratories 901 San Antonio Rd. UMTV29-235 Palo Alto, CA 95303-4900 USA
詹姆斯·肯普夫太阳微系统实验室美国加利福尼亚州帕洛阿尔托市圣安东尼奥路901号UMTV29-235，邮编95303-4900
Phone: +1 650 336 1684
Fax: +1 650 691 0893
EMail: James.Kempf@Sun.COM
Phone: +1 650 336 1684
Fax: +1 650 691 0893
EMail: James.Kempf@Sun.COM
Pars Mutaf INRIA Rhone-Alpes 655 avenue de l'Europe 38330 Montbonnot Saint-Martin FRANCE
法国圣马丁蒙特邦诺大街655号法国罗纳阿尔卑斯山穆塔夫公园
Phone:
Fax: +33 4 76 61 52 52
EMail: pars.mutaf@inria.fr
Phone:
Fax: +33 4 76 61 52 52
EMail: pars.mutaf@inria.fr
Claude Castelluccia INRIA Rhone-Alpes 655 avenue de l'Europe 38330 Montbonnot Saint-Martin FRANCE
克劳德·卡斯特卢西亚·因里亚·罗纳·阿尔卑斯欧洲大道655号法国蒙博诺圣马丁市38330号
Phone: +33 4 76 61 52 15
Fax: +33 4 76 61 52 52
EMail: claude.castelluccia@inria.fr
Phone: +33 4 76 61 52 15
Fax: +33 4 76 61 52 52
EMail: claude.castelluccia@inria.fr
Nobuyasu Nakajima Toshiba America Research, Inc. P.O. Box 136 Convent Station, NJ 07961-0136 USA
中岛信泰东芝美国研究有限公司美国新泽西州修道院站136号邮政信箱07961-0136
Phone: +1 973 829 4752
EMail: nnakajima@tari.toshiba.com
Phone: +1 973 829 4752
EMail: nnakajima@tari.toshiba.com
Yoshihiro Ohba Toshiba America Research, Inc. P.O. Box 136 Convent Station, NJ 07961-0136 USA
美国新泽西州修道院站136号邮政信箱东芝美国研究公司大叶吉弘07961-0136
Phone: +1 973 829 5174
Fax: +1 973 829 5601
EMail: yohba@tari.toshiba.com
Phone: +1 973 829 5174
Fax: +1 973 829 5601
EMail: yohba@tari.toshiba.com
Ramachandran Ramjee Bell Labs, Lucent Technologies Room 4g-526 101 Crawfords Corner Road Holmdel, NJ 07733 USA
Ramachandran Ramjee Bell实验室，朗讯科技4g-526室，美国新泽西州霍姆德尔克劳福德角路101号，邮编：07733
Phone: +1 732 949 3306
Fax: +1 732 949 4513
EMail: ramjee@bell-labs.com
Phone: +1 732 949 3306
Fax: +1 732 949 4513
EMail: ramjee@bell-labs.com
Yousuf Saifullah Nokia Research Center 6000 Connection Dr. Irving, TX 75039 USA
优素福·赛福拉诺基亚研究中心6000连接美国德克萨斯州欧文博士75039
Phone: +1 972 894 6966
Fax: +1 972 894 4589
EMail: Yousuf.Saifullah@nokia.com
Phone: +1 972 894 6966
Fax: +1 972 894 4589
EMail: Yousuf.Saifullah@nokia.com
Behcet Sarikaya Alcatel USA, M/S CT02 1201 Campbell Rd. Richardson, TX 75081-1936 USA
Behcet Sarikaya Alcatel USA，美国德克萨斯州理查森坎贝尔路1201号CT02，邮编75081-1936
Phone: +1 972 996 5075
Fax: +1 972 996 5174
EMail: Behcet.Sarikaya@usa.alcatel.com
Phone: +1 972 996 5075
Fax: +1 972 996 5174
EMail: Behcet.Sarikaya@usa.alcatel.com
Xiaofeng Xu Alcatel USA, M/S CT02 1201 Campbell Rd. Richardson, TX 75081-1936 USA
徐晓峰美国阿尔卡特公司，邮编：美国德克萨斯州理查森坎贝尔路1201号CT02，邮编：75081-1936
Phone: +1 972 996 2047
Fax: +1 972 996 5174
Email: xiaofeng.xu@usa.alcatel.com
Phone: +1 972 996 2047
Fax: +1 972 996 5174
Email: xiaofeng.xu@usa.alcatel.com
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。