Re: [MBONED] [nvo3] NVO3 Multicast Framework

Hi Dino,

Thanks for pointing that out.  Indeed that is not specific to head end
replication.  We can move that text to a separate section that is
referenced by the sections for all of the multicast methods.  Let me know
if that would address the comment.

Thanks,
Anoop

On Tue, May 24, 2016 at 10:20 AM, Dino Farinacci <farinacci@gmail.com>
wrote:

> Sorry, I thought I had. NVo3, see my comments below.
>
> Dino
>
> > On May 24, 2016, at 6:14 AM, Bocci, Matthew (Nokia - GB) <
> matthew.bocci@nokia.com> wrote:
> >
> > Hi Dino
> >
> > Could you copy NVO3 on your comments, please?
> >
> > Thanks
> >
> > Matthew
> >
> > From: EXT Dino Farinacci <farinacci@gmail.com>
> > Date: Monday, 16 May 2016 at 23:31
> > To: Leonard Giuliano <lenny@juniper.net>
> > Cc: MBONED WG <mboned@ietf.org>, Matthew Bocci <
> matthew.bocci@alcatel-lucent.com>, Benson Schliesser <
> bensons@queuefull.net>
> > Subject: Re: [MBONED] NVO3 Multicast Framework
> >
> > I just have one minor comment. Regarding the second paragraph:
> >
> > <PastedGraphic-2.png>
> >
> > Using LISP-signal-free does not mean the head-end must do replication.
> The draft indicates that a mapping system is used to decide where packets
> go. If the mapping database indicates that packets are encapsulated to
> multicast RLOCs, or unicast RLOCs, or both in one set, so be it.
> >
> > And note if there is a single multicast RLOC, then there is no
> replication happening at the head-end, just one packet encapsulting
> multicast in multicast.
> >
> > So what is written above is true, but it may be associated with an
> incorrect section title.
> >
> > Dino
> >
> >> On May 12, 2016, at 2:52 PM, Leonard Giuliano <lenny@juniper.net>
> wrote:
> >>
> >> MBONED,
> >>
> >> The following draft recently went through WG last call in the NVO3
> working group:
> >>
> >> https://datatracker.ietf.org/doc/draft-ietf-nvo3-mcast-framework/
> >>
> >> This doc covers multicast in data center overlay networks.  As you
> know, it is part of our charter in MBONED to provide feedback to other
> relevant working groups.  Please review and send any comments to the NVO3
> WG mailing list (nvo3@ietf.org)- all comments will be greatly appreciated
> by NVO3.
> >>
> >> _______________________________________________
> >> MBONED mailing list
> >> MBONED@ietf.org
> >> https://www.ietf.org/mailman/listinfo/mboned
> >
> > <PastedGraphic-2.png>
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>