Use of VLANs for IPv4-IPv6 Coexistence in Enterprise Networks
RFC 4554

Note: This ballot was opened for revision 01 and is now closed.

(David Kessens) Yes

(Brian Carpenter) No Objection

Comment (2005-12-13 for -)
No email
send info
Editorial comments from Gen-ART review by Elwyn Davies:

s1, para 6: s/provided a/provided by a/

s1, last para: s/sites who/sites that/

s2.2, para 1: I think that 'BSD-based' could be removed - I think the idea was that a standard PC rather than a dedicated router could be used but that doesn't really matter here and if not you ought to expand the acronym BSD.

s2.2, para 1: The phrase '/64 size links' is a bit colloquial.  How about 'stub links using 64 bit subnet prefixes'

s2.3, para 2: s/while IPv6/while the IPv6/

s2.5: Might be good to remind people that the VLAN tag is 16 bits so that this can work with a 'usual' maximum 48 bit site prefix

App A, para 1: s/for BSD/using a computer running the FreeBSD variant of the Berkeley Software Distribution (BSD) operating system as a router/

App A: In the configuration s/#Router advs/# Router advertisements/

(Bill Fenner) No Objection

Comment (2005-12-15 for -)
No email
send info
It strikes me that this document recommends somewhat dangerous behavior in an offhand manner - e.g.,

   The simplest approach would be to connect an IPv6 router with one
   interface to an ethernet switch, and connect that switch to other
   switches, and then use VLAN tags between the switches and the IPv6
   router to "reach" all the IPv4-only subnets from the IPv6 router.

Naively, if the switches weren't interconnected previously, the site could have been, e.g., using the same VLAN tag on different sets of interconnected switches, or using untagged traffic; this could result in multiple subnets being accidentally combined.

(Ted Hardie) No Objection

(Sam Hartman) No Objection

(Russ Housley) No Objection

(Bert Wijnen) No Objection