Re: call for discussion on draft-heinanen-radius-pe-discovery-03. txt

Yakov Rekhter <[email protected]> Tue, 20 May 2003 08:37:26 -0700
Newsgroups gmane.ietf.ppvpn
Message-ID <[email protected]>
Richard,

[clipped...]
 
>  > Richard> and  meets all  the  discovery requirements  
>  > identified within  the
>  > Richard> PPVPN WG so far including "Limits VPN information 
>  > to only those PEs
>  > Richard> involved  in  that  VPN",  "Extendible to  provide  
>  > information  in
>  > Richard> additional to VPN endpoint IP address" and 
>  > "Supports inter-provider
>  > Richard> VPNs". 
>  > 
>  > The BGP-based discovery procedure meets these requirements. 
> 
> RS> I think how well the BGP discovery mechanism is perceived to meet the
> above requirements depends on how the requirements are interpreted. 
> 
> In the case of limiting VPN information to only those PEs involved in the
> VPN, in the BGP discovery process PEs broadcast VPN membership information
> for all the VPNs that they are members of, to all the other PEs in the
> network. This is done regardless of whether the other PEs in the network are
> members of the VPN or not and is a receiver based filtering process in which
> receiving PEs have to filter out the relevant information for the VPNs that
> they belong to. Information for VPNs that a receiving PE is not a member of
> can be discarded (or retained for future use). The point being that the
> *distribution* of VPN information is not limited to those PEs involved in a
> particular VPN, although the storing of this information can be.

This is incorrect. Please read section 7 of draft-ietf-ppvpn-bgpvpn-auto-05.txt.
  
Yakov.