3HH-00057-2280-DFZZA-01P04-ISAM R4 - 2 - 02 Workshop - Data

R4.2.
02 CFT workshop
Dec 2010
Wendy Michiels
All Rights Reserved © Alcatel-Lucent 2007,

Agenda
1) ALU00123396 : IPv6 anti-spoofing on FD
2) ALU00123522/ALU00123524 : IPv6 ICMPv6 transparency and

ND agent on FD
3) ALU00722116 : Lawful Intercept on IPv6
4) ALU00123653 : License management for IPv6 security
5) ALU00123507/ALU00123548 : IPv6 on GPON and CATAN LT’s
6) ALU00123529 : vMAC on NGLT-A
7) ALU00123588 : PON feeder protection
8) ALU00123660 : NGLT-A/B scaling
9) ALU00123599 : OLT/OMCI/ONT support for TR-69
CFT Workshop R4.2.02 - 2 All Rights Reserved © Alcatel-Lucent 2010,

Agenda
10) ALU00500716/ALU00500724/ALU00500726/ALU00505245/
ALU00747313 : OMCI
11) ALU00123542 : LT backplane load sharing towards NT
12) ALU00123538 : Operator with RAD VSA and def prof
13) ALU00123705 : NELT-B phase 2
14) ALU00274393 : MAC address overbooking on CATE/CATAN
15) ALU00298179/ALU00303766 : Support overlapping

multicast group IP@: Fixed multicast VLAN per IGMP channel
16) ALU00305702 : Increase number of multicast VLANs to 64
17) ALU00467870 : PIM-SSM : ASM to SSM translation per SAP
18) ALU00421300 : Porting of 2.5G REM capabilities from

R4.1.03

Agenda
19) ALU00426579 : IEEE1588 slave on NANT-E
20) ALU00719661/ALU00808506 : IPv6 on NANT-E (trident+)
21) ALU00811527 : Relay Tag Circuit Id / Remote Id

Configuration - VF Germany
22) ALU00121718/ALU00123597 : Ethernet OAM support (ph1)
23) ALU00123702 : License key for Cross talk cancellation
24) ALU00761457 : DTAG SNMP Conformity of R4.2 MIBs
25) ALU00747163 : Demo for RAC on 1st mile for unicast

applications
26) ALU00500716/ALU00500724/ALU00500726/
ALU00505245/ALU00747313 : OMCIv1

1
ALU00123396 : IPv6 antispoofing on FD

IPv6 FD document 3HH-03825-AAAA-FDZZA

Author Sven Ooghe, feature PLM
IPv6 address anti-spoofing is similar to IPv4 anti-spoofing. The ISAM discards in

upstream direction any IPv6 packets whose IPv6 source address does not
match any IPv6 addresses or prefixes allocated to the user interface. The
ISAM will only check the first 64 bits of the 128-bit IPv6 address.
Restriction:
- Only for dynamically learned IPv6 addresses through DHCPv6
- Not for IPv6 prefixes learned through SLAAC, where prefixes are forwarded in
the DS via RA messages
- Not for statically configured IPv6 addresses

CLI:
----configure
----vlan
----id
----secure-forwarding
Feature binder: 3HH-08216-AAAA-ADZZA

2
ALU00123522/ALU00123524 : IPv6 ICMPv6
transparency and ND agent on FD

ALU00123522 : IPv6 ICMPv6 transparency and ND agent on FD

In general: ICMPv6 messages are allowed to be forwarded, following the MAC

forwarding rules
On top:
(1) NGLT-A: IPv6 MC control flag
ICMPv6 multicast forwarding is additionally controlled by the IPv6MC flag.
When disabled, all Ipv6 multicast packets are dropped
(2) ICMPv6 security flag:
When enabled, some ICMPv6 messages are dropped for security reasons
(3) vMAC:
When enabled, some ICMPv6 messages need to be manipulated.
Downstream: user MAC@ replaced by vMAC@, Upstream: vMAC@ replaced by
user MAC@ + additional processing inside the ICMP message

