stds-80220-requirements: FW: 802.1q Vlan Tagging

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

NTWK SVCS]; Landon, Jim [GMG]; Rausch, Walter F [GMG]; Seagren, Chris E [NTWK SVCS]
Subject: 802.1q Vlan Tagging

Current Text

[802.1Q tagging must be supported by the system (such that network egress traffic can be switched by a L2 device to the appropriate L2 termination device for managing backbone traffic or distinguishing traffic for wholesale partners in a wholesale environment).][JJH1]

Proposed text

802.1Q tagging must be supported by the system (such that network egress traffic can be switched by a L2 device to the appropriate L2 termination device for managing backbone traffic authentication vlans and or captive portal redirection to enable purchase and provision retail models or distinguish traffic for wholesale partners in a wholesale environment).

Rational

It is a crucial business requirement for next generation broadband wireless networks to support partnered networks and consumer based retail mass market purchase and enabling on line network service provisioning models. If these models cannot be delivered with resulting cost reductions it will be difficult for any XG wireless networks to be built in the United States at the very least given the highly competitive telecom market. Any technology enabling a network design that would offer more flexibility should be incorporated.

David S. McGinniss

Sprint Broadband Wireless Group

Principal Engineer II

(630) 926-3184
david.s.mcginniss@mail.sprint.com

[JJH1]Given the unspecified nature of the network architecture in which a .20 air-interface would plug in and the number of ways by which different users' traffic can be partitioned at Base Stations/other elements in the network infrastructure, its not clear if specifically using 802.1Q VLAN tags ought to be a requirement, particularly a binding one. So I would second Mike'e suggestion to not have it so.

Regarding software push, software loads etc, since these pertain more generally to the management/admin of the user terminal and not to the desired behavior of the MAC/PHY itself, we should not be specifying them in this requirements document. Regards,

[JJH2]Given the unspecified nature of the network architecture in which a .20 air-interface would plug in and the number of ways by which different users' traffic can be partitioned at Base Stations/other elements in the network infrastructure, its not clear if specifically using 802.1Q VLAN tags ought to be a requirement, particularly a binding one. So I would second Mike'e suggestion to not have it so.