Spec: Extended Connection/NSE labels

[Bolodya1997]

To select NSE client uses network service name and labels. Now there is only one selector for labels:

• exact match

request: {
    Labels: map[string]string{
        "value": "10",
    }
}

nse: {
    Labels: map[string]string{
        "value": "10",
    }
}

A proposal is to add extra selectors:

1. set selectors - value is a comma separated set of values:

• one of

request: {
    Labels: map[string]string{
        "node": "one-of:a,b,c",
    }
}

nse: {
    Labels: map[string]string{
        "node": "a",
    }
}

• contains

request: {
    Labels: map[string]string{
        "typesSupported": "contains:b,c",
    }
}

nse: {
    Labels: map[string]string{
        "typesSupported": "a,b,c,d",
    }
}

2. comparison selectors - value is a number:

• lower than

request: {
    Labels: map[string]string{
        "latency": "lower-than:100",
    }
}

nse: {
    Labels: map[string]string{
        "latency": "40",
    }
}

• greater than

request: {
    Labels: map[string]string{
        "capability": "greater-than:100",
    }
}

nse: {
    Labels: map[string]string{
        "capability": "500",
    }
}

[denis-tingaikin]

Sounds a little bit like networkservicemesh/api#51

[edwarnicke]

Do we have a current use case you have in mind for this?

[Bolodya1997]

Guess it is really a duplicate, closing :)