Re: [802SEC] IEEE P802.3br draft PAR and 5 Criteria - Interspersing Express Traffic
Sent from my iPhone
On May 22, 2013, at 6:47 AM, "Law, David" <firstname.lastname@example.org> wrote:
> Dear EC members,
> In support of subclause 10.2 'IEEE 802 LMSC Approval' of the LMSC Operations Manual please find below the required information in respect to the IEEE P802.3br Amendment: Interspersing Express Traffic PAR for consideration at the July 2013 plenary.
> Best regards,
>  Draft PAR and 5C:
> Draft PAR: <http://www.ieee802.org/3/DMLT/8023-DMLT-SG-1305-Winkel-PAR-2013-05-17r1.pdf>
> Draft 5C: <http://www.ieee802.org/3/DMLT/8023-DMLT-SG-1305-Winkel-5C-2013-05-17r1.pdf>
>  Explanatory technical background material:
> Adoption of Ethernet into new market areas, including but not limited to, automotive, industrial automation, transportation (aircraft, railway and heavy trucks) has generated a need to converge low latency and best effort traffic streams.
> - Currently this functionality requires multiple networks with parallel links.
> - IEEE Std 802.3 currently does not have support for interspersed express traffic.
> - This project will allow the needs of IEEE P802.1Qbu to be met with a single physical link between bridges.
>  Work plan for the development of managed object definitions:
> The project will include a protocol independent specification of managed objects with SNMP management capability to be provided in the future by an amendment to IEEE Std 802.3.1-2011 Ethernet MIBs.
>  Status of the development of the PAR:
> The draft PAR and 5C are pending IEEE 802.3 Working Group approval at the July 2013 plenary.
> Since the submission deadline for the August NesCom meeting (12th July) occurs prior to the date of the July IEEE 802 EC meeting, I will pre-submit this draft PAR to NesCom on the understanding that:
> [a] Any changes to the draft PAR text resulting from the Plenary will be promptly communicated to the NesCom Administrator.
> [b] Should the IEEE 802.3 Working Group not approve the submission, it will be removed from the IEEE 802 Executive Committee and NesCom agenda.
> [c] Should the IEEE 802 Executive Committee not approve the submission, it will be removed from the NesCom agenda.
> This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.