Re: Poll to adopt draft-rosen-l3vpn-mvpn-spmsi-joins-00 as a L3VPN WG document

[Yakov Rekhter <[e-mail]>]

Ben,

> Colleagues,
> 
> This e-mail is to start a poll on whether the L3VPN WG should adopt
> draft-rosen-l3vpn-mvpn-spmsi-joins-00 as a L3VPN WG document.
> 
> As there was some discussion in Anaheim on section 3.1 of the draft, we will
> follow Eric's suggestion in his mail of 16th April (
> http://www.ietf.org/mail-archive/web/l3vpn/current/msg02664.html).
> 
> Therefore please indicate your support or otherwise by responding to this
> message or e-mailing the WG chairs privately with one of the following three
> options:
> 
> 1) Yes/Support for the entire of draft-rosen-l3vpn-mvpn-spmsi-joins-00 to be
> adopted as a L3VPN WG document.
> 
> 2) Yes/Support for draft-rosen-l3vpn-mvpn-spmsi-joins-00 to be adopted as a
> WG document provided section 3.1 is removed.
> 
> 3) No/Do not support draft-rosen-l3vpn-mvpn-spmsi-joins-00 being adopted as
> a WG document at all.
> 
> Please send your responses by the end of May 9th PST.

Please note the following from 3.2 S-PMSI Signaling of
draft-ietf-l3vpn-mvpn-considerations:

                                           the authors specifically do
   not recommend extending the already proposed UDP-based TLV protocol
   to new types of P-tunnels.

Note that option 1 above is a direct contradiction of the recommendation
made in draft-ietf-l3vpn-mvpn-considerations, as section 3.1 of
draft-rosen-l3vpn-mvpn-spmsi-joins-00 describes extensions to
UDP-based S-PMSI signaling to support new types of P-tunnels.

Note also that draft-ietf-l3vpn-mvpn-considerations-06, including
the recommendation not to extend UDP-based S-PMSI signaling to other
types of P-tunnels, passed L3VPN WG Last Call, passed IETF Last
Call, and has been submitted to RFC Editor for publications.

All this shows that L3VPN WG already made a decision wrt not extending
UDP-based S-PMSI signaling. There is no justification to revisit
this decision. Thus I would like to ask you to modify your call,
and remove option 1 from the list of possible options.

Yakov.