Dallaglio NETCONF OFCtalk 2016

YANG Model and NETCONF Protocol
for Control and Management

of Elastic Optical Networks

M. Dallaglio1, N. Sambo1, J. Akhtar1, F. Cugini2, P. Castoldi1

1: Scuola Superiore Sant’Anna, Pisa, Italy

2: CNIT, Pisa, Italy

OFC 2016!
Introduction!
•  Relevant advances in the data and control plane
-  data plane:
✓ flexible transponders à configurable/adaptable rate, FEC, format, slice-ability …
✓ support of monitoring through Digital Signal Processing (pre-FEC BER, Q factor, etc.)
-  control plane:
✓ Software Defined Networking à to remotely set network devices, programming transmission
characteristics (such as bit rate) and switching
•  Management?
-  innovations have not followed these trends yet [a]:
‣ issues related to the presence of network devices from different vendors
‣ lack of standard solutions (e.g., for operation administration and maintainance – OAM)
•  NETCONF based on YANG model is emerging as a standard SDN protocol providing both control
(e.g., data plane device configuration) and management (e.g., access to monitoring information)
functionalities
In this paper:
•  we present and demonstrate a YANG model describing flexible transponders supporting monitoring
functionalities
•  experimental demonstration: connection setup and OAM through NETCONF and YANG
[a] A. Martinez, M. Yannuzzi, V. Lopez, D. Lopez, W. Ramirez, R. Serral-Gracia, X. Masip-Bruin, M. Maciejewski, and J. Altmann, “Network management
challenges and trends in multi-layer and multi-vendor settings for carrier-grade networks,” Communications Surveys Tutorials, IEEE, vol. 16, no. 4, 2014.

NETCONF and YANG!
• NETCONF: Standard protocol defined by the IETF [b]

• Provides mechanisms to install, manipulate, and delete states of network devices
à it enables device configuration
• YANG is recommended to model and describe network devices into NETCONF
messages [c]
- ongoing work on YANG model for transponders, e.g. [d]
• NETCONF is indicated for management because it includes NOTIFICATION
messages that can implement ALARMS upon monitoring
[b] R. Enns, M. Bjorklund, J. Schoenwaelder, and A. Bierman, “Network configuration protocol (NETCONF),” IETF RFC 6241, June 2011.

[c] M. Bjorklund, “YANG - a data modeling language for the network configuration protocol (NETCONF),” IETF RFC 6020.

[d]
J. Vergara and et al., IETF draft-vergara-flexigrid-yang-02, March. 2016.

NETCONF messages!
Controller Device
NETCONF Client NETCONF Server
<hello>
<hello> DISCOVERY
<get>
WHICH SUPPORTED
<rpc-‐reply> CAPABILITIES?
<edit-‐config>
<ok>
DEVICE CONFIGURATION
<create-‐subscrip@o
n> SUBSCRIPTION TO
<ok> SPECIFIC NOTIFICATIONS
<no@fica@on> NOTIFICATION THAT

SUBSCRIBED EVENT
OCCURRED
Reference sliceable transponder (S-BVT)!
S-BVT
(add/drop ports)
Sub-carrier module #1
Optical coupler/
OXC
mux
Sub-carrier module #2
Sub-carrier module #k
Sub-carrier module!
TX side!
MOD!
DSP! DAC!
PM!
COH!
DSP! ADC!
RX!
RX side!
N. Sambo and et al., “Next generation sliceable bandwidth variable transponders,” Communications Magazine, IEEE, vol. 53, no. 2, pp. 163–171, Feb 2015.

TRANSPONDER YANG SCHEME!
Following YANG standardization guidelines IETF [e,f] and OpenConfig working group [g],
we propose:
TRANSPONDER
NODE INFORMATION
NOTIFICATIONS
SLICE-‐ABILITY SUPPORT
N M
SUB-‐CARRIER 2 2
MODULE 1 CONNECTION 1
[e] A. Bierman, “Guidelines for Authors and Reviewers of YANG Data Model Documents”, IETF RFC 6087, 2011.
[f] R. Shakir, “Consistent Modeling of Opera@onal State Data in YANG draX-‐openconfig-‐netmod-‐opstate-‐01”, IETF DraX, 2015.
[g] hZp://www.openconfig.net
YANG CONFIG AND STATE DATA!
Configuration data
• Writable (NETCONF <edit-config>)
• Explicitly set by an external entity
State data
• Read only (NETCONF <get>)
• Parameters that cannot be set by an external entity
• List of parameters supported by the device
SUB-CARRIER MODULE!
CONFIG

