0% found this document useful (0 votes)
32 views5 pages

Notes 29 09

Uploaded by

infosec BHA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
32 views5 pages

Notes 29 09

Uploaded by

infosec BHA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 5

28-09-2023:

1. Conveying the DNS Server IP to RU -> Concluded to be Proposed to RU.

IPv4
DHCP Option 6 -> Length = 4 byte or 8 byte(opt) (IPv4)
Primary DNS IP
(opt)Secondary DNS IP.
IPv6
DHCP Option 23 -> Length = 16 byte or 32 bytes(opt) (Ipv6)
Primary DNS IP
(opt)Secondary DNS IP

=> PDL check for FQDN vs DNS IP should be present.


=> PDL RU RMOD-Internet Protocol version should be present with CMP and DNS IP
address version.

2. Conveying CMP Server Parameters.


DHCP Option 43
Type:3
TLV
Type:4
TLV
Type: New Type
Length: Length of cmp parameters
Value: CMP Parameters

Open: -
1. Without Additional trust anchor support, there is no need of multiple CMP server
to be supported.??

RUCMPMAP (New MOC)


=> 1. CMP Server DN ---> MNL/<<CMPFH/CMPESERVER>> (Closed)
CMPSERVER MOC -> contains all parameters required for Fronthaul CMP.

2. CRL Server DN --> MNL/CERTH/CRL (open): 1. Whether separate MAP Object.


2) CRL seems to be URI, how DU can obtain IP?

3. RMODDN --> (open)-> Direction of the pointer.

4. NAT --> Yes OR No.

===========History=================================================

how to differentiate between Primary & Secondary CMP Server is there any parameter
required to mark it as primary or secondary
Parameter list should be identical for split A & split B.

Firewall related parameters port number or range of parameters for


CMP(Primary/Secondary/CRL/DNS(primary and secondary) -- ->

Primary CMP Server IP Address


Secondary CMP Server IP Address
Port Number for Primary & Secondary CMP Server
***************Mandatory CMP Server Parameters*********************
CMP Directory (serverPath) is mandatory to pass on to RU.
CMP Server IP address
CMP Server Port number
*******************************************************************
Do primary and secondary CMP Server will have same server path i.e. CMP Directory ?

CMP server can be different for RU & DU.

Secondary CMP server is optional.

CMP server configuration can be global for all RUs or each RU can have specific CMP
Server detail.
But not a mix and match of above.

How to associate CMP Server with RU(RMOD)?


-- - it can be a list of RMODs reffered from CMP Server object MO.
-- - RMOD can have reference DN to CMP server MO.

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
Is following configuration is allowed or not ?
RU1 -- Prim (CMP1)
--Secon (CMP2)

RU2 -- Prim(CMP2)
-- Secon(CMP1)

CMPServer Manadatory parameters should be defined under a seprate MOC and this MOC
instance can be referenced by RU
as a Primary or Secondary CMP Server.(RMOD-Primary Server DN / RMOD-Secondary
Server DN)

&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&

New Parameter to distinguish between Global or RU Specific CMP server deployments.

For Global CMP Server Deployment :- Max two instances of CMP server MO should be
allowed. kind of CMPFH/CMPSERVER-1 or CMPFH/CMPSERVER-2 . Then in NIDD
configuration parameter detail CMPSERV-1 should be as Primary CMP Server and
CMPSERVER-2 should be as Secondary CMP Server
For Per RU CMP Server Deployment :- It can be more than two CMP server MO (linked
through RMOD-Primary Server DN/RMOD-Secondary Server DN)

******************************28th September*****************************
1)New Parameter to indicate position of CMPSERVER ..whether it can be behind DU or
RU can directly reach CMP server. This will decide upon requirement of bypass
policy and firewall/routing/natting rules at DU.
2)To be discussed New Parameter to indicate position of DNS Server -- -> in case of
external DNS server-- It can be reached by DU from Backhaul and RU from Fronthaul.
So in this scenerio firwall rule update is not required at DU.

To be checked with PDM -- -> Single location for CMP/CRL/DNS , so that we can have
only two options 1. CMP/DNS/CRL behind DU 2.CMP/DNS/CRL between DU & RU. In this
case , there can be single switch to toggle between these two option.
it will simplyfy solution .

UnUsed Port in case of unused default port

RUCMPMAP-1 to 96

-> 1. CMP Server DN ---> MNL/<<CMPFH/CMPESERVER>>/IP/FQDN + Port --> There will be