VLAN CrossConnect
ICMPv6 filtering disabled ICMPv6 filtering enabled
Upstream Downstream Upstream Downstream
unicast multicast unicast multicast Unicast multicast unicast multicast
NS vMAC vMAC NS vMAC vMAC
NA vMAC vMAC NA vMAC vMAC
RS vMAC vMAC RS vMAC vMAC
RA RA
Redirect Redirect
MLD MLD
Other Other

i-bridge vlan, IPv6MC flag enabled
Unicast multicast unicast multicast Unicast multicast unicast multicast
NS vMAC vMAC NS vMAC vMAC
NA vMAC vMAC NA vMAC vMAC
RS vMAC vMAC RS vMAC vMAC
RA RA
Redirect Redirect
MLD MLD
Other Other

i-bridge vlan, IPv6MC flag disabled
unicast multicast unicast multicast Unicast multicast unicast multicast
NS vMAC NS vMAC
NA vMAC NA vMAC
RS vMAC RS vMAC
RA RA
Redirect Redirect
MLD MLD
Other Other

CLI:
----configure
----vlan
----id
----ipv6-mcast-ctrl
----icmpv6-sec-fltr
----vmac-translation

3
ALU00722116 : Lawful Intercept on IPv6

ALU00722116 : Lawful Intercept on IPv6
Lawful intercept FD document 3HH-03821-AAAA-FDZZA
Reference: Lawful intercept on IPv4: ALU00124460 (R4.2)

presentation RCR: 3HH-00057-2270-DFZZA

4
ALU00123653 : License management for IPv6
security

ALU00123653 : License management for IPv6 security

The ISAM must count the number of access lines (DSL, Ethernet or ONT UNI)
where one or more IPv6 security features are activated, and store this
information in a “license counter”. This allows the ISAM Element Manager to
limit the maximum amount of IPv6 users according to the installed license.
(specific for IPv6!!)
Counter increases when:

- IPv6 anti-spoofing is enabled
- ICMPv6 (ND+MLD) filtering is enabled
- Lightweight DHCPv6 Relay Agent is enabled

ALU00123653 : License management for IPv6 security
leg:isadmin># show system license
================================================================================
license table
================================================================================
feature |number-license
-----------------+--------------------------------------------------------------
adsl2-plus 0
readsl2 0
igmp 0
annex-m 0
ip-forward 0
pppox-relay 0
802dot1x 0
ipoa-cc/rb 0
upbo-policing 0
xdslline-overrule 0
xdsl-ins 0
adsl-adsl2-dpbo 0
annex-j 0
synce-if-timing 0
2dot5gbps-lt 0
redcy 0
shdsl-ctc 0
vdsl2 0
arq 0
10gbps-lt 0
20gbps-lt 0
ipv6-security 0
lawful-intercept 0
--------------------------------------------------------------------------------
license count : 23
================================================================================

5
ALU00123507/ALU00123548 : IPv6 on GPON and
CATAN LT’s

ALU00123507/ALU00123548 : IPv6 on GPON and CATAN LT’s

GPON LT: NGLT-A

CATAN LT’s: NVLT-M/N, NVLS-A, NELT-B (UNI mode only!)
=> Feature binder: 3HH-08558-AAAA-ADZZA
IPv6 features [R4.2 + R4.2.02]:

- DHCPv6
- IPv6 antispoofing
- ICMPv6 transparency
- ICMPv6 filtering
- vMAC
-…

6
ALU00123529 : vMAC on NGLT-A

Architecture overview 3HH-09127-AGAA-DFZZA

Author Lucien Marcotte, product architect
- In R4.2: preparations were done: DSLAM-Id (configure vlan vmac-address-format)