RX
p  Modula@on p  Direc@on
•  Local oscillator
p  FEC p  Bit rate TX •  Sampling rate
p  Central frequency p  Baud rate •  Output power •  Analog BW
STATE
RX
Monitored
p  Direc@on parameters:
p  Supported Modula-on p  Supported Bit rate •  Input power
p  Supported FEC p  Supported Baud rate •  Pre-‐FEC BER
•  PMD
•  Q-‐Factor
•  CD
•  OSNR …
NOTIFICATION!
PRE-‐FEC BER CHANGE

p  Sub-‐carrier ID
p  pre-‐FEC BER above a threshold
<create-‐subscrip@on>
Filter: e.g., pre-‐FEC BER > TH

Controller Device
event
<no@fica@on>
pre-‐FEC BER > TH
Controller Device
Experimental demonstration!
•  The Controller based on PYTHON NETCONF client
•  The device runs ConfD, a NETCONF server implementation made by Tail-f
•  A 100 Gb/s connection request has been considered:
-  a baudrate of 28 Gbaud PM-QPSK supports 100 Gb/s net rate and 7% FEC
-  31 Gbaud around 20% FEC
•  The controller subscribes to the transponder Notification stream specifying, through a filter, that it is
interested on pre-FEC BER exceeding 9 × 10−4 threshold.
Edt-config: connection setup!
Subscription to pre-FEC BER increase!
Notification of BER increase!
Conclusions!
•  This paper presented a YANG model for transponders with monitoring capabilities, slice-
ability, and variable:
•  rate
•  baudrate
•  FEC
•  format
•  Experiments have shown connection set up and management
•  OAM: the mechanism of Notification messages can be easily exploited to implement
alarms
ACK: The work has been supported by the ORCHESTRA project.

