RE: Advancing the Protocol and Morin Drafts

["ASIF, SAUD, ATTLABS" <[e-mail]>]

 
My Vote is :  NO
 
Unless this draft changes its structure to include the requirements and
recommendations of ISPs that has large real-life MVPN customer base and
experience I don't support this draft. We need to solve the multicast
scalability, inter-as, and interoperability issues by incorporating
recommendations from people who are already in trenches facing these on
a daily basis.

Saud Asif
New Technology Product Dev. Eng. 
AT&T Laboratories 
[e-mail] 
v: 732-420-2062
 
  

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf
Of Marshall Eubanks
Sent: Wednesday, October 01, 2008 10:04 AM
To: [e-mail]
Cc: Ross Callon
Subject: Advancing the Protocol and Morin Drafts 

This email starts a 3 week call for input, to expire October 23, 2008,  
for the following steps:

1.) To accept draft-morin-l3vpn-mvpn-considerations-03 as a working
group document;  and

2.) To turn this document into a requirements draft, with mandatory to
implement features for an interoperable implementation. The authors
have indicated that they are willing to do this.

Our intention is, if this approach is accepted, to then begin WG last
call to submit to the IESG for publication:

draft-ietf-l3vpn-2547bis-mcast
draft-ietf-l3vpn-2547bis-mcast-bgp

We expect that these two documents will be submitted more or less as is
(i.e., certainly with any new bug fixes or other necessary corrections  
and
improvements, but without specific mandatory to implement feature
description in those drafts).

Please respond to the list with your recommendations for these two
courses of action.

Regards
Marshall & Danny