draft-ietf-ancp-pon-03.txt   draft-ietf-ancp-pon-04.txt 
Network Working Group Nabil Bitar(ed.) Network Working Group Nabil Bitar(ed.)
Verizon Verizon
Internet Draft Internet Draft
Intended Status: Informational Sanjay Wadhwa (ed.) Intended Status: Informational Sanjay Wadhwa (ed.)
Alcatel-Lucent Alcatel-Lucent
Expires: January 16, 2013 Expires: June 02, 2013
Thomas Haag Thomas Haag
Deutsche Telekom Deutsche Telekom
Hongyu Li Hongyu Li
Huawei Technologies Huawei Technologies
July 16, 2012 December 02, 2012
Applicability of Access Node Control Mechanism to Applicability of Access Node Control Mechanism to
PON based Broadband Networks PON based Broadband Networks
draft-ietf-ancp-pon-03.txt draft-ietf-ancp-pon-04.txt
Abstract Abstract
The purpose of this document is to provide applicability of the The purpose of this document is to provide applicability of the
Access Node Control mechanism to PON-based broadband access. The Access Node Control mechanism to PON-based broadband access. The
need for an Access Node Control mechanism between a Network need for an Access Node Control mechanism between a Network
Access Server (NAS) and an Access Node Complex (a combination of Access Server (NAS) and an Access Node Complex (a combination of
Optical Line Termination (OLT) and Optical Network Termination Optical Line Termination (OLT) and Optical Network Termination
(ONT) elements) is described in a multi-service reference (ONT) elements) is described in a multi-service reference
architecture in order to perform QoS-related, service-related and architecture in order to perform QoS-related, service-related and
Subscriber-related operations. The Access Node Control mechanism Subscriber-related operations. The Access Node Control mechanism
is also extended for interaction between components of the Access is also extended for interaction between components of the Access
Node Complex (OLT and ONT). The Access Node Control mechanism Node Complex (OLT and ONT). The Access Node Control mechanism
will ensure that the transmission of information between the NAS will ensure that the transmission of information between the NAS
and Access Node Complex (ANX) and between the OLT and ONT within and Access Node Complex (ANX) and between the OLT and ONT within
an ANX does not need to go through distinct element managers but an ANX does not need to go through distinct element managers but
rather uses a direct device-to-device communication and stays on rather uses a direct device-to-device communication and stays on
net. This allows for performing access link related operations net. This allows for performing access link related operations
within those network elements to meet performance objectives. within those network elements to meet performance objectives.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current working documents as Internet-Drafts. The list of current
Internet-Drafts is at Internet-Drafts is at
http://datatracker.ietf.org/drafts/current/. http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work Drafts as reference material or to cite them other than as "work
in progress." in progress."
This Internet-Draft will expire on January 16,2013. This Internet-Draft will expire on June 02,2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as Copyright (c) 2012 IETF Trust and the persons identified as
the document authors. All rights reserved. the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date (http://trustee.ietf.org/license-info) in effect on the date
of publication of this document. Please review these documents of publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described document must include Simplified BSD License text as described
in Section 4.e of the Trust Legal Provisions and are provided in Section 4.e of the Trust Legal Provisions and are provided
without warranty as described in the Simplified BSD License. without warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction..................................... 4 1. Introduction............................................ 4
2. Terminology...................................... 5 2. Terminology............................................. 5
3. Motivation for explicit extension of ANCP to FTTx 3. Motivation for explicit extension of ANCP to FTTx PON.... 7
PON................................................. 7 4. Reference Model for PON Based Broadband Access Network.. 8
4. Reference Model for PON Based Broadband Access 4.1. Functional Blocks 11
Network............................................. 8 4.1.1. Home Gateway............................... 11
4.1. Functional Blocks............................. 11 4.1.2. PON Access................................. 11
4.1.1. Home Gateway................................ 11 4.1.3. Access Node Complex........................ 11
4.1.2. PON Access.................................. 11 4.1.4. Access Node Complex Uplink to the NAS...... 12
4.1.3. Access Node Complex......................... 11 4.1.5. Aggregation Network........................ 12
4.1.4. Access Node Complex Uplink to the NAS....... 12 4.1.6. Network Access Server...................... 12
4.1.5. Aggregation Network......................... 12 4.1.7. Regional Network........................... 12
4.1.6. Network Access Server....................... 12
4.1.7. Regional Network............................ 12
4.2. Access Node Complex Control Reference 4.2. Access Node Complex Control Reference
Architecture Options............................... 13 Architecture Options 13
4.2.1. ANCP+OMCI ANX Control....................... 13 4.2.1. ANCP+OMCI ANX Control...................... 13
4.2.2. All-ANCP ANX Control........................ 14 4.2.2. All-ANCP ANX Control....................... 14
5. Concept of Access Node Control Mechanism for PON 5. Concept of Access Node Control Mechanism for PON
Based Access....................................... 15 Based Access........................................... 15
6. Multicast....................................... 18 6. Multicast............................................. 18
6.1. Multicast Conditional Access.................. 19 6.1. Multicast Conditional Access 19
6.2. Multicast Admission Control................... 22 6.2. Multicast Admission Control 21
6.3. Multicast Accounting.......................... 34 6.3. Multicast Accounting 33
7. Remote Connectivity Check....................... 35 7. Remote Connectivity Check............................. 34
8. Access Topology Discovery....................... 35 8. Access Topology Discovery............................. 35
9. Access Loop Configuration....................... 37 9. Access Loop Configuration............................. 37
10. Security Considerations........................ 37 10. Security Considerations.............................. 37
11. Differences in ANCP applicability between DSL and 11. Differences in ANCP applicability between DSL and PON. 38
PON................................................ 38 12. ANCP versus OMCI between the OLT and ONT/ONU......... 39
12. ANCP versus OMCI between the OLT and ONT/ONU... 40 13. IANA Consideration................................... 40
13. IANA Considerations............................ 40 14. Acknowledgements..................................... 40
14. Acknowledgements............................... 41 15. References.....................................,..... 40
15. References..................................... 41 15.1. Normative References 40
15.1. Normative References......................... 41 15.2. Informative References 41
15.2. Informative References....................... 41
1. Introduction 1. Introduction
Passive Optical Networks (PONs) based on BPON [G.983.1] and GPON Passive Optical Networks (PONs) based on BPON [G.983.1] and GPON
[G.984.1] are being deployed across carrier networks. There are [G.984.1] are being deployed across carrier networks. There are
two models for PON deployment: Fiber to the building/curb two models for PON deployment: Fiber to the building/curb
(FTTB/FTTC), and Fiber to the Premises (FTTP). In the FTTB/C (FTTB/FTTC), and Fiber to the Premises (FTTP). In the FTTB/C
deployment, the last mile connectivity to the subscriber premises deployment, the last mile connectivity to the subscriber premises
is provided over the local Copper loop, often using Very High is provided over the local Copper loop, often using Very High
Speed Digital Subscriber line (VDSL). In the FTTP case, PON Speed Digital Subscriber line (VDSL). In the FTTP case, PON
extends to the premises of the subscriber. In addition, there are extends to the premises of the subscriber. In addition, there are
four main PON technologies: (1) Broadband PON (BPON), (2) Gigabit four main PON technologies: (1) Broadband PON (BPON), (2) Gigabit
skipping to change at page 5, line 43 skipping to change at page 5, line 41
environments between the AN complex (ANX) and the NAS, environments between the AN complex (ANX) and the NAS,
specifically focusing on bandwidth dedicated for multicast and specifically focusing on bandwidth dedicated for multicast and
shared bandwidth between multicast and unicast. shared bandwidth between multicast and unicast.
[RFC5851] provides the framework and requirements for [RFC5851] provides the framework and requirements for
coordinated admission control between a NAS and an AN with coordinated admission control between a NAS and an AN with
special focus on DSL deployments. This document extends that special focus on DSL deployments. This document extends that
framework and the related requirements to explicitly address framework and the related requirements to explicitly address
PON deployments. PON deployments.
2. Terminology 2. Terminology
- PON (Passive Optical Network) [G.983.1][G.984.1]: a point-to- - PON (Passive Optical Network) [G.983.1][G.984.1]: a point-to-
multipoint fiber to the premises network architecture in which multipoint fiber to the premises network architecture in which
unpowered splitters are used to enable the splitting of an unpowered splitters are used to enable the splitting of an
optical signal from a central office on a single optical fiber to optical signal from a central office on a single optical fiber to
multiple premises. Up to 32-128 may be supported on the same PON. multiple premises. Up to 32-128 may be supported on the same PON.
A PON configuration consists of an Optical Line Terminal (OLT) at A PON configuration consists of an Optical Line Terminal (OLT) at
the Service Provider's Central Office (CO) and a number of the Service Provider's Central Office (CO) and a number of
Optical Network Units or Terminals (ONU/ONT) near end users, with Optical Network Units or Terminals (ONU/ONT) near end users, with
an optical distribution network (ODN) composed of fibers and an optical distribution network (ODN) composed of fibers and
skipping to change at page 7, line 30 skipping to change at page 7, line 26
the ANX and the access loop logical port on the ANX to the the ANX and the access loop logical port on the ANX to the
subscriber (customer) premises, and is used in any interaction subscriber (customer) premises, and is used in any interaction
between NAS and ANX that relates to access-loops. Logically it is between NAS and ANX that relates to access-loops. Logically it is
composed of information containing identification of the OLT (the composed of information containing identification of the OLT (the
OLT may be physically directly connected to the NAS), the PON OLT may be physically directly connected to the NAS), the PON
port on the OLT, the ONT/ONU, and the port on the ONT/ONU port on the OLT, the ONT/ONU, and the port on the ONT/ONU
connecting to the subscriber HGW. When acting as a DHCP relay connecting to the subscriber HGW. When acting as a DHCP relay
agent, the OLT can encode PON-Customer-ID in the "Agent-Circuit- agent, the OLT can encode PON-Customer-ID in the "Agent-Circuit-
Identifier" Sub-option in Option-82 of the DHCP messages [RFC3046]. Identifier" Sub-option in Option-82 of the DHCP messages [RFC3046].
3. Motivation for explicit extension of ANCP to FTTx PON 3. Motivation for explicit extension of ANCP to FTTx PON
The fundamental difference between PON and DSL is that a PON is The fundamental difference between PON and DSL is that a PON is
an optical broadcast network by definition. That is, at the PON an optical broadcast network by definition. That is, at the PON
level, every ONT on the same PON sees the same signal. However, level, every ONT on the same PON sees the same signal. However,
the ONT filters only those PON frames addressed to it. Encryption the ONT filters only those PON frames addressed to it. Encryption
is used on the PON to prevent eavesdropping. is used on the PON to prevent eavesdropping.
The broadcast PON capability is very suitable to delivering The broadcast PON capability is very suitable to delivering
multicast content to connected premises, maximizing bandwidth multicast content to connected premises, maximizing bandwidth
usage efficiency on the PON. Similar to DSL deployments, enabling usage efficiency on the PON. Similar to DSL deployments, enabling
skipping to change at page 8, line 43 skipping to change at page 8, line 37
- Multicast - Multicast
- Optimized multicast delivery - Optimized multicast delivery
- Unified video resource control - Unified video resource control
- NAS based provisioning of ANX - NAS based provisioning of ANX
- Remote connectivity check - Remote connectivity check
4. Reference Model for PON Based Broadband Access Network 4. Reference Model for PON Based Broadband Access Network
An overall end-to-end reference architecture of a PON access An overall end-to-end reference architecture of a PON access
network is depicted in Figure 1 and Figure 2 with ONT serving a network is depicted in Figure 1 and Figure 2 with ONT serving a
single HGW, and ONT/ONU serving multiples HGWs, respectively. An single HGW, and ONT/ONU serving multiples HGWs, respectively. An
OLT may provide FTTP and FTTB/C access at the same time but most OLT may provide FTTP and FTTB/C access at the same time but most
likely not on the same PON port. Specifically, the following PON likely not on the same PON port. Specifically, the following PON
cases are addressed in the context of this reference cases are addressed in the context of this reference
architecture: architecture:
- BPON with Ethernet uplink to the NAS and ATM on the PON - BPON with Ethernet uplink to the NAS and ATM on the PON
skipping to change at page 10, line 50 skipping to change at page 10, line 50
| | | | | | | || | | or|-|HGW| | | | | | | | || | | or|-|HGW|
|Broadband| | +-----+ | +-----+ +----+| | |ONU| +---+ |Broadband| | +-----+ | +-----+ +----+| | |ONU| +---+
|Network |-+-|NAS | +----------------+ | | | |Network |-+-|NAS | +----------------+ | | |
ASP---+ | | +-----+ | | | +---+ ASP---+ | | +-----+ | | | +---+
| | | +-----+ | | |-|HGW| | | | +-----+ | | |-|HGW|
+---------+ +-|NAS | | +---+ +---+ +---------+ +-|NAS | | +---+ +---+
+-----+ | +-----+ |
| +---+ +---+ | +---+ +---+
+-|ONT|-|HGW| +-|ONT|-|HGW|
+---+ +---+ +---+ +---+
Figure 2: FTTP/FTTB/C with multi-subscriber ONT/ONU serving Figure 2: FTTP/FTTB/C with multi-subscriber ONT/ONU serving
MTUs/MDUs. MTUs/MDUs.
The following sections describe the functional blocks and network The following sections describe the functional blocks and network
segments in the PON access reference architecture. segments in the PON access reference architecture.
4.1. Functional Blocks 4.1. Functional Blocks
4.1.1. Home Gateway 4.1.1. Home Gateway
The Home Gateway (HGW) connects the different Customer Premises The Home Gateway (HGW) connects the different Customer Premises
Equipment (CPE) to the ANX and the access network. In case of Equipment (CPE) to the ANX and the access network. In case of
PON, the HGW is a layer 3 router. In this case, the HGW performs PON, the HGW is a layer 3 router. In this case, the HGW performs
IP configuration of devices within the home via DHCP, and IP configuration of devices within the home via DHCP, and
performs Network Address and Port Translation (NAPT) between the performs Network Address and Port Translation (NAPT) between the
LAN and WAN side. In case of FTTP/B/C, the HGW connects to the LAN and WAN side. In case of FTTP/B/C, the HGW connects to the
ONT/ONU over an Ethernet interface. That Ethernet interface could ONT/ONU over an Ethernet interface. That Ethernet interface could
be over an Ethernet physical port or over another medium. In case be over an Ethernet physical port or over another medium. In case
of FTTP, it is possible to have a single box GPON CPE solution, of FTTP, it is possible to have a single box GPON CPE solution,
where the ONT encompasses the HGW functionality as well as the where the ONT encompasses the HGW functionality as well as the
GPON adaptation function. GPON adaptation function.
4.1.2. PON Access 4.1.2. PON Access
PON access is composed of the ONT/ONU and OLT. PON ensures PON access is composed of the ONT/ONU and OLT. PON ensures
physical connectivity between the ONT/ONU at the customer physical connectivity between the ONT/ONU at the customer
premises and the OLT. PON framing can be BPON (in case of BPON) premises and the OLT. PON framing can be BPON (in case of BPON)
or GPON (in case of GPON). The protocol encapsulation on BPON is or GPON (in case of GPON). The protocol encapsulation on BPON is
based on multi-protocol encapsulation over AAL5, defined in based on multi-protocol encapsulation over AAL5, defined in
[RFC2684]. This covers PPP over Ethernet (PPPoE, defined in [RFC2684]. This covers PPP over Ethernet (PPPoE, defined in
[RFC2516]), or bridged IP (IPoE). The protocol encapsulation on [RFC2516]), or bridged IP (IPoE). The protocol encapsulation on
GPON is always IPoE. In all cases, the connection between the AN GPON is always IPoE. In all cases, the connection between the AN
(OLT) and the NAS (or BNG) is assumed to be Ethernet in this (OLT) and the NAS (or BNG) is assumed to be Ethernet in this
document. document.
4.1.3. Access Node Complex 4.1.3. Access Node Complex
This is composed of OLT and ONT/ONU and is defined in section 2. This is composed of OLT and ONT/ONU and is defined in section 2.
4.1.4. Access Node Complex Uplink to the NAS 4.1.4. Access Node Complex Uplink to the NAS
The ANX uplink connects the OLT to the NAS. The fundamental The ANX uplink connects the OLT to the NAS. The fundamental
requirements for the ANX uplink are to provide traffic requirements for the ANX uplink are to provide traffic
aggregation, Class of Service distinction and customer separation aggregation, Class of Service distinction and customer separation
and traceability. This can be achieved using an ATM or an and traceability. This can be achieved using an ATM or an
Ethernet based technology. The focus in this document is on Ethernet based technology. The focus in this document is on
Ethernet as stated earlier. Ethernet as stated earlier.
4.1.5. Aggregation Network 4.1.5. Aggregation Network
The aggregation network provides traffic aggregation towards the The aggregation network provides traffic aggregation towards the
NAS. The Aggregation network is assumed to be Ethernet in this NAS. The Aggregation network is assumed to be Ethernet in this
document. document.
4.1.6. Network Access Server 4.1.6. Network Access Server
The NAS is a network device which aggregates multiplexed The NAS is a network device which aggregates multiplexed
Subscriber traffic from a number of ANXs. The NAS plays a central Subscriber traffic from a number of ANXs. The NAS plays a central
role in per-subscriber policy enforcement and QoS. It is often role in per-subscriber policy enforcement and QoS. It is often
referred to as a Broadband Network Gateway (BNG) or Broadband referred to as a Broadband Network Gateway (BNG) or Broadband
Remote Access Server (BRAS). A detailed definition of the NAS is Remote Access Server (BRAS). A detailed definition of the NAS is
given in [RFC2881]. The NAS interfaces to the aggregation network given in [RFC2881]. The NAS interfaces to the aggregation network
by means of 802.1Q or 802.1 Q-in-Q Ethernet interfaces, and by means of 802.1Q or 802.1 Q-in-Q Ethernet interfaces, and
towards the Regional Network by means of transport interfaces towards the Regional Network by means of transport interfaces
(e.g., GigE, PPP over SONET). The NAS functionality corresponds (e.g., GigE, PPP over SONET). The NAS functionality corresponds
to the BNG functionality described in BroadBand Forum (BBF) TR- to the BNG functionality described in BroadBand Forum (BBF) TR-
101 [TR-101]. In addition, the NAS supports the Access Node 101 [TR-101]. In addition, the NAS supports the Access Node
Control functionality defined for the respective use cases in Control functionality defined for the respective use cases in
this document. this document.
4.1.7. Regional Network 4.1.7. Regional Network
The Regional Network connects one or more NAS and associated The Regional Network connects one or more NAS and associated
Access Networks to Network Service Providers (NSPs) and Access Networks to Network Service Providers (NSPs) and
Application Service Providers (ASPs). The NSP authenticates Application Service Providers (ASPs). The NSP authenticates
access and provides and manages the IP address to Subscribers. It access and provides and manages the IP address to Subscribers. It
is responsible for overall service assurance and includes is responsible for overall service assurance and includes
Internet Service Providers (ISPs). The ASP provides application Internet Service Providers (ISPs). The ASP provides application
services to the application Subscriber (gaming, video, content on services to the application Subscriber (gaming, video, content on
demand, IP telephony, etc.). The NAS can be part of the NSP demand, IP telephony, etc.). The NAS can be part of the NSP
network. Similarly, the NSP can be the ASP. network. Similarly, the NSP can be the ASP.
4.2. Access Node Complex Control Reference Architecture Options 4.2. Access Node Complex Control Reference Architecture Options
Section 3 details the differences between xDSL access and PON Section 3 details the differences between xDSL access and PON
access and the implication of these differences on DSLAM control access and the implication of these differences on DSLAM control
vs. OLT and ONT/ONU (access node complex (ANX)) control. The vs. OLT and ONT/ONU (access node complex (ANX)) control. The
following sections describe two reference models: (1) ANCP+OMCI following sections describe two reference models: (1) ANCP+OMCI
ANX control, and (2) all-ANCP ANX control. That is, the two ANX control, and (2) all-ANCP ANX control. That is, the two
models differ in the ONT/ONU control within the ANX. models differ in the ONT/ONU control within the ANX.
Implementations, out of the scope of this document, may choose to Implementations, out of the scope of this document, may choose to
implement one or the other based on the ONT/ONU type and the implement one or the other based on the ONT/ONU type and the
capabilities of the ONT/ONU and OLT. It is possible for an OLT or capabilities of the ONT/ONU and OLT. It is possible for an OLT or
skipping to change at page 13, line 28 skipping to change at page 13, line 28
and same PON. Section 12 describes the differences between OMCI and same PON. Section 12 describes the differences between OMCI
and ANCP in controlling the ONU/ONT. and ANCP in controlling the ONU/ONT.
OMCI is designed as a protocol between the OLT and ONT/ONU. It OMCI is designed as a protocol between the OLT and ONT/ONU. It
enables the OLT to configure and administer capabilities on the enables the OLT to configure and administer capabilities on the
ONT/ONU in BPON, GPON and XPON. ANCP is designed as a protocol ONT/ONU in BPON, GPON and XPON. ANCP is designed as a protocol
between the NAS and access node. It enables the NAS to enforce between the NAS and access node. It enables the NAS to enforce
dynamic policies on the access node, and the access node to dynamic policies on the access node, and the access node to
report events to the NAS among other functions. report events to the NAS among other functions.
4.2.1. ANCP+OMCI ANX Control 4.2.1. ANCP+OMCI ANX Control
Figure 3 depicts the reference model for ANCP+OMCI ANX control. Figure 3 depicts the reference model for ANCP+OMCI ANX control.
In this model, ANCP is enabled between the NAS and a connected In this model, ANCP is enabled between the NAS and a connected
OLT, and OMCI is enabled between the OLT and an attached ONT/ONU. OLT, and OMCI is enabled between the OLT and an attached ONT/ONU.
NAS communicates with the ANX via ANCP. The OLT acts as an NAS communicates with the ANX via ANCP. The OLT acts as an
ANCP/OMCI gateway for communicating necessary events and policies ANCP/OMCI gateway for communicating necessary events and policies
between the OLT and ONT/ONU within the ANX and for communicating between the OLT and ONT/ONU within the ANX and for communicating
relevant policies and events between the ONT/ONU and the NAS. The relevant policies and events between the ONT/ONU and the NAS. The
functionality performed by the OLT as ANCP/OMCI gateway will be functionality performed by the OLT as ANCP/OMCI gateway will be
application dependent (e.g., multicast control, topology application dependent (e.g., multicast control, topology
skipping to change at page 14, line 36 skipping to change at page 14, line 34
HGW: Home Gateway HGW: Home Gateway
NAS: Network Access Server NAS: Network Access Server
PON: Passive Optical Network PON: Passive Optical Network
OLT: Optical Line Terminal OLT: Optical Line Terminal
ONT: Optical Network Terminal ONT: Optical Network Terminal
ONU: Optical Network Unit ONU: Optical Network Unit
Figure 3: Access Network with single ANCP+OMCI access control Figure 3: Access Network with single ANCP+OMCI access control
4.2.2. All-ANCP ANX Control 4.2.2. All-ANCP ANX Control
Figure 4 depicts the All-ANCP ANX control reference model. In Figure 4 depicts the All-ANCP ANX control reference model. In
this model, an ANCP session is enabled between a NAS and a this model, an ANCP session is enabled between a NAS and a
connected OLT, and another ANCP session is enabled between the connected OLT, and another ANCP session is enabled between the
OLT and a connected ONT/ONU. ANCP enables communication of OLT and a connected ONT/ONU. ANCP enables communication of
policies and events between the OLT and the ANX. The OLT acts as policies and events between the OLT and the ANX. The OLT acts as
a gateway to relay policies and events between the NAS and a gateway to relay policies and events between the NAS and
ONT/ONU within the ANX in addition to communicating policies and ONT/ONU within the ANX in addition to communicating policies and
events between the OLT and ONT/ONU. It should be noted that in events between the OLT and ONT/ONU. It should be noted that in
this model, OMCI(not shown) is expected to be simultaneously this model, OMCI(not shown) is expected to be simultaneously
skipping to change at page 15, line 37 skipping to change at page 15, line 37
HGW: Home Gateway HGW: Home Gateway
NAS: Network Access Server NAS: Network Access Server
PON: Passive Optical Network PON: Passive Optical Network
OLT: Optical Line Terminal OLT: Optical Line Terminal
ONT: Optical Network Terminal ONT: Optical Network Terminal
ONU: Optical Network Unit ONU: Optical Network Unit
Figure 4: All-ANCP ANX Reference Model Figure 4: All-ANCP ANX Reference Model
5. Concept of Access Node Control Mechanism for PON Based 5. Concept of Access Node Control Mechanism for PON Based
Access Access
The high-level communication framework for an Access Node Control The high-level communication framework for an Access Node Control
mechanism is shown in Figure 5 for the ALL-ANCP ANX control mechanism is shown in Figure 5 for the ALL-ANCP ANX control
model. The Access Node Control mechanism defines a quasi real- model. The Access Node Control mechanism defines a quasi real-
time, general-purpose method for multiple network scenarios with time, general-purpose method for multiple network scenarios with
an extensible communication scheme, addressing the different use an extensible communication scheme, addressing the different use
cases that are described in the sections that follow. The access cases that are described in the sections that follow. The access
node control mechanism is also extended to run between OLT and node control mechanism is also extended to run between OLT and
ONT/ONU. The mechanism consists of control function, and ONT/ONU. The mechanism consists of control function, and
skipping to change at page 18, line 7 skipping to change at page 18, line 7
ANCP may be used in variant ways and may interwork with other ANCP may be used in variant ways and may interwork with other
protocols, e.g., OMCI. In the ANCP+OMCI model described earlier, protocols, e.g., OMCI. In the ANCP+OMCI model described earlier,
the NAS maintains ANCP adjacency with the OLT while the OLT the NAS maintains ANCP adjacency with the OLT while the OLT
controls the ONT/ONU via OMCI. The messages shown in Figure 6 controls the ONT/ONU via OMCI. The messages shown in Figure 6
show the conceptual message flow for this model. The actual use show the conceptual message flow for this model. The actual use
of these flows, and the times or frequencies when these messages of these flows, and the times or frequencies when these messages
are generated depend on the actual use cases. are generated depend on the actual use cases.
+--------+ +--------+
| Policy | | Policy |
| Server | | Server | +---+ +---+
+--------+ +---+ +---+ +--------+ +---- |ONT|--------|HGW|
| +---- |ONT|--------|HGW|
| | +---+ +---+ | | +---+ +---+
| +--------------- |-------------+ | +--------------- |-------------+
+----+ | +----+ | +-----+ | +---+ +----+ | +----+ | +-----+ | +---+
|NAS |---------------| | | | |-|----|HGW| |NAS |---------------| | | | |-|----|HGW|
| |<------------->| | | | ONU | | +---+ | |<------------->| | | | ONU | | +---+
+----+ ANCP | |OLT |------<PON>----| | | +----+ ANCP | |OLT |------<PON>----| | |
| | | | | | | +---+ | | | | | | | +---+
| | | |<------------->| |------|HGW| | | | |<------------->| |------|HGW|
| | +----+ OMCI +-----+ | +---+ | | +----+ OMCI +-----+ | +---+
| +-----------------------------+ | +-----------------------------+
skipping to change at page 18, line 35 skipping to change at page 18, line 34
| Control Response |<------------------- | | Control Response |<------------------- |
|<-------------------| | |<-------------------| |
| |Admission Request | | |Admission Request |
| Admission Request |<--------------------| | Admission Request |<--------------------|
|<-------------------| | |<-------------------| |
|Admission Response | | |Admission Response | |
|------------------->|Admission Response | |------------------->|Admission Response |
| |-------------------->| | |-------------------->|
|Information Report | | |Information Report | |
|<-------------------| | |<-------------------| |
Access Node Control Operating Maintenance ANCP Mechanoism OMCI
Mechanism Control Interface (OMCI)
<--------------------><--------------------> <--------------------><-------------------->
PPP, DHCP, IP PPP, DHCP, IP
<-------------------------------------------------------> <------------------------------------------------------->
Figure 6: Conceptual Message Flow for ANCP+OMCI ANX control Figure 6: Conceptual Message Flow for ANCP+OMCI ANX control model.
model.
6. Multicast 6. Multicast
With the rise of supporting IPTV services in a resource-efficient With the rise of supporting IPTV services in a resource-efficient
way, multicast services are becoming increasingly important. way, multicast services are becoming increasingly important.
In order to gain bandwidth optimization with multicast, the In order to gain bandwidth optimization with multicast, the
replication of multicast content per access-loop needs to be replication of multicast content per access-loop needs to be
distributed to the ANX. This can be done by ANX (OLT and ONT/ONU) distributed to the ANX. This can be done by ANX (OLT and ONT/ONU)
becoming multicast aware by implementing an IGMP snooping and/or becoming multicast aware by implementing an IGMP snooping and/or
proxy function. The replication thus needs to be distributed proxy function. The replication thus needs to be distributed
between NAS, aggregation nodes, and ANX. In case of GPON, and in between NAS, aggregation nodes, and ANX. In case of GPON, and in
skipping to change at page 19, line 34 skipping to change at page 19, line 30
this scenario, the NAS can use ANCP to create replication state this scenario, the NAS can use ANCP to create replication state
in the ANX for efficient multicast replication. The NAS sends a in the ANX for efficient multicast replication. The NAS sends a
single copy of the multicast stream towards the ANX. The NAS can single copy of the multicast stream towards the ANX. The NAS can
perform network-based conditional access and multicast admission perform network-based conditional access and multicast admission
control on multicast joins, and create replication state in the control on multicast joins, and create replication state in the
ANX if the request is admitted by the NAS. ANX if the request is admitted by the NAS.
The following sections describe various use cases related to The following sections describe various use cases related to
multicast. multicast.
6.1. Multicast Conditional Access 6.1. Multicast Conditional Access
In a Broadband FTTP/B/C access scenario, Service Providers may In a Broadband FTTP/B/C access scenario, Service Providers may
want to dynamically control, at the network level, access to some want to dynamically control, at the network level, access to some
multicast flows on a per user basis. This may be used in order to multicast flows on a per user basis. This may be used in order to
differentiate among multiple Service Offers or to differentiate among multiple Service Offers or to
realize/reinforce conditional access based on customer realize/reinforce conditional access based on customer
subscription. Note that, in some environments, application layer subscription. Note that, in some environments, application layer
conditional access by means of Digital Rights Management (DRM) conditional access by means of Digital Rights Management (DRM)
for instance may provide sufficient control so that network-based for instance may provide sufficient control so that network-based
Multicast conditional access may not be needed. However, network Multicast conditional access may not be needed. However, network
skipping to change at page 22, line 5 skipping to change at page 21, line 38
service. service.
Instead of including the channel list(s) at the ONT/ONU, the OLT Instead of including the channel list(s) at the ONT/ONU, the OLT
or NAS can be programmed with these access lists. Having these or NAS can be programmed with these access lists. Having these
access lists on the ONT/ONU prevents forwarding of unauthorized access lists on the ONT/ONU prevents forwarding of unauthorized
joins to the OLT or NAS, reducing unnecessary control load on joins to the OLT or NAS, reducing unnecessary control load on
these network elements. Similarly, performing the access control these network elements. Similarly, performing the access control
at the OLT instead of the NAS, if not performed on the ONT/ONU, at the OLT instead of the NAS, if not performed on the ONT/ONU,
will reduce unnecessary control load on the NAS. will reduce unnecessary control load on the NAS.
6.2. Multicast Admission Control 6.2. Multicast Admission Control
The successful delivery of Triple Play Broadband services is The successful delivery of Triple Play Broadband services is
quickly becoming a big capacity planning challenge for most of quickly becoming a big capacity planning challenge for most of
the Service Providers nowadays. Solely increasing available the Service Providers nowadays. Solely increasing available
bandwidth is not always practical, cost-economical and/or bandwidth is not always practical, cost-economical and/or
sufficient to satisfy end-user experience given not only the sufficient to satisfy end-user experience given not only the
strict QoS requirements of unicast applications like VoIP and strict QoS requirements of unicast applications like VoIP and
Video on Demand, but also the fast growth of multicast Video on Demand, but also the fast growth of multicast
interactive applications such as "video conferencing", digital interactive applications such as "video conferencing", digital
TV, and digital audio. These applications typically require low TV, and digital audio. These applications typically require low
skipping to change at page 25, line 5 skipping to change at page 25, line 5
based admission control from a policy server. The policy server based admission control from a policy server. The policy server
can in turn interact with the NAS to request the bandwidth for can in turn interact with the NAS to request the bandwidth for
the unicast video flow if it needs to use shared bandwidth with the unicast video flow if it needs to use shared bandwidth with
multicast. If the bandwidth is available, NAS will reserve the multicast. If the bandwidth is available, NAS will reserve the
bandwidth, update the bandwidth pools for subscriber bandwidth, bandwidth, update the bandwidth pools for subscriber bandwidth,
the PON bandwidth, and the bandwidth on the link towards the OLT, the PON bandwidth, and the bandwidth on the link towards the OLT,
and send a response to the policy server, which is propagated and send a response to the policy server, which is propagated
back to the application server to start streaming. Otherwise, the back to the application server to start streaming. Otherwise, the
request is rejected. request is rejected.
+----+ +----+
+---<PON>---------- |ONT |------ HGW +---<PON>---------- |ONT |------ HGW
+ +----+ + +----+
+ +----+ + +----+
+ +--------- |ONT |------ HGW + +--------- |ONT |------ HGW
+----+ +----+ + +----+ +----+ +----+ + +----+
|NAS |---------------| |------<PON> |NAS |---------------| |------<PON>
| |<------------->| | + +-----+ | |<------------->| | + +-----+
+----+ ANCP |OLT | +--------- | |----- HGW +----+ ANCP |OLT | +--------- | |----- HGW
| | | | | | | | | |
| | |<------------------>| ONU |------HGW | | |<------------------>| ONU |------HGW
skipping to change at page 30, line 47 skipping to change at page 30, line 47
|-------------------->| | | |-------------------->| | |
| 7.+========================+ | | | 7.+========================+ | |
| [Update Replication State] | | | [Update Replication State] | |
| +========================+ | | | +========================+ | |
| | 8.Admission-Reply-Pass | | | | 8.Admission-Reply-Pass | |
| |(<Flow,Cust-Port-ID> | | | |(<Flow,Cust-Port-ID> | |
| |----------------------> | | | |----------------------> | |
| | 9.+============+ | | | 9.+============+ |
| | [Update Repl.] | | | [Update Repl.] |
| | [ State ] | | | [ State ] |
| | +============+ | +============+
Figure 9: Interaction between NAS & ANX for Multicast Bandwidth Figure 9: Interaction between NAS & ANX for Multicast Bandwidth
Admission Control in the All-ANCP ANX control model upon success. Admission Control in the All-ANCP ANX control model upon success.
Similar functionality will be required when OMCI is enabled between Similar functionality will be required when OMCI is enabled between
the OLT and ONT/ONU in the ANCP+OMCI ANX control model. In this the OLT and ONT/ONU in the ANCP+OMCI ANX control model. In this
latter case, the OLT will act as ANCP-OMCI gateway. latter case, the OLT will act as ANCP-OMCI gateway.
+----+ +----+
+--------- |ONT |------ HGW +--------- |ONT |------ HGW
+----+ +----+ + +----+ +----+ +----+ + +----+
|NAS |---------------| |------<PON> |NAS |---------------| |------<PON>
skipping to change at page 31, line 28 skipping to change at page 31, line 28
| |(Flow,Customer-Port-ID) | | | |(Flow,Customer-Port-ID) | |
| |<---------------------- | | | |<---------------------- | |
| 2.+===============+ | | | 2.+===============+ | |
| [ Access Ctrl ] | | | [ Access Ctrl ] | |
| [ & PON B/W ] | | | [ & PON B/W ] | |
| [ Admission Ctrl] | | | [ Admission Ctrl] | |
| +===============+ PASS | | | +===============+ PASS | |
|3.Admission-Request | | | |3.Admission-Request | | |
| <Flow,Customer-Port-ID> | | | <Flow,Customer-Port-ID> | |
|<--------------------| | | |<--------------------| | |
4.| | | | 4.+==================+ | | |
+==================+ | | | [Subscriber B/W ] | | |
[Subscriber B/W ] | | | [& OLT link B/W ] | | |
[& OLT link B/W ] | | | [Admission Ctrl ] | | |
[Admission Ctrl ] | | | +==================+FAIL | |
+==================+FAIL | |
| | | | | | | |
|5.Admission-Reply-Fail | | |5.Admission-Reply-Fail | |
|<Flow,Cust-Port-ID> | | | |<Flow,Cust-Port-ID> | | |
|-------------------->| | | |-------------------->| | |
| 6.+==================+ | | | 6.+==================+ | |
| [Release PON B/W ] | | | [Release PON B/W ] | |
| [Remove Repl.State ] | | | [Remove Repl.State ] | |
| +==================+ | | | +==================+ | |
| | 7.Admission-Reply-Fail | | | | 7.Admission-Reply-Fail | |
| |<Flow,Cust-Port-ID> | | | |<Flow,Cust-Port-ID> | |
| |----------------------> | | | |----------------------> | |
| | 8.+============+ | | | 8.+============+ |
| | [Remove Repl.] | | | [Remove Repl.] |
| | [ State ] | | | [ State ] |
| | +============+ | +============+
Figure 10: Interaction between NAS and ANX for Multicast Bandwidth Figure 10: Interaction between NAS and ANX for Multicast Bandwidth
Admission Control in the All-ANCP ANX control model upon failure. Admission Control in the All-ANCP ANX control model upon failure.
Similar functionality will be required when OMCI is enabled between Similar functionality will be required when OMCI is enabled between
the OLT and ONT/ONU in the ANCP+OMCI ANX control model. In this the OLT and ONT/ONU in the ANCP+OMCI ANX control model. In this
latter case, the OLT will act as ANCP-OMCI gateway. latter case, the OLT will act as ANCP-OMCI gateway.
+------------+ 1. VoD Request +------------+ 1. VoD Request
| App. Server|<----------------------------------------------- | App. Server|<-----------------------------------------------
| Server | | Server |
+------------+ +------------+
skipping to change at page 32, line 22 skipping to change at page 32, line 22
|Server | |Server |
+-------+ +-------+
| + | +
|<-|---3. Admission-Request |<-|---3. Admission-Request
| | | |
+ | 8. Admission-Reply + | 8. Admission-Reply
+----+ + +----+ +-----+ +----+ + +----+ +-----+
|NAS |---------------|OLT |------<PON>-------|ONT |---HGW--CPE |NAS |---------------|OLT |------<PON>-------|ONT |---HGW--CPE
| |<------------->| | +-----+ | | |<------------->| | +-----+ |
+----+ ANCP +----+ | | +----+ ANCP +----+ | |
| | | |
4.| | | | 4.| | | |
+=================+ | | | +=================+ | | |
[Subscriber B/W ] | | | [Subscriber B/W ] | | |
[& OLT link B/W ] | | | [& OLT link B/W ] | | |
[Admission Ctrl ] | | | [Admission Ctrl ] | | |
+=================+PASS | | | +=================+PASS | | |
| | | | | | | |
| 5.Admission-Request | | | | 5.Admission-Request | | |
|(Bandwidth,PON-Port-ID) | | |(Bandwidth,PON-Port-ID) | |
|-------------------> | | | |-------------------> | | |
| | | | | | | |
| 6.+===============+ | | | 6.+===============+ | |
| [ PON B/W ] | | | [ PON B/W ] | |
| [ Admission Ctrl] | | | [ Admission Ctrl] | |
| +===============+ PASS | | | +===============+ PASS | |
|7.Admission-Reply | | | |7.Admission-Reply | | |
| <PON-Port-ID> | | | | <PON-Port-ID> | | |
|<------------------- | | | |<------------------- | | |
| | | |
| | | |
Figure 11: Interactions for VoD Bandwidth Admission Control in Figure 11: Interactions for VoD Bandwidth Admission Control in
the All-ANCP ANX control model. Similar functionality will be the All-ANCP ANX control model. Similar functionality will be
required when OMCI is enabled between the OLT and ONT in the required when OMCI is enabled between the OLT and ONT in the
ANCP+OMCI ANX control model. In this latter case, the OLT will ANCP+OMCI ANX control model. In this latter case, the OLT will
act as ANCP-OMCI gateway. act as ANCP-OMCI gateway.
-A third possible approach is where the ANX is assumed to have a -A third possible approach is where the ANX is assumed to have a
full knowledge to make an autonomous decision on admitting or full knowledge to make an autonomous decision on admitting or
rejecting a multicast and a unicast join. With respect to the rejecting a multicast and a unicast join. With respect to the
skipping to change at page 34, line 5 skipping to change at page 33, line 46
video bandwidth. If the OLT rejects the policy server request, it video bandwidth. If the OLT rejects the policy server request, it
will return a reject to the policy server. will return a reject to the policy server.
It should be noted that if the policy server adjacency is with It should be noted that if the policy server adjacency is with
the NAS, the policy server may make the admission request to the the NAS, the policy server may make the admission request to the
NAS. The NAS then sends an ANCP admission request to the OLT on NAS. The NAS then sends an ANCP admission request to the OLT on
behalf of the policy server. The NAS returns an accept or reject to behalf of the policy server. The NAS returns an accept or reject to
the policy server if it gets a reject or accept, respectively, the policy server if it gets a reject or accept, respectively,
from the OLT. from the OLT.
6.3. Multicast Accounting 6.3. Multicast Accounting
It may be desirable to perform accurate per-user or per Access It may be desirable to perform accurate per-user or per Access
Loop time or volume based accounting. In case the ANX is Loop time or volume based accounting. In case the ANX is
performing the traffic replication process, it knows when performing the traffic replication process, it knows when
replication of a multicast flow to a particular Access Port or replication of a multicast flow to a particular Access Port or
user starts and stops. Multicast accounting can be addressed in user starts and stops. Multicast accounting can be addressed in
two ways: two ways:
- ANX keeps track of when replication starts or stops, and - ANX keeps track of when replication starts or stops, and
reports this information to the NAS for further processing. In reports this information to the NAS for further processing. In
this case, ANCP can be used to send the information from the ANX this case, ANCP can be used to send the information from the ANX
skipping to change at page 35, line 5 skipping to change at page 34, line 45
and the ONT/ONU, then for some of the information required by the and the ONT/ONU, then for some of the information required by the
NAS (such as the list of access-ports on which a flow is being NAS (such as the list of access-ports on which a flow is being
forwarded or list of flows being forwarded on an access-port), a forwarded or list of flows being forwarded on an access-port), a
query to the OLT from the NAS will result in a query from OLT to query to the OLT from the NAS will result in a query from OLT to
ONT/ONU. The OLT responds back to the NAS when it receives the ONT/ONU. The OLT responds back to the NAS when it receives the
response from the ONT/ONU. Also, if the list of PONs on which response from the ONT/ONU. Also, if the list of PONs on which
replication is happening for a multicast channel or the list of replication is happening for a multicast channel or the list of
channels being replicated on a PON is what is desired, the OLT channels being replicated on a PON is what is desired, the OLT
can return this information. can return this information.
7. Remote Connectivity Check 7. Remote Connectivity Check
In an end-to-end Ethernet aggregation network, end-to-end In an end-to-end Ethernet aggregation network, end-to-end
Ethernet OAM as specified in IEEE 802.1ag and ITU-T Ethernet OAM as specified in IEEE 802.1ag and ITU-T
Recommendation Y.1730/1731 can provide Access Loop connectivity Recommendation Y.1730/1731 can provide Access Loop connectivity
testing and fault isolation. However, most HGWs do not yet testing and fault isolation. However, most HGWs do not yet
support these standard Ethernet OAM procedures. Also, in a mixed support these standard Ethernet OAM procedures. Also, in a mixed
Ethernet and ATM access network (e.g., Ethernet based aggregation Ethernet and ATM access network (e.g., Ethernet based aggregation
upstream from the OLT, and BPON downstream), interworking upstream from the OLT, and BPON downstream), interworking
functions for end-to-end OAM are not yet standardized or widely functions for end-to-end OAM are not yet standardized or widely
available. Until such mechanisms become standardized and widely available. Until such mechanisms become standardized and widely
skipping to change at page 35, line 28 skipping to change at page 35, line 22
access-loop from the NAS. access-loop from the NAS.
Triggered by a local management interface, the NAS can use the Triggered by a local management interface, the NAS can use the
Access Node Control Mechanism (Control Request Message) to Access Node Control Mechanism (Control Request Message) to
initiate an Access Loop test between Access Node and HGW or initiate an Access Loop test between Access Node and HGW or
ONT/ONU. On reception of the ANCP message, the OLT can trigger ONT/ONU. On reception of the ANCP message, the OLT can trigger
native OAM procedures defined for BPON in [G.983.1] and for GPON native OAM procedures defined for BPON in [G.983.1] and for GPON
in [G.984.1]. The Access Node can send the result of the test to in [G.984.1]. The Access Node can send the result of the test to
the NAS via a Control Response message. the NAS via a Control Response message.
8. Access Topology Discovery 8. Access Topology Discovery
In order to avoid congestion in the network, manage and utilize In order to avoid congestion in the network, manage and utilize
the network resources better, and ensure subscriber fairness, NAS the network resources better, and ensure subscriber fairness, NAS
performs hierarchical shaping and scheduling of the traffic by performs hierarchical shaping and scheduling of the traffic by
modeling different congestion points in the network (such as the modeling different congestion points in the network (such as the
last-mile, access Node uplink, and the access facing port). last-mile, access Node uplink, and the access facing port).
Such mechanisms require that the NAS gains knowledge about the Such mechanisms require that the NAS gains knowledge about the
topology of the access network, the various links being used and topology of the access network, the various links being used and
their respective rates. Some of the information required is their respective rates. Some of the information required is
skipping to change at page 36, line 22 skipping to change at page 36, line 14
control model, and then from OLT to the NAS via ANCP. control model, and then from OLT to the NAS via ANCP.
Additionally, during the time the DSL NT is active, data rate Additionally, during the time the DSL NT is active, data rate
changes can occur due to environmental conditions (the DSL Access changes can occur due to environmental conditions (the DSL Access
Loop can get "out of sync" and can retrain to a lower value, or Loop can get "out of sync" and can retrain to a lower value, or
the DSL Access Loop could use Seamless Rate Adaptation making the the DSL Access Loop could use Seamless Rate Adaptation making the
actual data rate fluctuate while the line is active). In this actual data rate fluctuate while the line is active). In this
case, ANX sends an additional Information Report to the NAS each case, ANX sends an additional Information Report to the NAS each
time the Access Loop attributes change above a threshold value. time the Access Loop attributes change above a threshold value.
Existing DSL procedures are not applicable in this case because Existing DSL procedures are not applicable in this case because
an adapted message flow and additional TLVs are needed. an adapted message flow and additional TLVs are needed.
+--------+ +--------+
| Policy | | Policy |
| Server | | Server | +---+ +---+
+--------+ +---+ +---+ +--------+ +-----------|ONT|---|HGW|
| +-----------|ONT|---|HGW|
| | +---+ +---+ | | +---+ +---+
| +--------------- |-----------------+ | +--------------- |-----------------+
+----+ | +----+ | +-----+ | +---+ +----+ | +----+ | +-----+ | +---+
|NAS |------------ | | | | | |-|-|HGW| |NAS |------------ | | | | | |-|-|HGW|
| |<----------> | | | | |ONT/ | | +---+ | |<----------> | | | | |ONT/ | | +---+
+----+ ANCP | |OLT |------<PON>--------|ONU | | +----+ ANCP | |OLT |------<PON>--------|ONU | |
| | | | | | | +---+ | | | | | | | +---+
| | | |<----------------->| |---|HGW| | | | |<----------------->| |---|HGW|
| | +----+ OMCI +-----+ | +---+ | | +----+ OMCI +-----+ | +---+
| +----------------------------------+ | +----------------------------------+
| | Access Node | | | Access Node |
| | | | | |
| |------GPON Ranging------| | |------GPON Ranging------|
| Port Status Message| ONT Port UP | | Port Status Message| ONT Port UP |
|<------------------ |<-----------------------| |<------------------ |<-----------------------|
|Port Configuration GPON Line/Service Profile| |Port Configuration GPON Line/Service Profile|
|------------------> |<---------------------->| |------------------> |<---------------------->|
| ONT/ONI Port UP| | | ONT/ONI Port UP| |
|<------------------ | | |<------------------ | |
| | |
| ANCP | OMCI | | ANCP | OMCI |
<-------------------><----------------------->| <-------------------><----------------------->|
PPP, DHCP, IP PPP, DHCP, IP
<------------------------------------------------------> <------------------------------------------------------>
Figure 12: Message Flow for the use case of Topology Discovery Figure 12: Message Flow for the use case of Topology Discovery
for the ANCP+OMCI access control model. for the ANCP+OMCI access control model.
Figure 12 depicts a message flow for topology discovery when Figure 12 depicts a message flow for topology discovery when
using the ANCP+OMCI access control model. Basically, when an using the ANCP+OMCI access control model. Basically, when an
ONT/ONU gets connected to a PON, the OLT detects a new device and ONT/ONU gets connected to a PON, the OLT detects a new device and
a GPON Ranging process starts. During this process the ONT/ONU a GPON Ranging process starts. During this process the ONT/ONU
becomes authorized by the OLT and identified by ONT/ONU ID, PON becomes authorized by the OLT and identified by ONT/ONU ID, PON
Port ID and max Bandwidth. This port status is reported via ANCP Port ID and max Bandwidth. This port status is reported via ANCP
to the NAS and then potentially the policy server via another to the NAS and then potentially the policy server via another
skipping to change at page 37, line 18 skipping to change at page 37, line 9
a GPON Ranging process starts. During this process the ONT/ONU a GPON Ranging process starts. During this process the ONT/ONU
becomes authorized by the OLT and identified by ONT/ONU ID, PON becomes authorized by the OLT and identified by ONT/ONU ID, PON
Port ID and max Bandwidth. This port status is reported via ANCP Port ID and max Bandwidth. This port status is reported via ANCP
to the NAS and then potentially the policy server via another to the NAS and then potentially the policy server via another
mechanism that is out of scope of this document. In a second step mechanism that is out of scope of this document. In a second step
after GPON Service profile is assigned from OLT to ONT/ONU, the after GPON Service profile is assigned from OLT to ONT/ONU, the
OLT reports the final status to NAS with information about OLT reports the final status to NAS with information about
service profile and other information such as the ONT/ONU port service profile and other information such as the ONT/ONU port
rate to the subscriber for instance. rate to the subscriber for instance.
9. Access Loop Configuration 9. Access Loop Configuration
Topology Discovery reports access port identification to NAS when Topology Discovery reports access port identification to NAS when
sending an Access Port Discovery message. This informs NAS sending an Access Port Discovery message. This informs NAS
identification of PON port on an Access Node. Based on Access identification of PON port on an Access Node. Based on Access
Port Identification and on customer identification, service Port Identification and on customer identification, service
related parameters could be configured on an OLT and an ONU/ONT. related parameters could be configured on an OLT and an ONU/ONT.
Service related parameters could be sent to OLT via ANCP before Service related parameters could be sent to OLT via ANCP before
or after an ONU/ONT is up. Sending of ANCP loop Configuration or after an ONU/ONT is up. Sending of ANCP loop Configuration
messages from NAS can be triggered by a management system or by messages from NAS can be triggered by a management system or by
skipping to change at page 37, line 42 skipping to change at page 37, line 33
ID, S-VLAN ID, and service bandwidth. ID, S-VLAN ID, and service bandwidth.
Parameters of UNI (subscriber interface to HGW/CPE) of ONU/ONT Parameters of UNI (subscriber interface to HGW/CPE) of ONU/ONT
can also be configured via ANCP. When the ONU/ONT supports ANCP, can also be configured via ANCP. When the ONU/ONT supports ANCP,
parameters of the UNI on ONU/ONT are sent to the ONU/ONT via parameters of the UNI on ONU/ONT are sent to the ONU/ONT via
ANCP. If the ONU/ONT does not support ANCP, but only OMCI, ANCP. If the ONU/ONT does not support ANCP, but only OMCI,
parameters have to be sent from the NAS to the OLT via ANCP parameters have to be sent from the NAS to the OLT via ANCP
first. Then, the OLT translates such configuration into OMCI and first. Then, the OLT translates such configuration into OMCI and
sends it to the ONU/ONT. sends it to the ONU/ONT.
10. Security Considerations 10. Security Considerations
[RFC5713] lists the ANCP related security threats that could be [RFC5713] lists the ANCP related security threats that could be
encountered on the Access Node and the NAS. It develops a threat encountered on the Access Node and the NAS. It develops a threat
model for ANCP security, and lists the security functions that model for ANCP security, and lists the security functions that
are required at the ANCP level. are required at the ANCP level.
With Multicast handling as described in this document, ANCP With Multicast handling as described in this document, ANCP
protocol activity between the ANX and the NAS is triggered by protocol activity between the ANX and the NAS is triggered by
join/leave requests coming from the end-user equipment. This join/leave requests coming from the end-user equipment. This
could potentially be used for denial of service attack against could potentially be used for denial of service attack against
skipping to change at page 38, line 20 skipping to change at page 38, line 11
To mitigate this risk, the NAS and ANX may implement control To mitigate this risk, the NAS and ANX may implement control
plane protection mechanisms such as limiting the number of plane protection mechanisms such as limiting the number of
multicast flows a given user can simultaneously join, or limiting multicast flows a given user can simultaneously join, or limiting
the maximum rate of join/leave from a given user. the maximum rate of join/leave from a given user.
Protection against invalid or unsubscribed flows can be deployed Protection against invalid or unsubscribed flows can be deployed
via provisioning black lists as close to the subscriber as via provisioning black lists as close to the subscriber as
possible (e.g., in the ONT). possible (e.g., in the ONT).
11. Differences in ANCP applicability between DSL and PON 11. Differences in ANCP applicability between DSL and PON
As it currently stands, both ANCP framework [RFC5851] and As it currently stands, both ANCP framework [RFC5851] and
protocol [RFC6320] are defined in context of DSL access. Due to protocol [RFC6320] are defined in context of DSL access. Due to
inherent differences between PON and DSL access technologies, inherent differences between PON and DSL access technologies,
ANCP needs a few extensions for supporting the use-cases outlined ANCP needs a few extensions for supporting the use-cases outlined
in this document for PON based access. These specific differences in this document for PON based access. These specific differences
and extensions are outlined below. and extensions are outlined below.
- In PON, the access-node functionality is split between OLT and - In PON, the access-node functionality is split between OLT and
ONT. Therefore, ANCP interaction between NAS and AN translates to ONT. Therefore, ANCP interaction between NAS and AN translates to
skipping to change at page 40, line 7 skipping to change at page 39, line 44
based on the set of access-ports indicated by the NAS. based on the set of access-ports indicated by the NAS.
- For reporting purposes, ANCP must enable the NAS to query the - For reporting purposes, ANCP must enable the NAS to query the
OLT for channels replicated on a PON or a list of PONs and to OLT for channels replicated on a PON or a list of PONs and to
specific access ports. The latter should trigger the OLT to query specific access ports. The latter should trigger the OLT to query
the ONT for a list of channels being replicated on all access the ONT for a list of channels being replicated on all access
ports or on specific access ports to the premises. In DSL case, ports or on specific access ports to the premises. In DSL case,
it is sufficient to query the DSLAM for a list of channels being it is sufficient to query the DSLAM for a list of channels being
replicated on an access port or a list of access ports. replicated on an access port or a list of access ports.
12. ANCP versus OMCI between the OLT and ONT/ONU 12. ANCP versus OMCI between the OLT and ONT/ONU
ONT Management and Control Interface (OMCI) [OMCI] is specified ONT Management and Control Interface (OMCI) [OMCI] is specified
for in-band ONT management via the OLT. This includes configuring for in-band ONT management via the OLT. This includes configuring
parameters on the ONT/ONU. Such configuration can include adding parameters on the ONT/ONU. Such configuration can include adding
an access port on the ONT to a multicast tree and the ONT to a an access port on the ONT to a multicast tree and the ONT to a
multicast tree. Thus, OMCI can be a potential replacement for multicast tree. Thus, OMCI can be a potential replacement for
ANCP between the OLT and ONT/ONU, albeit it may not a be suitable ANCP between the OLT and ONT/ONU, albeit it may not a be suitable
protocol for dynamic transactions as required for the multicast protocol for dynamic transactions as required for the multicast
application. application.
skipping to change at page 40, line 38 skipping to change at page 40, line 28
on the implementation may require a different address. Sharing on the implementation may require a different address. Sharing
the same IP address between VoIP and ANCP may have other network the same IP address between VoIP and ANCP may have other network
implications on traffic routing. Using a separate IP address for implications on traffic routing. Using a separate IP address for
the purpose of ONT/ONU management or ANCP specifically may often the purpose of ONT/ONU management or ANCP specifically may often
be required when supporting ANCP. These considerations may favor be required when supporting ANCP. These considerations may favor
OMCI in certain environments. However, OMCI will not allow some OMCI in certain environments. However, OMCI will not allow some
of the transactions required in approach 2, where the ONT/ONU of the transactions required in approach 2, where the ONT/ONU
sends unsolicited requests to the OLT rather than being queried or sends unsolicited requests to the OLT rather than being queried or
configured by OLT requests. configured by OLT requests.
13. IANA Considerations 13. IANA Consideration
This document does not require actions by IANA. This document does not require actions by IANA.
14. Acknowledgements 14. Acknowledgements
The authors are thanksful to Rajesh Yadav and Francois Le The authors are thanksful to Rajesh Yadav and Francois Le
Faucheur for valuable comments and discussions. Faucheur for valuable comments and discussions.
15. References 15. References
15.1. Normative References 15.1. Normative References
[RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, [RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone,
D., and R. Wheeler, "A Method for Transmitting PPP Over D., and R. Wheeler, "A Method for Transmitting PPP Over
Ethernet (PPPoE)", RFC 2516, February 1999. Ethernet (PPPoE)", RFC 2516, February 1999.
[RFC2684] Grossman, D. and J. Heinanen, "Multiprotocol [RFC2684] Grossman, D. and J. Heinanen, "Multiprotocol
Encapsulation over ATM Adaptation Layer 5", RFC 2684, September Encapsulation over ATM Adaptation Layer 5", RFC 2684, September
1999. 1999.
15.2. Informative References 15.2. Informative References
[RFC2881] Mitton, D. and M. Beadles, "Network Access Server [RFC2881] Mitton, D. and M. Beadles, "Network Access Server
Requirements Next Generation (NASREQNG) NAS Model", RFC 2881, Jul Requirements Next Generation (NASREQNG) NAS Model", RFC 2881, Jul
2000. 2000.
[RFC5851] Ooghe, S., et al., "Framework and Requirements [RFC5851] Ooghe, S., et al., "Framework and Requirements
for Access Node Control Mechanism in Broadband Networks", RFC for Access Node Control Mechanism in Broadband Networks", RFC
5851, May 2010. 5851, May 2010.
[G.983.1] ITU-T recommendation G.983.1, Broadband optical access [G.983.1] ITU-T recommendation G.983.1, Broadband optical access
skipping to change at page 42, line 18 skipping to change at page 41, line 45
[RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder, [RFC5713] Moustafa, H., Tschofenig, H., and S. De Cnodder,
"Security Threats and Security Requirements for the Access Node "Security Threats and Security Requirements for the Access Node
Control Protocol (ANCP)", RFC 5713, January 2010. Control Protocol (ANCP)", RFC 5713, January 2010.
[OMCI] ITU-T recommendation G.984.4 GPON ONT Management and [OMCI] ITU-T recommendation G.984.4 GPON ONT Management and
Control Interface (OMCI) Specifications. Control Interface (OMCI) Specifications.
[RFC6320] Taylor, T., et al, "Protocol for Access Node Control [RFC6320] Taylor, T., et al, "Protocol for Access Node Control
Mechanism in Broadband Networks", RFC 6320, October 2011. Mechanism in Broadband Networks", RFC 6320, October 2011.
Authors' Addresses Authors' Addresses
Nabil Bitar Nabil Bitar
Verizon Verizon
60 Sylvan Road 60 Sylvan Road
Waltham, MA 02451 Waltham, MA 02451
Email: nabil.n.bitar@verizon.com Email: nabil.n.bitar@verizon.com
Sanjay Wadhwa Sanjay Wadhwa
Alcatel-Lucent Alcatel-Lucent
701 East Middlefield Road 701 East Middlefield Road
 End of changes. 59 change blocks. 
108 lines changed or deleted 89 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/