RE: I-D Action:draft-ietf-v6ops-ipv6-cpe-router-02.txt

Francois-Xavier,

Please note that this version of the CE Rtr draft (-02) which we call as
Phase I does not included any mcast behavior definition.  The SP's
working on the design team could not agree to putting mcast in the Phase
I document.  So when the Phase II gets worked on, as we have discussed
in the v6ops mailer in the past, this bridged mcast will be added as a
requirement in the document.  Do expect such text in the Phase II
document.

Note the Phase II document (after the San Francisco IETF in March 2009)
is the document below.

http://tools.ietf.org/id/draft-wbeebee-v6ops-ipv6-cpe-router-bis-01.txt

Since mcast was moved out of CE Rtr Phase I, it is included as is in the
bis doc above.  "As is" means what we agreed upon in the v6ops mailer
with you on MLDv2 snooping.  This is the text we have

If the CPE Router hardware includes a network bridge between the WAN
interface and the LAN interface(s), then the CPE Router MUST support
MLDv2 snooping as per [RFC4541].

When the design team starts work on Phase II document, this bis version
will also morph into the format being used in the
raft-ietf-v6ops-ipv6-cpe-router-02.txt.

Thanks,

Hemant