a new CMPFH and SERVER MOC.

-> 2. DNS IP DN ---> MNL/MNLENT/DNS/ serverIpAddressPrimary (IPv4 or IPv6, IPv6 has


dependency on backhaul M-plane dual stack feature RP001186 flag)
OR MNL/MNLENT/DNS/ serverIpAddressSecondary

(if No NULL, this means DNS not required, PDL rule should ensure that in FQDN
case, DNS is always set)
This parameter is not needed.
-> 3. CRL Server DN --> MNL/CERTH/CRL
-> RMODDN -->
-> NAT --> Yes OR No.

NATing rule for RU initiated CMP traffic and Response from CMP Server:

iptables -t nat -A POSTROUTING -p tcp -s RU IP@[MOC:


MNL/MNLENT/MPLANEFHNW/RUCMPMAP/rmodDN ] -d CMP Server IP@[MOC:
MNL/MNLENT/MPLANEFHCMP/CMPFH??] --dport <<CMP Server DN --->
MNL/CMPFH-1/CMPESERVER/Port>>> -j SNAT --to-src DU M-Plane IP@
[MOC: MNL/MNLENT/MPLANENW.mPlaneIpAddressDN
=>MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4]:[Unique Range]

iptables -t nat -A POSTROUTING -p tcp -s RU IP@[MOC:


MNL/MNLENT/MPLANEFHNW/RUCMPMAP/rmodDN ] -d CRL Server IP@[MOC:
MNL/MNLENT/MPLANEFHCMP/CMPFH] --dport <<CMP Server DN --->
MNL/CMPFH-1/CMPESERVER/Port>>> -j SNAT --to-src DU M-Plane IP@
[MOC: MNL/MNLENT/MPLANENW.mPlaneIpAddressDN
=>MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4]:[Unique Range]

This is when it is FQDN.


iptables -t nat -A POSTROUTING -p udp -s RU IP@[MOC:
MNL/MNLENT/MPLANEFHNW/RUCMPMAP/rmodDN ] -d DNS Server IP@[MOC:
MNL/MNLENT/MPLANEFHCMP/CMPFH] --dport <<CMP Server DN --->
MNL/CMPFH-1/CMPESERVER/Port>>> -j SNAT --to-src DU M-Plane IP@
[MOC: MNL/MNLENT/MPLANENW.mPlaneIpAddressDN
=>MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4]:[Unique Range]
iptables -t nat -A POSTROUTING -p tcp -s RU IP@[MOC:
MNL/MNLENT/MPLANEFHNW/RUCMPMAP/rmodDN ] -d [CRL Server IP range low - high] @[MOC:
MNL/MNLENT/MPLANEFHCMP/CMPFH??] --dport <<CMP Server DN --->
MNL/CMPFH-1/CMPESERVER/Port>>> -j SNAT --to-src DU M-Plane IP@
[MOC: MNL/MNLENT/MPLANENW.mPlaneIpAddressDN
=>MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4]:[Unique Range]

28-09-2023:

3. Conveying the DNS Server IP to RU -> Concluded to be Proposed to RU.

IPv4
DHCP Option 6 -> Length = 4 byte or 8 byte(opt) (IPv4)
Primary DNS IP
(opt)Secondary DNS IP.
IPv6
DHCP Option 23 -> Length = 16 byte or 32 bytes(opt) (Ipv6)
Primary DNS IP
(opt)Secondary DNS IP

=> PDL check for FQDN vs DNS IP should be present.


=> PDL RU RMOD-Internet Protocol version should be present with CMP and DNS IP
address version.

4. Conveying CMP Server Parameters.


DHCP Option 43
Type:3
TLV
Type:4
TLV
Type: New Type
Length: Length of cmp parameters
Value: CMP Parameters

Open: -
4. Without Additional trust anchor support, there is no need of multiple CMP server
to be supported.??

RUCMPMAP (New MOC)


=> 1. CMP Server DN ---> MNL/<<CMPFH/CMPESERVER>> (Closed)
CMPSERVER MOC -> contains all parameters required for Fronthaul CMP.

2. CRL Server DN --> MNL/CERTH/CRL (open): 1. Whether separate MAP Object.


2) CRL seems to be URI, how DU can obtain IP?

3. RMODDN --> (open)-> Direction of the pointer.


4. NAT --> Yes OR No.

You might also like