================================================================================

IBIS INTERCONNECT TASK GROUP
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibis.org_interconnect-5Fwip_&d=DwIGAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DcQR-qLpQg5lIreuM6-NYECRIAFXt268PRNS5WO043M&m=FKRuVwKokzv_O1bGg6DHeR2LaZSr45-s2xhh9KZhMCM&s=wKy_Y8HPOvhU8AcfdjBUK9DYQUJ2W-t5Q7_JE_1Fhcg&e=  
Mailing list: ibis-interconnect@freelists.org 
Archives at https://urldefense.proofpoint.com/v2/url?u=http-3A__www.freelists.org_archive_ibis-2Dinterconn_&d=DwIGAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DcQR-qLpQg5lIreuM6-NYECRIAFXt268PRNS5WO043M&m=FKRuVwKokzv_O1bGg6DHeR2LaZSr45-s2xhh9KZhMCM&s=WjPZgDjZXfJ4KZVbOqAtjqDb0Sg0eNtGdtAp2mwQc0A&e=  

================================================================================

Attendees from January 6, 2021 Meeting (* means attended at least using audio)

ANSYS                                Curtis Clark*
Intel Corp.                          Michael Mirmak*
Mentor, A Siemens Business           Arpad Muranyi*
Micron Technology                    Justin Butterfield*
                                     Randy Wolff*
Teraspeed Labs                       Bob Ross*
Zuken USA                            Lance Wang*


Michael Mirmak convened the meeting.  No patents were declared. 
Justin Butterfield took minutes.


Review of Minutes:
- Michael called for review of the minutes from the December 16, 2020 meeting.  
  Michael displayed the minutes.  Randy Wolff moved to approve the minutes.  
  Curtis Clark seconded.  The minutes were approved without objection.

  
Review of ARs:   
- Michael to edit and make consistent "e.g." and "i.e." followed by a comma.  
  - Michael noted this is not done [AR].

- Michael to make the changes to the EMD Pin List to match the Designator Pin 
  List and send out EMD BIRD202.2 draft4.
  - Done.


Opens:
- Michael noted we may spend less time on the minutes review in future meetings, 
  since we are reviewing the minutes before they are sent out.  Curtis asked 
  what the review process is.  Justin replied he is sending the minutes to Randy
  and Michael to catch any typos and other issues.  Curtis agreed with this 
  approach.

- Michael noted he has worked with Steve Parker, and all documents and minutes 
  are now posted to the website.  Randy asked if the posting script is working.  
  Michael was not sure, but Steve was able to post the documents quickly.


BIRD202.2 draft4 review:
Michael noted we have copied some of the reserved word language into the 
Designator Pin List for NC, POWER, and GND.  Curtis had asked about this 
previously, as he was not sure what NC meant in the context of the Designator 
Pin List.  Michael agreed it is not clear what NC would be used for in the 
Designator Pin List.  He asked if it should match the IBIS Component.  Arpad 
Muranyi noted, in the signal_name column for Designator Pin List, we allow the 
model maker to use any signal_name, which does not need to match the IBIS file.  
The third column (signal_type) is used to establish power, ground, or signal, 
and it is a good question what NC is for.  Bob Ross stated NC could be a pin not 
modeled in IBIS.  Arpad noted that is relevant in the IBIS file, while here we 
are describing the signal and distinguishing between power, ground, and signal.  
Bob stated, if it has an NC pin on the EMD, you might route it with a 
signal_name.  

Michael asked, if we removed NC, would anything be broken.  Randy replied the 
signal could be connected to an NC inside the IBIS file.  Michael asked if this 
will be flagged by the parser.  Arpad asked if these have to match between the 
EMD and the IBIS file.  He asked why we need this.  Arpad noted we have some 
rules that relate to these categories, but he questioned if it is required that 
that the signal_type match the IBIS file.  Bob was not sure if we check this for 
Interconnect Models, as you could have a 0V power rail and connect it to 
ground.  

Arpad suggested to remove the highlighted NC related text.  Bob asked if this 
affects any of the examples.  Randy noted we still have no-connects in the EMD 
Pin List.  He asked if this is still valid.  Bob replied, on the EMD Pin List, 
we can have NC if the edge connector has NC pins that the model maker wants to 
document or for signals that have routing but no connections.  Arpad noted, if 
there is an NC pin, we do not need to include a model for it.  Bob asked how we 
handle a pin with no routing.  Arpad replied the pin can be dangling.  Bob 
suggested to keep NC for EMD Pin List and remove it for Designator Pin List.  
Arpad asked what is the purpose of this.  Bob replied there could be no known 
model to connect, or there could be no routing.  Curtis commented his issue was 
mostly with the wording of the text.  

Michael asked if the third column (signal_type) should be required for rail 
pins.  Randy agreed.  Michael noted we can have only two columns for signals now.

Randy thought the examples were okay.  Michael noted one example uses NC in the 
EMD Pin List.  Arpad asked if we are okay keeping the NC for EMD Pin List.  Bob 
replied we could have the EMD pin but none of the models connect to it.  Arpad 
asked if the description for NC is correct.  Randy commented the NC in the IBIS 
component could be for signals that cannot be modeled.  It is useful at this 
level to know that the signal disconnects at the IBIS component level.  Arpad 
reiterated his concern with the description of NC.  Arpad noted the POWER and 
GND serve a purpose for checking the rules of the signal_name.  Michael 
suggested to simplify the NC description.  Randy suggested to also remove the 
parenthetical.

Michael noted the only comment remaining in the document is related to the Usage 
Rules under EMD Pin List.  Randy thought this section does match that in 
Designator Pin List.  Michael agreed and noted he checked this.

Bob had noticed a couple of editorial issues.  He suggested to delete the word 
"token".  Bob also noted a sentence related to the EMD Group number of 
characters, and he suggested the word "length" should not used.  He noted there 
is a similar issue in IBIS 7.0.  Randy asked if we should change it for EMD.  
Randy removed the phrase "in length" from instances where it referred to the 
number of characters.  Randy suggested to add this to the IBIS 7.0 known issues.

Bob asked who will make the changes to "i.e." and "e.g.".  Randy replied he can 
make these changes now.  Randy fixed these in draft5.

Randy asked about the phrase "PCI Express" which is highlighted on page 18.  
Arpad asked if we should stay away from product and specifications.  Randy asked 
if we should look up the official abbreviation.  Arpad suggested to use "PCIe".

Randy will add fixing "in length" and "PCI Express" to the IBIS 7.0 known issues 
list [AR].

Arpad asked if we are done with this BIRD now and if we can submit it to the 
IBIS Open Forum.  Randy replied we need to discuss the bin list and the EMD 
Parts.  Bob was not sure what the issue with EMD Parts was.  Randy replied we 
could have a selector for easier component changes.

Randy will send EMD BIRD202.2 draft5 [AR].


Next Meeting:
The next meeting will be January 13.


Arpad moved to adjourn.  Curtis seconded.  The meeting adjourned without 
objection.

================================================================================
Bin List:

EMD Comments to be Resolved:
(See BIRD202.1 tracking spreadsheet)

IBIS-ISS Parser:
- IBIS-ISS parser scope document