- DSLAM-Id: max value: 8K required to accommodate GPON needs (extra bits
to identify the UNI)
- Limitation introduced for DSL boards
- NGLT-A: no vmac support yet
- In R4.2.02: final implementation:
- Limitation of DSLAM-Id was removed again for DSL (allowed max value:
512K)
- For GPON: max value: 64K
- Operator’s responsibility: when GPON and DSL in same DSLAM: choose
DSLAM-Id  64K

47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
R 4.0 DSL
R 4.2 DSL
R 4.2.02a DSL
R 4.2.02a GPON
47…45 Rack Id [0…7] 47…45 DSLAM Id part1 – Total [0… 65536]

44 DSL / PON flag (0 : DSL) 44 DSL / PON flag (1 : PON)
Application tag 43…42 Application tag
 00 : vMAC
41 U/L field (1 : local MAC@ validity)
43…42  01 : Reserved for future use
 10 : 802.1ag CFM (ISAM Port MAC@) 40 I/G field (0 : unicast MAC@)
 11 : 802.1ag CFM (CPE MAC@ discovery) GPON 39…27 DSLAM Id part2 – Total [0… 65536]
DSL – Ethernet pt-to-pt
41 U/L field (1 : local MAC@ validity)

26…22 Slot Id [0…31]
40 I/G field (0 : unicast MAC@)
21…18 PON Port Id [0…15]
DSLAM Id [0… 524287]
39…21 17…8 Port Id (UNI) [0…1023]
Limited to [0…8191] in R42 … R42.02
20…15 Slot Id [0…63] 7 Reserved (0)
14…6 Port Id [0…511]

6…0 Mac Id [0…127]
7
ALU00123588 : PON feeder protection

Des
cop
ALU00123588 : PON feeder protection e d fr
om
R 42
Architecture overview 3HH-08989-AGAA-DFZZA 02
Author Julia Ferguson
Requirement:
- Optical protection mechanism on PON level -> if PONLOSS on the active PON,
then switch-over takes place to the stand-by PON
- Requirement/implementation taken over from FTTU
- On NGLT-A: fixed PON protection pairs: 1&2, 3&4, 5&6, 7&8

GPON LT / ONT
NT ONT
PON 1
PON 2 2xN
PON 3
PON 4
ONT
NGLT
PON 5
PON 6
PON 7
PON 8

No CLI support
TL1 support (already in R4010 but not supported yet):
ENT-PONPROTN:[tid]:aid_pon:[ctag]:::ponprotn_nblk[:];
DLT-PONPROTN:[tid]:aid_pon:[ctag][:];
RTRV-PONPROTN:[tid]:aid_pon:[ctag][:];
REPT-OPSTAT-PONPROTN:[tid]:aid_pon:[ctag][:];
SW-DX-PON:[tid]:aid_dxpon:[ctag]::[dirn][,];

8
ALU00123660 : NGLT-A/B scaling

ALU00123660 : NGLT-A/B scaling

Author Michael TODD, Sujeeth DHARANIKOTA
Converged platform dimensioning document: 3HH-08154-3004-DFZZA

Author Johan Verkinderen
Requirement:
- Increase max number of UNI per LT to 4096 (8 * 512)
- Accordingly increase max number of (UNI level) DS shapers to 4096

9
ALU00123599 : OLT/OMCI/ONT support for TR-
69

ALU00123599 : OLT/OMCI/ONT support for TR-69

Author Rick RZONCA, PLM
TR-69:
- Defines application layer for the remote management of end-user devices
OLT impact:
- Creation of VEIP (Virtual Ethernet Interface Point)
- OLT manages the VEIP via OMCI and terminate VLANs on it as it would for any
other UNI it might normally manage
- VEIPs will be managed as other UNIs and will be created with ONTCARD
creation and a VEIP card type. Up to 16 VEIPs on a card, but it is expected
that it will normally be configured with one or two

ALU00123599 : OLT/OMCI/ONT support for TR-69
CLI/TL1 impact:
ToDo: mail sent to Rick Rzonca

