[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

IPV6 in enterprise best practices/white papaers

Subject: IPV6 in enterprise best practices/white papaers
From: trejrco at gmail.com (TJ)
Date: Tue, 29 Jan 2013 15:04:57 -0500
In-reply-to: <1359454077.20278.3.camel@karl>
References: <CAKb_Nupf4GAY4cFnyyb3hewFCWk6Vp4zLyyKnc4ct-0T4K356A@mail.gmail.com> <CALgc3C4bZOM2nxVEgh0aFF4jHGpEUyMRvVOeCHx0bBUbfV5N_w@mail.gmail.com> <CAHDzDLA=9+zPgTRppAkqJt3EmJuCgQNpHg4YcuteCvtm2JD-AA@mail.gmail.com> <[email protected]> <1359454077.20278.3.camel@karl>

> Also, if a switch does not do MLD snooping, it will flood multicast to
> all ports. You lose one of the major benefits of IPv6 multicast - less
> admin traffic.

Agreed; but just to be fair: there is still a difference between
multicast being flodded everywhere and boradcast being flooded
everywhere ... L2 interrupt vs. L2+L3 interrupt; bigger difference
than it sounds ;).


/TJ

References:
- IPV6 in enterprise best practices/white papaers
  - From: paveldimow at gmail.com (Pavel Dimow)
- IPV6 in enterprise best practices/white papaers
  - From: eugen at imacandi.net (Eugeniu Patrascu)
- IPV6 in enterprise best practices/white papaers
  - From: mukom.tamon at gmail.com (Mukom Akong T.)
- IPV6 in enterprise best practices/white papaers
  - From: mansaxel at besserwisser.org (Måns Nilsson)
- IPV6 in enterprise best practices/white papaers
  - From: kauer at biplane.com.au (Karl Auer)

Prev by Date: Ethernet Service at 150 S. Market Street, SJ
Next by Date: Muni network ownership and the Fourth
Previous by thread: IPV6 in enterprise best practices/white papaers
Next by thread: IPV6 in enterprise best practices/white papaers
Index(es):
- Date
- Thread