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

Re: [802.3_NGBIDI] Material for ad hoc call

Hi Marek,

An overview of the IEEE-SA copyright policy can be accessed at <> which includes links to the copyright policy found in subclause 7.2 of the IEEE-SA Bylaws. As can be seen subclause 7.2.1 'Contributions from previously Published sources' <> states that contributions from previously Published sources shall be accompanied by a Copyright Permission Form that is completed by the copyright owner. Subclause 7.1 'Definitions' states that '"Published" shall mean material for which a claim of copyright is apparent (e.g., the presence of the copyright symbol; an explicit statement of copyright ownership ...).'.

Based on this, if a contribution from an individual has a copyright statement it has to be accompanied by a Copyright Permission Form completed by the copyright owner. I'm happy to supply a copy of the Copyright Permission Form to the individual.

Best regards,


From: Marek Hajduczenia [mailto:mxhajduczenia@xxxxxxxxx
Sent: 20 February 2019 14:30
Cc: Law, David <dlaw@xxxxxxx>
Subject: RE: [802.3_NGBIDI] Material for ad hoc call


I do not believe any *watermark* is needed at this time, since this is a contribution from an individual, right? It only happens to look similar to what the initial draft version would look like. I think it might be best to consult David here on what the right approach is. All I know is that distributing it as if it was an official copyrighted draft is confusing. 

If the preference is to separate single-fiber PMDs from multi-fiber PMDs (I still find it odd that any of the editors would actually recommend that, given the added maintenance mess if adds) we should strive to keep all single-fiber PMDs in one clause. After all, a lot of the material will be similar. Effectively, what I am trying to figure out is how we can get the draft out without having to repeat too much material from existing clauses, and avoid repetition over and over again within the new clause(s), unless there is a very good reason for it. 

The base standard is becoming larger and larger quickly with each new project, and while electronic version is still very usable, all the repetitive material is just a nightmare for future maintenance projects


From: frank effenberger <frank.effenberger@xxxxxxxxxx
Sent: Wednesday, February 20, 2019 7:20 AM
Subject: RE: [802.3_NGBIDI] Material for ad hoc call

HI Marek, 
It is true that this is not any kind of official draft.  Perhaps we should put a watermark across each page, saying so.  That would avoid confusion. 

As for adding columns to existing clauses, I had socialized that with a few other editors, and their view was that significantly different PHY types should be in different clauses.  Changing the medium from 2 fiber to 1 fiber is considered a significant change.  

As for the repetition of material, that is a concern.  We can always try to use references back to the existing clause for any sub-sections that we do not change.  Effectively, these BiDi PMD clauses will end up reading a lot like amendments.  However, I notice that other PMDs that were derivatives do repeat a lot of material.  I could go either way on that issue.  

Frank E

From: Marek Hajduczenia [mailto:mxhajduczenia@xxxxxxxxx
Sent: Wednesday, February 20, 2019 9:05 AM
Subject: Re: [802.3_NGBIDI] Material for ad hoc call


Since this is not any "draft" at this time, and certainly not an official Task Force draft, it seems that all copyright and versioning information should be struck from these contributions. This might be confusing for people. 

Also, given the volume of overlap with other PMDs of the similar type, I will repeat my observation from the last meeting - rather than have to prepare brand *new* clauses, that look 97% (or more) like the clauses we already have in the standard, why not add new columns in PMD tables and define new PMD types to address the new target functionality instead? That is a much simpler approach since we do not have to create and replicate content at all, keeping PMDs with already existing PMDs of similar type. All we need then is an extension to Clause 56 (likely) to list new PMD types and describe why they are special and point to particular existing clauses where they are defined? 


On Tue, Feb 19, 2019 at 12:17 PM Duane Remein <Duane.Remein@xxxxxxxxxx> wrote:
I would like to present the attached material on the next BiDi ad hoc call.  Most of this pretty straight forward and can be covered in a relatively short amount of time.  Comments are welecome.
Best Regards,
FutureWei Technologies Inc.
Director, Access R&D
919 418 4741
Raleigh, NC
To unsubscribe from the STDS-802-3-NGBIDI list, click the following link: 
To unsubscribe from the STDS-802-3-NGBIDI list, click the following link: 

To unsubscribe from the STDS-802-3-NGBIDI list, click the following link: