@puck.nether.net
Subject: Re: [j-nsp] MPLS and QoS at penultimate hop ?
On Mon, Feb 04, 2013 at 09:36:10AM -0900, Christopher E. Brown wrote:
The packet is classified on input.
*UNLESS* you use table-label in a l3vpn, then it gets re-classified
after the label POP.
Intresting. However, my
On Mon, Feb 04, 2013 at 09:36:10AM -0900, Christopher E. Brown wrote:
The packet is classified on input.
*UNLESS* you use table-label in a l3vpn, then it gets re-classified
after the label POP.
Intresting. However, my question is not about l3vpn, it is about plain
old IPv4 packet with one
The table-lable bit is the one time I am aware of that the forwarding
class is changed in the middle without the system being specifically
setup to do so.
Assuming that you have mpls and ipv4 classifiers on all interfaces.
Incoming is classified on the label, label pop, outgoing is transmitted
The packet is classified on input.
*UNLESS* you use table-label in a l3vpn, then it gets re-classified
after the label POP.
On 2/3/13 6:03 PM, Chris Kawchuk wrote:
It was my understanding that the label was logically popped on
Egress (in terms of how one would envision the packet flow);
*UNLESS* you use table-label in a l3vpn, then it gets re-classified after the
label POP.
Aha, Very true - Good ole vrf-table-label
So, to Alexandre for L3VPN, just do this:
class-of-service {
routing-instances {
all {
classifiers {
exp MY-CLASIFIER;
Hi!
Simple question I'm not able to find answer for: what is the order
of label pop operation and BA classification on penultimate router ?
I have a gut feeling that label is stripped first and then BA
classification is done on a naked packet, f.e., ipprec-based
in case of IP packet, without
It was my understanding that the label was logically popped on Egress (in
terms of how one would envision the packet flow); hence the outer label EXP
bits were evaluated by the BA classifier on ingress properly. (Whether it's
popped on ingress, yet evaluated prior-to-pop is a mechanics thing..)
7 matches
Mail list logo