11
ALU00123542 : LT backplane load sharing
towards NT

ALU00123542 : LT backplane load sharing towards NT

Author Rob Parsons, PLM
NGLT-A: 3HH-08811-AKAA-DFZZA
Backplane bandwidth must be doubled:

 NANT-D enables 2.5Gbps per LT => LT load sharing with 2xNANT-D enables
5Gbps per LT
 NANT-E enables 10Gbps per LT => LT load sharing with 2xNANT-E enables
20Gbps per LT
When NT gets in redundancy mode, both NT and LT load sharing are enabled
automatically, i.e. the LT will automatically go to the highest capacity
possible - non configurable

ALU00123542 : LT backplane load sharing towards NT
Full Load Sharing with NTIO
Applicable NT’s: NANT-D and NANT-E

NT I/O
Applicable LT’s: NGLT-A/B and NELT-B
R1
NT
LT Internal static LAG (from NT’s perspective) – Link
from standby removed from LAG. In the event
NT R2 of switchover. Old active link removed and new
active link added
Internal static LAG (from NT’s perspective)

Data Plane traffic
Full Load Sharing without NTIO
–.Operates as normal LAG with both links

included in LAG. Failed links will be removed
from LAG..
NT R1 LT’s perspective: Add/remove links from LT LAG

based on link state and active NT signal
LT
NT R2 DS traffic: NT uses hashing algorithm
US traffic: LT uses hashing algorithm

12
ALU00123538 : Operator with RAD VSA
and def prof

ALU00123538 : Operator with RAD VSA and def prof
FD Management & Troubleshooting: 3HH-03848-AAAA-FDZZA
The RADIUS proxy/server checks the user name and password and returns, in
case of an ACCESS_ACCEPT, the operator privilege levels (= authorization),
the prompt, the password timeout value and a description, as been specified
by the administrator before. All this information is returned using Vendor
Specific Attributes (VSA), as specified by the RADIUS protocol (RFC 2865).
From R4.2.02 onwards, when doing operator authentication using Radius, all
parameters not retrieved from the Radius server, are automatically set using
the values as specified in the default operator profile. (before R4.2.02 -> SW
hardcoded values were used)

13
ALU00123705 : NELT-B phase 2

FD: 3HH-08150-3020-DFZZA
Phase 1: R4.2 => ALU00123441

UNI NNI
vMAC 4.2 NA
PPPoE relay with MAC@ concentration 4.2 NA
IGMP 4.2 4.2
Multicast in one vlan 4.2 4.2
Multicast cross vlan 4.2 NA
IP anti-spoofing / ARP relay 4.2 NA
MAC movement and Dup MAC control 4.2 4.2
802.1x 4.2.02 NA
DHCP relay 4.2 NA
PPPoE relay agent 4.2 NA
ARP port 4.2 NA
LACP 4.2.02 4.2.02
RSTP NA 4.2.02
802.3ah OAM 4.2.02 4.3
802.1ag CFM (UNI/NNI efficient extraction) 4.2.02 4.2.02
C-VLAN CC 4.2 4.2
C-VLAN iBridge 4.2 4.2
S+C VLAN CC 4.2 4.2.02

S VLAN Tunnel 4.2 4.2.02

S-iBridge 4.3? 4.2
VLAN translation 4.2 4.3
N:1 VLAN Translation 4.2.02 4.3
UNI L2 classification
VLAN 4.2 NA
VLAN + Pbits 4.2.02 NA
Pbits 4.2.02 NA
CCL 4.2.02 NA
UNI L3 classification
DSCP 4.2.02 NA
CCL 4.2.02 NA
NNI QoS
Trusted NA 4.2
Remark P-bit NA 4.2.02
S-Tag option 1 NA 4.2.02
S-Tag option 2 NA 4.2.02
option 1) trusted = Copy [C-tag] p-bit to [S-tag] p-bits
option 2) translate = Incoming [C-tag] p-bit to [S-tag] p-bits

(One translation per BridgePort)
ISAM 7356 SW support the NELT-B in the master slot 4.2.02 4.2.02
Auto Power protection on SFP 4.2 4.2

14
ALU00274393 : MAC address overbooking
on CATE/CATAN

ALU00274393 : MAC address overbooking on CATE/CATAN
Architecture overview 3HH-03716-0476-DFZZA
Ported feature now on CATE/CATAN LT‘s
Purpose:
 Allow occasional overbooking of the MAC FDB table per bridge port
Solution:
 Introduce a new parameter “committed number of MAC addresses” per bridge
port (configure bridge port <port> max-committed-mac
<number>)
 This parameter is checked against the DSL line and LT-level budget
 Extra MAC addresses, above the committed value, are learnt on a best-effort
basis so without any guarantee
 If new MAC@ comes in for a bridge port where committed value is not
reached, and DSL line and LT limits are reached, then a MAC@ will be
removed from a bridge port with a FDB table size exceeding committed value

15
ALU00298179/ALU00303766 : Support
overlapping multicast group IP@: Fixed
multicast VLAN per IGMP channel

ALU00298179/ALU00303766 : Support overlapping multicast group IP@:
Fixed multicast VLAN per IGMP channel
FD Video Services 3HH-03803-AAAA-FDZZA
Main customers NBN, FT
Background:
 SSM (IGMPv3) is solution today for wholesaling where different video
service/content providers coexist in same network
 But what if different service providers, offering the same broadband
channels, get their content from the same content provider who will use the
same src ip address?
Solution:
 It must be possible to configure per end-user IGMP channel what is the
associated multicast VLAN. In this way a direct link is made between the end-
user and his Video Service Provider.

In practice:
 A system-wide parameter VlanSelection is introduced to select the

wholesale approach -> via SSM or based on mcast vlan
 configure igmp system vlanSelection

 If VlanSelection is false (default), then fixed mcast vlan is ignored and pre-
configured streams must have unique [Group address,Source address]
 If VlanSelection is true, then fixed mcast vlan is considered and used for joining
video streams..
 configure igmp channel xxx mcastVlanid
 configuring mcast streams:
 [Group address,Source address] must not be unique, as long as the
associated vlan is different
 configure mcast chnl

ONT:
 Needs to know for which VLAN they need to take the mcast stream from the
mcast gemport
 OLT informs the ONT about the VLAN
 !! ALU proprietary: only when lt-ont-signaling enabled
 ALU ONT: I-240G-B => OK

 CIG ONT: I-010G-P, I-010G-R => committed, current plan (full scope): June
2011

16
ALU00305702 : Increase number of
multicast VLANs to 64

ALU00305702 : Increase number of multicast VLANs to 64
Main customer: NBN
As the number of video Service Providers in the NBN network could grow up to
64, the number of multicast VLANs in ISAM must be increased to 64.
Note that NBN Co will make use of configured multicast channels in order to
enable CAC for Video on the 1st mile. The current number of multicast VLANs
for configured channels is 16.

17
ALU00467870 : PIM-SSM : ASM to SSM
translation per SAP

ALU00467870 : PIM-SSM : ASM to SSM translation per SAP
Main customer: FT
Background:
 If PIM-SSM is configured on iHUB, then it needs to come up with a source ip
address before sending it to the network, in case there was no source ip
address yet in the IGMP join coming from the LT. As there can be several
service providers in the network, it is not enough to configure a global source
ip address for a range of mcast group addresses.
Solution:
 On the IHUB it must be possible to configure ASM to SSM translation per
multicast VLAN / SAP. This allows to assign the right source IP@ S to (*,G)
IGMP JOINs belonging to a given multicast VLAN (end hence Video Service
Provider)
 Related RCR: ALU00298179 : Support overlapping multicast group IP@: Fixed
