Found 1 record.

Status: Held for Document Update (1)

RFC 6625, "Wildcards in Multicast VPN Auto-Discovery Routes", May 2012

Note: This RFC has been updated by RFC 7582, RFC 7900, RFC 8534

Errata ID: 5605
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Jingrong Xie
Date Reported: 2019-01-16
Held for Document Update by: Alvaro Retana
Date Held: 2022-06-22

Section 3.2.1 says:

      - If there is an installed S-PMSI A-D route originated by PE2,
        whose NLRI contains (C-S,C-G), then (C-S,C-G) matches that
        route.

      - Otherwise, if there is an installed S-PMSI A-D route originated
        by PE2, whose NLRI contains (C-S,C-*), AND if C-G is an SSM
        multicast group address, then (C-S,C-G) matches that route.

      - Otherwise, if there is an installed S-PMSI A-D route originated
        by PE2, whose NLRI contains (C-*,C-G), AND if C-G is an ASM
        multicast group address, then (C-S,C-G) matches that route.

      - Otherwise, if there is an installed S-PMSI A-D route originated
        by PE2, whose NLRI contains (C-*,C-*), then (C-S,C-G) matches
        that route.

It should say:

      - If there is an installed S-PMSI A-D route originated by PE2,
        whose NLRI contains (C-S,C-G), then (C-S,C-G) matches that
        route.

      - If there is an installed S-PMSI A-D route originated
        by PE2, whose NLRI contains (C-S,C-*), AND if C-G is an SSM
        multicast group address, then (C-S,C-G) matches that route too.

      - If there is an installed S-PMSI A-D route originated
        by PE2, whose NLRI contains (C-*,C-G), AND if C-G is an ASM
        multicast group address, then (C-S,C-G) matches that route too.

      - If there is an installed S-PMSI A-D route originated
        by PE2, whose NLRI contains (C-*,C-*), then (C-S,C-G) matches
        that route too.

Notes:

The 'Match for data reception' is an behavior on the MVPN receiver-site PE. If an SPMSI A-D route is matched for data reception, it means that the receiver-site PE will respond to this SPMSI A-D route, either send a responded Leaf A-D route in case there is an explicit-tracking flag (LIR or LIRpF), or join the PMSI tunnel in the SPMSI A-D route in case the tunnel type is mLDP/PIM etc. This usage of 'match for data reception' is not explicitly explained in this RFC but it is used in <draft-ietf-bess-mvpn-expl-track-13>.
There is clear inclusive-selective relationship between S-PMSI A-D (*,*) and S-PMSI A-D(S,G).
Thinking the S-PMSI A-D (*,*) as an Inclusive one, the receiver site PE with a (C-S,C-G) state should keep its join state on both the S-PMSI A-D (*,*) and S-PMSI A-D(S,G), and setup the 'reception state' on both the (*,*) PMSI-tunnel and (S,G) PMSI-tunnel. So the 'match for reception' should be one or more SPMSI A-D routes. The 'if/othersize/othersize' sentences make the wrong meaning.


=== AD Note ====
This section of rfc6625 has been Updated by rfc7582, rfc7900, and rfc8534 for various scenarios. Any general change to the overall procedure must take those updates into consideration. I am then marking this report as "Held for Document Update" so these modifications can be taken into account.

Report New Errata