Comments on RT-Constrain issues for draft-zzhang-l3vpn-mvpn-global-table-mcast

Jeffrey Haas <jhaas@pfrc.org> Mon, 09 June 2014 14:23 UTC

Date: Mon, 09 Jun 2014 10:23:40 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: l3vpn@ietf.org
Subject: Comments on RT-Constrain issues for draft-zzhang-l3vpn-mvpn-global-table-mcast
Message-ID: <20140609142340.GG31027@pfrc>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/l3vpn/UUqrRpGiKvlGVvZlF9hldg9ML1I
Precedence: list

L3VPN,

As part of resolving some interoperability issues between Juniper and
another vendor for the MDT SAFI while using the Constrained Route Target
distribution mechanism (rt-constrain, RFC 4684), it was noted that the
behavior of rt-constrain while being used on "VPN" routes with no Route
Targets was not specified.  

The behavior thus observed was that when rt-constrain was present, routes
lacking RTs may not be distributed.  This behavior would impact the Global
Table Multicast feature.

I started a thread on IDR to discuss this issue:

http://www.ietf.org/mail-archive/web/idr/current/msg13162.html

The thread somewhat abruptly ends since the participants decided to iterate
a bit less publicly.  A clarification Internet-Draft will likey result prior
to the upcoming IETF session in Toronto.  However, in the mean-time, please
be aware of this issue and its presence in various vendors and thus its
impact on this proposal.

-- Jeff

Comments on RT-Constrain issues for draft-zzhang-… Jeffrey Haas