multicast VLAN per IGMP channel

ALU00467870 : PIM-SSM : ASM to SSM translation per SAP
CLI
 configure router igmp interface xxx ssm-translate

18
ALU00421300 : Porting of 2.5G REM
capabilities from R4.1.03

ALU00421300 : Porting of 2.5G REM capabilities from R4.1.03
Main customer: Telecom Austria
Impact:
 NRCD-x card
 SFP’s
Intention:
 Support all the 2.5G boards from R42 and before
 NVLT-G/H/M (R4.1.03)
 NVLS-A/NVLT-P/NVLT-Q/NVLT-N: R4.2
 NELT-B
 NGLT-A/B
 Commercial case: VDSL2, fibre (P2P) deployment
 Complete presentation: 3HH-00057-5038-DFZZA

19
ALU00426579 : IEEE1588 slave on NANT-E

Des
cop
ALU00426579 : IEEE1588 slave on NANT-E e d fr
om
R 42
Main customer: DT, FT, VF 02
IEEE1588:
Standard that describes the PTP (Precision Time Protocol) making it possible to
synchronise distributed clocks with an accuracy of less than 1 microsecond.
Synchronization and management of a PTP system is achieved through the
exchange of messages (mulicast messaging, both IPv4, IPv6)

20
ALU00719661/ALU00808506 : IPv6 on
NANT-E (trident+)

ALU00719661/ALU00808506 : IPv6 on NANT-E (trident+)

Test only RCR - Impact:

 IPv6 regression testing
 Special focus on ACL’s because implementation on NANT-E is different than
on NANT-D for the ingress filtering
Main customer: FT

21
ALU00811527 : Relay Tag Circuit Id / Remote Id
Configuration - VF Germany

ALU00811527 : Relay Tag Circuit Id / Remote Id Configuration -
VF Germany
In Vodafone Germany, while constructing the relay tag for circuit id in the
upstream, for untagged frames, the customer requests to not include the
default VLAN-id (PVID) in the circuit id construct and expects the VLAN-id
only in case of tagged frames.
configure system loop-id-syntax <with VLAN>
Main customer: VF

22
ALU00121718/ALU00123597 : Ethernet
OAM support (ph1)

ALU00121718/ALU00123597 : ODM ONT Ethernet OAM support
(ph1)
Architecture document (ONT): 8DM-20911-0005-DRZZA
Architecture document (OLT): 3HH-09304-AGAA-DFZZA
Requirement
 Customer expects a minimum acceptable set of features for IEEE802.1ag CFM & ITU-T
Y.1731 protocols to perform Ethernet fault and performance management activities
 Customer expects CFM support in GPON ONTs
Impact
 Extension of the existing implementation to the NGLT cards
 Configuration and retrieval using CLI, TL1 and SNMP
 Configuration of Down MEP on a ONT UNI
 OLT support for Up- MEP, Down- MEP , MIP per UNI per VLAN
 CFM in C-CC, S+C CC, S-Tunnel CC forwarding models
 iBridge VLAN support for VoIP UNI only
 CFM Stack table Support for ONT

ALU00121718/ALU00123597 : ODM ONT Ethernet OAM support
(ph1)
Some background on existing CFM support:

 Continuity check (CCM), Link Trace (LTM/LTR) “traceroute”, Loop Back
(LBM/LBR) “ping”
 Support exists in sending replies LTR/LBR
 No initiation of CCM/LTM/LBM
CLI commands:
configure cfm domain (domain-index)
configure cfm domain (domain-index) association (association-index)
configure cfm domain (domain-index) association (association-index) mep
(mepid)
Main customer: NBN

23
ALU00123702 : License key for Cross talk
cancellation

ALU00123702 : License key for Cross talk cancellation
Architecture document: 3HH-09567-AGAA-DFZZA
FD SHDSL: 3HH-03832-AAAA-FDZZA
Pay fee for CTC

 If the customer require CTC feature, he will pay the additional fee for all