TRANSPONDER YANG
module transponder {
namespace "http://sssup.it/transponder";
prefix tran;

import modulation-‐formats {
prefix mdfrms;
}

import fec-‐types {
prefix fec;
}

import ietf-‐yang-‐types {
prefix yang;
}

organization
"Scuola Superiore Sant'Anna Network and Services Laboratory";

description
"This module contains a YANG definitions for configuring Optical Transponder.";

revision 2015-‐09-‐15 {
description "Initial Revision.";
reference "TBD";
}

typedef transmission-‐type {
description "The transmission method";
type enumeration {
enum NWDM;
enum O-‐OFDM;
enum TFP;//Time-‐frequency packing
}
}

typedef direction-‐type {
description "Indicates the direction";
type enumeration {
TRANSPONDER YANG
typedef direction-‐type {
description "Indicates the direction";
type enumeration {
enum TX;
enum RX;
}
}

typedef bit-‐rate-‐type {
type decimal64 {
fraction-‐digits 3;
range "0..max";
}
units "Gb/s";
}

typedef baud-‐rate-‐type {
type decimal64 {
range "0..max";
}
units "Gbaud";
}

typedef modulation-‐type {
type identityref {
base mdfrms:modulation-‐format;
}
}

typedef fec-‐type {
type identityref {
base fec:fec-‐type;
}
}

TRANSPONDER YANG
typedef frequency-‐ghz-‐type {
type decimal64 {
range "0..max";
}
units "GHz";
}

grouping fec-‐config {
description "Configuration data for forward error correction";

container fec-‐in-‐use {
description "FEC in use";
presence "Enables FEC";

leaf name {
type fec-‐type;
}

container rate {
description
"The code rate is given by message-‐length/block-‐length";
leaf message-‐length {
type int16 {
range "1..max";
}
}
leaf block-‐length {
type int16 {
range "1..max";
}
}
must "block-‐length >= message-‐length" {
error-‐message "block-‐length must be greater or equal to message-‐length";
}
}//container rate

}//container fec-‐in-‐use
}//grouping fec-‐config
TRANSPONDER YANG
grouping fec-‐state {
description "Operational state data for forward error correction";
container supported-‐fec {
description "List of supported FEC schemes";
leaf-‐list fec {
type fec-‐type;
}
}//supported
}//grouping fec-‐state

grouping transmitter-‐config {
description "Configuration data for the transmitter";
leaf output-‐power {
description "launch power at the transmitter";
type int16;
units "dBm";
}
}//grouping transmitter-‐config

grouping transmitter-‐state {
description "Operational state data for the transmitter";
}

grouping receiver-‐config {
description "Configuration data for the receiver";

leaf local-‐oscillator {
type frequency-‐ghz-‐type;
}

leaf sampling-‐rate {
description "Minimum hardware requirements in terms of sampling rate";
type uint32;
units "GS/s";
}

TRANSPONDER YANG
leaf analog-‐bw {
description "Minimum hardware requirements in terms of analog bandwidth";
}

}//grouping receiver-‐config

grouping receiver-‐state {
description "Operational state data for the receiver";

leaf input-‐power {
description "per-‐channel received optical power at the receiver";
type int16;
units "dBm";
}

leaf pre-‐fec-‐ber {
description
"Pre-‐FEC Bit Error Rate.";
type decimal64 {
range "0..max";
}
}

leaf sample-‐variance {
type decimal64 {
range "0..max";
}
reference
"http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7035536";
}

TRANSPONDER YANG
leaf pmd {
description
"Polarization Mode Dispersion.";
type decimal64 {
range "0..max";
}
units "ps/(km)^0.5";
}

leaf cd {
description
"Chromatic Dispersion.";
type decimal64 {
}
units "ps/nm/km";
}

leaf q-‐factor{
type decimal64 {
}
units "dB";
}
}//grouping receiver-‐state

grouping subcarrier-‐module-‐config {
description "Configuration data for the optical subcarrier-‐module";

leaf direction {
description "Defines whether the subcarrier is received or transmitted";
type direction-‐type;
}

leaf bit-‐rate {
description "The bit-‐rate in use";
type bit-‐rate-‐type;
}
TRANSPONDER YANG
leaf baud-‐rate {
description "The baud-‐rate in use";
type baud-‐rate-‐type;
}

leaf modulation {
description "Modulation format in use";
type modulation-‐type;
}
uses fec-‐config;
leaf central-‐frequency {
description
"The central frequency of the subcarrier.";
}

leaf bandwidth {
description
"The bandwidth occupied.";
}
}//subcarrier-‐module-‐config

grouping subcarrier-‐module-‐state {
description "Operational state data for the optical subcarrier-‐module";
container supported-‐bit-‐rates{
description "List of supported bit-‐rates";
leaf-‐list bit-‐rate {
description "the bit rate value";
type bit-‐rate-‐type;
}
}

container supported-‐baud-‐rates {
description "List of supported baud-‐rates";
leaf-‐list baud-‐rate {
description "the baud rate value";
type baud-‐rate-‐type;
}
}
TRANSPONDER YANG
container supported-‐modulations {
description "List of supported modulation formats";
leaf-‐list modulation {
description "Name of the supported modulation";
type modulation-‐type;
}
}
uses fec-‐state;
}//subcarrier-‐module-‐state

grouping subcarrier-‐module {
description "Top-‐level grouping for optical subcarrier-‐module";

container config {
description
"Configuration data for subcarrier-‐module";
uses subcarrier-‐module-‐config;

container transmitter {
when "../direction = 'TX'";
uses transmitter-‐config;
}

container receiver {
when "../direction = 'RX'";
uses receiver-‐config;
}
}
container state {
config false;
description
"Operational state data for subcarrier-‐module";
uses subcarrier-‐module-‐config;
uses subcarrier-‐module-‐state;

container transmitter {
when "../direction = 'TX'";
uses transmitter-‐config;
uses transmitter-‐state;
}
TRANSPONDER YANG
container receiver {
when "../direction = 'RX'";
uses receiver-‐config;
uses receiver-‐state;
}
}

}//subcarrier-‐module

grouping connection-‐config {
description "Configuration data for a connection";
leaf connection-‐id{
type uint32;
}

leaf transmission-‐scheme {
description "The scheme adopted for the transmission";
type transmission-‐type;
}

list subcarrier {
description "List of ids of the involved subcarriers";
key "subcarrier-‐id";
leaf subcarrier-‐id {
type leafref {
path "/tran:transponder/tran:subcarrier-‐module/tran:subcarrier-‐id";
}
}
}

container frequency-‐slot {
description
"The frequency range allocated to a slot
within the flexible grid and unavailable to other slots. A
frequency slot is defined by its nominal central frequency and its
slot width.";
reference "draft-‐ietf-‐ccamp-‐flexi-‐grid-‐fwk-‐07";

TRANSPONDER YANG
leaf nominal-‐central-‐frequency-‐granularity {
description
"It is the spacing between allowed nominal central frequencies.";
default 6.25;
}//leaf nominal-‐central-‐frequency-‐granularity

leaf slot-‐width-‐granularity {
description "It is the minimum slot width.";
default 12.5;
}//leaf slot-‐width-‐granularity

leaf n {
description
"n gives the nominal central frequency (ncf) using the following formula:
ncf = 193.1THz + n x nominal-‐central-‐frequency-‐granularity[THz].";
type int16;
mandatory true;
}//leaf n
leaf m {
description
"m gives the slot width. A slot width is constrained to be
m x slot-‐width-‐granularity";
type int16 {
range "1..max";
}
mandatory true;
}//leaf m
}//container frequency-‐slot

leaf source-‐address {
description "The IP address of the source node";
Type inet:ip-‐address;
}//leaf source-‐address
leaf destination-‐address {
description "The IP address of the destination node";
Type inet:ip-‐address;
}//leaf source-‐address
}//grouping connection-‐config
TRANSPONDER YANG
grouping connection-‐state {
description "Operational state data for a connection";
}//grouping connection-‐state

grouping connections {
description "List of all connections served by the transponder";
list connection {
key "connection-‐id";
leaf connection-‐id {
description "references the configured connection-‐id";
type leafref {
path "../config/connection-‐id";
}
}
container config {
description "Configuration parameters for connection";
uses connection-‐config;
}

container state {
config false;
description "State variables for connection";
uses connection-‐config;
uses connection-‐state;
}
}//list connection
}//grouping connections

TRANSPONDER YANG
//-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ MAIN TREE -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐//
container transponder {
list subcarrier-‐module {
description
"List of all the subcarrier modules installed in the transponder";
key "subcarrier-‐id";
leaf subcarrier-‐id {
type uint32;
}
uses subcarrier-‐module;
}

leaf slice-‐ability-‐support {
when "count(../subcarrier-‐module) > 1";
type boolean;
config false;
description "Determines if the transponder is slice-‐able.";
}

leaf node-‐id {
description "ID of the node where the transponder is installed";
type uint16;
}

leaf add-‐drop-‐id {
description "Add/drop ID inside the node";
type uint16;
}

container connections {
uses connections;
}
}

TRANSPONDER YANG
//-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐ NOTIFICATIONS -‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐//
notification pre-‐fec-‐ber-‐change {
leaf subcarrier-‐module-‐id {
description
"An existing subcarrier-‐module in the list";
type leafref {
}
mandatory true;
}
leaf pre-‐fec-‐ber {
type leafref {
path "/transponder/subcarrier-‐module[subcarrier-‐id=current()/../subcarrier-‐module-‐id]/state/receiver/pre-‐fec-‐ber";
}
mandatory true;
}
}
notification pmd-‐change {
leaf subcarrier-‐module-‐id {
description
"An existing subcarrier-‐module in the list";
type leafref {
}
mandatory true;
}
leaf pmd {
type leafref {
path "/transponder/subcarrier-‐module[subcarrier-‐id=current()/../subcarrier-‐module-‐id]/state/receiver/pmd";
}
mandatory true;
}
}
}//module transponder

email: nicola.sambo@sssup.it
CONNECTION
CONFIG
p  Connec@on ID List of Sub-‐carrier IDs Frequency Slot
p  n
p  Transmission scheme p  Sub-‐carrier ID
p  m
STATE
p  Connec@on ID List of Sub-‐carrier IDs Frequency Slot
p  n
p  Transmission scheme p  Sub-‐carrier ID
p  m
CONNECTION Example
<connecEon>
<connecEon-‐id>1</connecEon-‐id>
<config> <state>
<connecEon-‐id>1</connecEon-‐id> <connecEon-‐id>1</connecEon-‐id>
<transmission-‐scheme> <transmission-‐scheme>
NWDM NWDM
</transmission-‐scheme> </transmission-‐scheme>
<subcarrier> <subcarrier>
<subcarrier-‐id>1</subcarrier-‐id> <subcarrier-‐id>1</subcarrier-‐id>
<subcarrier-‐id>2</subcarrier-‐id> <subcarrier-‐id>2</subcarrier-‐id>
</subcarrier> </subcarrier>
<frequency-‐slot> <frequency-‐slot>
<n>0</n> <n>0</n>
<m>6</m> <m>6</m>
</frequency-‐slot> </frequency-‐slot>
</config> </state>
</connecEon>

Dallaglio NETCONF OFCtalk 2016

Uploaded by

Copyright:

Available Formats

Dallaglio NETCONF OFCtalk 2016

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

Dallaglio NETCONF OFCtalk 2016

Uploaded by

Copyright:

Available Formats

YANG Model and NETCONF Protocol

for Control and Management

1: Scuola Superiore Sant’Anna, Pisa, Italy

• NETCONF: Standard protocol defined by the IETF [b]

<no@ﬁca@on> NOTIFICATION THAT

PRE-‐FEC BER CHANGE

pre-‐FEC BER > TH

ACK: The work has been supported by the ORCHESTRA project.

You might also like

Dallaglio NETCONF OFCtalk 2016

Uploaded by

Copyright:

Available Formats

Dallaglio NETCONF OFCtalk 2016

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

Dallaglio NETCONF OFCtalk 2016

Uploaded by

Copyright:

Available Formats

YANG Model and NETCONF Protocol

for Control and Management 

1: Scuola Superiore Sant’Anna, Pisa, Italy

• NETCONF: Standard protocol defined by the IETF [b]

<no@ﬁca@on> NOTIFICATION THAT

PRE-­‐FEC BER CHANGE

pre-­‐FEC BER > TH

ACK: The work has been supported by the ORCHESTRA project.

You might also like

for Control and Management

1: Scuola Superiore Sant’Anna, Pisa, Italy

• NETCONF: Standard protocol defined by the IETF [b]

PRE-‐FEC BER CHANGE

pre-‐FEC BER > TH