The l2nm from ietf-opsawg-wg

EVPN: Missing validation for dot1q

The following MUST statements are missing.

r.

  deviation "/l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node/l2vpn-ntw:vpn-network-accesses/l2vpn-ntw:vpn-network-access/l2vpn-ntw:connection/l2vpn-ntw:dot1q-interface/l2vpn-ntw:dot1q/l2vpn-ntw:c-vlan-id" {
    deviate add {
      must "../../../l2vpn-ntw:encapsulation-type='vpn-common:dot1q'"{
        error-message "c-vlan-id can only be set when encapsulation-type is 'vpn-common:dot1q'";
      }
  deviation "/l2vpn-ntw:l2vpn-ntw/l2vpn-ntw:vpn-services/l2vpn-ntw:vpn-service/l2vpn-ntw:vpn-nodes/l2vpn-ntw:vpn-node/l2vpn-ntw:vpn-network-accesses/l2vpn-ntw:vpn-network-access/l2vpn-ntw:connection/l2vpn-ntw:dot1q-interface/l2vpn-ntw:dot1q" {
    deviate add {
      must "../../l2vpn-ntw:encapsulation-type='vpn-common:dot1q' and l2vpn-ntw:c-vlan-id"{
        error-message "c-vlan-id is required when encapsulation-type is 'vpn-common:dot1q'";
      }

remove dependency on the l2sm

clean up the module and point to the common module.

EVPN: Vpws-evpn IDs missing

EVI ID, EVI Source, EVI Target Needed for configuration. All Integer values. Could be received northbound or via a pool.

EVPN: ESI missing for multi-homed evpn-vpws

Value defined in RFC7432 missing

ECMP configuration for Aliasing

Flexibility to allow aliasing to MultiHoming CE

     bgp-evpn
        local-ac-name "MH“ eth-tag 710
        remote-ac-name "HL4-5“ eth-tag 710
        evi 710
        mpls
                auto-bind-tunnel
                    …
                exit
                ecmp 2
                no shutdown
        exit
     exit

Add rd (route distinguisher) parameter likewise l3nm

Hello

Checking the current draft, I spotted this difference between the two, to be corrected before uploading a next release for consistency.

ALMP plus filter policies

Possibility to add filter + ALMP at interface level

     sap lag-3:720 create 
        auto-learn-mac-protect
        ingress filter mac 720

configure filter mac-filter 720 create
default-action forward
entry 10 create
description "VRRP"
match src-mac 00:00:5e:00:01:00 ff:ff:ff:ff:ff:00
action drop
exit

Review in opsawg list (format & bugs)

Format correctly the Yang
Corrections needed in IANA section:

IANA Considerations registers an existing prefix
YANG imports mostly lack reference statements.
-Abstract 'The L2SM complements the Layer 2 Service model ...'

EVPN: Add support for dot1q push/pop/translate options

Missing the option to re-write dot1q information received in access.

Prepare text for -01 version which uses common module

Underlying tunnel selection per service/Node

In our proposal, There will be an ordered list by priorities of tunnel selection type (i.e.LDP,RSVP-TE, SR, SR-TE,etc..) per node and per services.
The reasonn why this list of preferences must consider also services and not only ingress node is because for services initiated in the same PE router, one service can be Best Effort and LDP is enough but other service can be low latency and TE is required.
If the Node does not support the first option in the list of preferences then try the second one and so on...

Consider E-VPN Support

Consider E-VPN Support (note this is a network model, not the device model to configure E-VPN)

EVPN: Control-word missing

Per RFC4448, control-word is missing.

why should we introduce site bearer into L2NM

Since L2SM has already defined bearer under site-network-accesses, why not reuse it? Instead introduce site-bearer?

EVPN: Incorrect XPATH in when expressions

Under list signaling-options
container l2vpn-bgp
Existing: when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'vpn-common:l2vpn-bgp'"
Correct clause: when "../type = 'vpn-common:l2vpn-bgp'"

container evpn-bgp
Existing: when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'vpn-common:evpn-bgp'"
Correct clause: when "../type = 'vpn-common:evpn-bgp'"

container t-ldp-pwe
Existing: when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'vpn-common:t-ldp'"
Correct clause: when "../type = 'vpn-common:t-ldp'"

container l2tp-pwe
Existing: when "/l2vpn-ntw/vpn-services/vpn-service/vpn-nodes/vpn-node/signaling-options/type = 'vpn-common:l2tp'"
Correct clause: when "../type = 'vpn-common:l2tp'"

EVPN: t-ldp with static label

When using t-ldp as type, we are missing the mpls-label in the ac-pw-list.

Use same syntax for underlay transport selection as in L3NM

+--rw underlay-transport
| +--rw type? protocols-type

Service mapping with BGP Tunnel and MPLS with LDP

Is BGP Tunnel BGP over GRE? Is there any other BGP Tunnel type? In addition, TE service mapping provide service mapping to TE tunnel, but how Service Mapping with BGP tunnel or MPLS with LDP? Where is this specified?

how precedence-type is different from access-priority under availability

I feel the role of access-priority and precedence-type is almost same. what is the their key difference? one is service level, the other is access level? Can you provide a usage example of precedence-type?

Max Neighbour Mac address limit

Add RTs to correctly support BGP-VPLS

L2SNM supports BGP-VPLS but not RT:RD are defined to support the configuration:

Example:

configure service vpls 1 customer 1 create
  bgp
    route-distinguisher 65536:1
    route-target export target:65536:1 import target:65536:1
    pw-template-bind 1
  exit

ietf-opsawg-wg / l2nm Goto Github PK

l2nm's Introduction

IMPORTANT NOTE

l2nm's People

Contributors

Stargazers

Watchers

Forkers

l2nm's Issues

Example:

Recommend Projects

Recommend Topics

Recommend Org