IPv6 Deployment in Internet Exchange Points (IXPs)
Note: This ballot was opened for revision 09 and is now closed.
(Ron Bonica) Yes
(Jari Arkko) No Objection
Comment (2010-07-15 for -)
Do IXPs normally run SIP gateways (Section 7)? That would be news to me... Ari Keränen's review noted some editorial issues: 2. Switch Fabric Configuration 2. independent VLAN (Virtual Local Area Network): when an IXP logically separates IPv4 and IPv6 traffic in different VLANs. Missing VLAN reference. 3. Addressing Plan o IXP may decide that LANs should (attempt to be) be globally The word "be" twice in a row. Additionally, possible IXP external services (such as dns, web pages, ftp servers) DNS and FTP not capitalized. 4.1. Multicast Support and Monitoring for ND at an IXP "ND" not expanded (mentioned first time). Probably would be better to do it somewhere before the title.
(Stewart Bryant) No Objection
(Gonzalo Camarillo) No Objection
(Lars Eggert) No Objection
(Adrian Farrel) No Objection
(Russ Housley) No Objection
Alexey Melnikov No Objection
Comment (2010-07-11 for -)
Slightly pedantic comments: In Section 3, last paragraph: Additionally, possible IXP external services (such as dns, web pages, ftp servers) need to be globally routed. s/dns/DNS s/ftp/FTP Also add informative references for these. More acronyms with no references in Section 7.
(Tim Polk) No Objection
(Dan Romascanu) No Objection
Comment (2010-07-14 for -)
> However, some management functions may require explicit IPv6 support (such as switch management, SNMP [RFC3411] support or flow analysis exportation) and this should be assessed by the IXP operator. I do not understand what switch management means here, and support of SNMP and IPFIX (which I suspect is what is meant by flow analysis exportation) should be transparent to the network layer.