CSD for P802.1AB-REV

PAR and CSD for P802.1Qxx802.1 WGJanuary 2015PAR (1)1.1 Project Number: P802.1Qxx1.2 Type of Document: Standard1.3 Life Cycle: Full Use2.1 Title: Standard for Local and metropolitan area networks--Bridges and Bridged Networks Amendment: Automatic Attachment of network devices to individual services in a Short Path Bridging (SPB) network using extensions to the Link Layer Discovery Protocol (LLDP)PAR (2)5.1 Approximate number of people expected to be actively involved in the development of this project: 355.2.a. Scope of the complete standard: This standard specifies Media Access Control (MAC) Bridges that interconnect individual Local Area Networks (LANs), each supporting the IEEE 802 MAC service using a different or identical media access control method, to provide Bridged Local Area Networks and Virtual LANs (VLANs). (unchanged)5.2.b. Scope of the project: This standard specifies the protocols, procedures and management objects for auto-attach Type, Length, Value (TLVs) within the Link Layer Discovery Protocol (LLDP) defined in IEEE 802.1AB.5.4 Purpose: MAC Bridges, as specified by this standard, allow the compatible interconnection of information technology equipment attached to separate individual LANs. (unchanged)5.5 Need for the Project: This amendment simplifies the deployment and administration of the networks running SPB by allowing for automatic configuration of the virtual LANs and service identifiers, thus allowing access to services of network devices without the need of 5.6 Stakeholders for the Standard: Developers, providers, and users of networking services and equipment such as software developers, bridge and NIC vendors, network operators and users.PAR (3)Intellectual Property6.1.a. Is the Sponsor aware of any copyright permissions needed for this project?: No6.1.b. Is the Sponsor aware of possible registration activity related to this project?: YesIf yes please explain: The project may include the following items that may require registrations:- new TLVs for the LLDP- a new sub-branch for the LLDP MIB module7.1 Are there other standards or projects with a similar scope?: No7.2 Joint DevelopmentIs it the intent to develop this document jointly with another organization?: NoProject process requirements

Managed objectsDescribe the plan for developing a definition of managed objects. The plan shall specify one of the following:The definitions will be part of this project.The definitions will be part of a different project and provide the plan for that project or anticipated future project.The definitions will not be developed and explain why such definitions are not needed.The definitions are part of the project.

Project process requirements

CoexistenceA WG proposing a wireless project shall demonstrate coexistence through the preparation of a Coexistence Assurance (CA) document unless it is not applicable.Will the WG create a CA document as part of the WG balloting process as described in Clause 13? (yes/no)If not, explain why the CA document is not applicable.Not applicable this is not a wireless project.5C requirements

Broad market potentialEach proposed IEEE 802 LMSC standard shall have broad market potential. At a minimum, address the following areas:Broad sets of applicability.Multiple vendors and numerous users.The proposed revision would apply to all 802 networks that implement IEEE 802.1AB and IEEE 802.1aqSome vendors and users have expressed their support for this extensions and there are a number of implementations successfully deployed in the field.5C requirements

CompatibilityEach proposed IEEE 802 LMSC standard should be in conformance with IEEE Std 802, IEEE 802.1AC, and IEEE 802.1Q. If any variances in conformance emerge, they shall be thoroughly disclosed and reviewed with IEEE 802.1 WG prior to submitting a PAR to the Sponsor.Will the proposed standard comply with IEEE Std 802, IEEE Std 802.1AC and IEEE Std 802.1Q?If the answer to a) is no, supply the response from the IEEE 802.1 WG.The review and response is not required if the proposed standard is an amendment or revision to an existing standard for which it has been previously determined that compliance with the above IEEE 802 standards is not possible. In this case, the CSD statement shall state that this is the case.Yes.5C requirements

Distinct IdentityEach proposed IEEE 802 LMSC standard shall provide evidence of a distinct identity. Identify standards and standards projects with similar scopes and for each one describe why the proposed project is substantially different.There is no other 802 standard or approved project that provides the same functionality for bridges or end stations. VDP-based solutions cannot cover all the range of SPB solutions (specifically SPB-M I-SID attachment)5C requirements

Technical FeasibilityEach proposed IEEE 802 LMSC standard shall provide evidence that the project is technically feasible within the time frame of the project. At a minimum, address the following items to demonstrate technical feasibility:Demonstrated system feasibility.Proven similar technology via testing, modeling, simulation, etc.There are numerous implementations of the IEEE 802.1AB and IEEE 802.1aq standards. This proposal represents an extension of the firstThe technology has been proven in the field and in compatibility testing carried out in testing labs.5C requirements

Economic FeasibilityEach proposed IEEE 802 LMSC standard shall provide evidence of economic feasibility. Demonstrate, as far as can reasonably be estimated, the economic feasibility of the proposed project for its intended applications. Among the areas that may be addressed in the cost for performance analysis are the following:Balanced costs (infrastructure versus attached stations).Known cost factors.Consideration of installation costs.Consideration of operational costs (e.g., energy consumption).Other areas, as appropriate.The functionality needed to provide the features specified in this standard is essentially the same in bridges and end stations. The cost of providing these features in each type of device will not be significant, given the expected large volumes.The cost factors are well known from implementations of IEEE 802.1AB. We are basically talking about a software upgradeThere are no incremental installation costs relative to the existing costs associated with IEEE 802.1AB and IEEE 802.1aqThere are no incremental operational costs relative to the existing costs associated with IEEE 802.1AB and IEEE 802.1aqNo other areas have been identified.