lines
 CDE record which customer need CTC
 When the CDE undefined customer enable CTC, it will be rejected
 The counter of license key “shdsl ctc” always return zero

ALU00123702 : License key for Cross talk cancellation
AccessOperatorName___OprName AccessOperatorId___OperId
VF_Spain 133
VF_Qatar 204
VF_Germany 217
VF_Egypt 270
VF_Portugal 289

24
ALU00761457 : DTAG SNMP Conformity of
R4.2 MIBs

ALU00761457 : DTAG SNMP Conformity of R4.2 MIBs
In order to pass the DTAG EMP tests, the R4.2 MIBs needs to pass the
conformity checks performed by DTAG prior to their OSS integration.
For the MSAN project this activity was already performed in R4.1
Specifically, the following is required

- run the SimpleTester to check for any errors on the NGLT-A related MIBs
- for all errors that are detected, created the corresponding FRs, and resolve
them in R4.2
The tests need to be performed for R4.2 as well as R4.2.02. Note that moving
forward, SimpleTester conformance testing will become a generic part of
release level testing.

25
ALU00747163 : Demo for RAC on 1st mile
for unicast applications

ALU00747163 : Demo for RAC on 1st mile for unicast
R4.
applications 4
Architecture document: 3HH-08261-AGAA-DFZZA
Contact: Luc Gijselinck, Ludwig Pauwels
Background:
There is need for Resource Admission Control (RAC) on the 1st mile for unicast Video and
BTV together.
(today: only RAC for MCAST traffic via CAC profile)
Solution:
 For every session, ISAM sets up diameter session
 Existing CAC algorithm to be extended
 For unicast video traffic, video server can send RAC requests towards ISAM
 For multicast
R4202:
 Demo implementation for KPN
 Corresponding CLI commands hidden in official R4202 builds

R4.
applications 4
DIAMETER Rx interface
5750 SSC
AAA
Server
DIAMETER Gxr interface

DIAMETER Gxe interface
MiViewTV
STB 1 IGMP
Home
STB 2 Gateway 7302/7330 ISAM 7450 ESS 7750 SR
7342 FTTU
Application
signaling (e.g. RTSP)

R4.
applications 4
Set-Top Box Access Node Resource Manager Video Server
IGMP report (join)

Channel zap
IGMP leave
Channel zap IGMP report
…
VoD_Session_Request
RAC_Request
RAC_Request
RAC_Accept
RAC_Accept
VoD_Session_Accept Start VoD

Stream
VoD_Session_Play
VoD Stream Stop VoD

VoD
Stream
session
VoD_Session_Stop
VoD_Session_Release
RAC_Release
RAC_Release

26
ALU00500716/ALU00500724/
ALU00500726/
ALU00505245/ALU00747313 : OMCIv1

ALU00500716/ALU00500724/ALU00500726/
ALU00505245/ALU00747313 : OMCIv1
No info available
Reference in RCR => 3HH-08803-AGAA-DFZZA
3HH-08803-AGAA-DFZZA deals specifically with arch for OISGv2 (ALU00182138)

arch which was moved to 4.2.02.
The completion of the OISGv1 was part of 4.2.

www.alcatel-lucent.com

3HH-00057-2280-DFZZA-01P04-ISAM R4 - 2 - 02 Workshop - Data

Uploaded by

Copyright:

Available Formats

You might also like

3HH-00057-2280-DFZZA-01P04-ISAM R4 - 2 - 02 Workshop - Data

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3HH-00057-2280-DFZZA-01P04-ISAM R4 - 2 - 02 Workshop - Data

Uploaded by

Copyright:

Available Formats

R4.2.

All Rights Reserved © Alcatel-Lucent 2007,

2) ALU00123522/ALU00123524 : IPv6 ICMPv6 transparency and

3) ALU00722116 : Lawful Intercept on IPv6

4) ALU00123653 : License management for IPv6 security

5) ALU00123507/ALU00123548 : IPv6 on GPON and CATAN LT’s

6) ALU00123529 : vMAC on NGLT-A

7) ALU00123588 : PON feeder protection

8) ALU00123660 : NGLT-A/B scaling

9) ALU00123599 : OLT/OMCI/ONT support for TR-69

CFT Workshop R4.2.02 - 2 All Rights Reserved © Alcatel-Lucent 2010,

11) ALU00123542 : LT backplane load sharing towards NT

12) ALU00123538 : Operator with RAD VSA and def prof

13) ALU00123705 : NELT-B phase 2

14) ALU00274393 : MAC address overbooking on CATE/CATAN

15) ALU00298179/ALU00303766 : Support overlapping

16) ALU00305702 : Increase number of multicast VLANs to 64

17) ALU00467870 : PIM-SSM : ASM to SSM translation per SAP

18) ALU00421300 : Porting of 2.5G REM capabilities from

CFT Workshop R4.2.02 - 3 All Rights Reserved © Alcatel-Lucent 2010,

20) ALU00719661/ALU00808506 : IPv6 on NANT-E (trident+)

21) ALU00811527 : Relay Tag Circuit Id / Remote Id

22) ALU00121718/ALU00123597 : Ethernet OAM support (ph1)

23) ALU00123702 : License key for Cross talk cancellation

24) ALU00761457 : DTAG SNMP Conformity of R4.2 MIBs

25) ALU00747163 : Demo for RAC on 1st mile for unicast

CFT Workshop R4.2.02 - 4 All Rights Reserved © Alcatel-Lucent 2010,

CFT Workshop R4.2.02 - 5 All Rights Reserved © Alcatel-Lucent 2010,

IPv6 FD document 3HH-03825-AAAA-FDZZA

IPv6 address anti-spoofing is similar to IPv4 anti-spoofing. The ISAM discards in

CFT Workshop R4.2.02 - 6 All Rights Reserved © Alcatel-Lucent 2010,

Feature binder: 3HH-08216-AAAA-ADZZA

CFT Workshop R4.2.02 - 7 All Rights Reserved © Alcatel-Lucent 2010,

CFT Workshop R4.2.02 - 8 All Rights Reserved © Alcatel-Lucent 2010,

IPv6 FD document 3HH-03825-AAAA-FDZZA

In general: ICMPv6 messages are allowed to be forwarded, following the MAC

CFT Workshop R4.2.02 - 9 All Rights Reserved © Alcatel-Lucent 2010,

ICMPv6 filtering disabled ICMPv6 filtering enabled

Upstream Downstream Upstream Downstream

unicast multicast unicast multicast Unicast multicast unicast multicast

NS vMAC vMAC NS vMAC vMAC

NA vMAC vMAC NA vMAC vMAC

RS vMAC vMAC RS vMAC vMAC

CFT Workshop R4.2.02 - 10 All Rights Reserved © Alcatel-Lucent 2010,

i-bridge vlan, IPv6MC flag enabled

ICMPv6 filtering disabled ICMPv6 filtering enabled

Upstream Downstream Upstream Downstream

Unicast multicast unicast multicast Unicast multicast unicast multicast

NS vMAC vMAC NS vMAC vMAC

NA vMAC vMAC NA vMAC vMAC

RS vMAC vMAC RS vMAC vMAC

CFT Workshop R4.2.02 - 11 All Rights Reserved © Alcatel-Lucent 2010,

i-bridge vlan, IPv6MC flag disabled

ICMPv6 filtering disabled ICMPv6 filtering enabled

Upstream Downstream Upstream Downstream

unicast multicast unicast multicast Unicast multicast unicast multicast

CFT Workshop R4.2.02 - 12 All Rights Reserved © Alcatel-Lucent 2010,

Feature binder: 3HH-08216-AAAA-ADZZA