================================================================================ 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=u9clb5stc2PT0ejjg983E5a2nHA5jdPoIj3Cy3fPIn4&s=Mdp6g0yokZHPDRN683zaP-jpXuuHkzADEBpDcn8LVE4&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=u9clb5stc2PT0ejjg983E5a2nHA5jdPoIj3Cy3fPIn4&s=fTFsrgB4xcCvCcrX7nefPKa0pvlryx3OarLWYrjAqCE&e= ================================================================================ Attendees from September 2, 2020 Meeting (* means attended at least using audio) ANSYS Curtis Clark* Intel Corp. Michael Mirmak* Ifiok Umoh Eric Edwards Keysight Technologies Radek Biernacki Mentor, A Siemens Business Arpad Muranyi* Micron Technology Justin Butterfield* Randy Wolff* SiSoft Walter Katz* Mike LaBonte 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 August 26, 2020 meeting. Michael displayed the minutes. Randy moved to approve the minutes with this change. Walter seconded. The minutes were approved without objection. Review of ARs: - Michael to check if the most recent drafts have been posted to the website. - Michael noted he will check on this [AR]. - Walter to make a recommendation on Aggressor_Only rules. - Done. - Bob to propose clarifying statements for "connected". - Done. - Michael to send out the latest copy of the EMD bin list spreadsheet. - Done. - Randy to send out EMD draft23. - Done. Opens: - None. Aggressor_Only Rules: Walter shared the email he sent on Aggressor_Only. He proposed a paragraph to be added at the end of section 13.3. He commented crosstalk simulation spans the extended nets that span packages, EMDs, boards, and connectors. Bob asked what is meant by extended net. Walter noted an extended net could be through a connector or resistor. Bob asked if the net names will be the same on both sides of the extended net. Walter gave an example of a connector which could have different net names on each side. Bob noted, for a series resistor, there would be different net names. Walter asked if the definition of extended net is well understood. Randy noted extended net is defined in the introduction on page 7. Bob stated he is questioning the definition of extended net. Michael asked if the question is the boundary, and if it goes through a component, then it is an extended net. Walter replied an extended net describes all the nets that are connected. Bob noted the definition is to connect two CAD nets. CAD nets are also connected. The confusion is, if a series resistor is removed, a net or CAD net maintains the same name. Bob asked if the Aggressor_Only rules should apply to a CAD net. Michael commented we are not trying to define every single case for Aggressor_Only. Walter commented we already have a statement about the net applying to Aggressor_Only. This statement says it can expand across CAD nets. Michael noted this is a subset, and we are not saying the Aggressor_Only does not apply to normal CAD nets. Arpad asked, in the first sentence, if the coupled interconnect models are always consisting of extended nets. And if the sentence could be changed to reflect this. Michael asked if we should start a draft24. Randy replied we can use Michael's draft as a starting point. Arpad commented the first sentence implies the extended nets will always be there. Randy suggested to say "extended nets or nets". Arpad agreed with this. Arpad and Randy suggested to fix a few typos. Walter suggested to say "net or extended net". Randy suggested to not capitalize "Boards". Arpad asked about the word "pins". Walter replied it could have none of the crosstalk included. Bob asked about the word "pins" as well. Walter replied the pin on the net would have crosstalk. Michael asked if we want to say the pins have crosstalk. Arpad stated the word "terminals" at the start of the sentence clashes with the word "pins". Bob noted the nets automatically include the pins, but he agrees the crosstalk is captured at the pins. Michael suggested to say simulation results reported for the pins. Randy asked if we want to say "terminals". Arpad suggested to remove "pins". Curtis suggested to change the end of the last sentence to say the crosstalk contributions will be incomplete. Michael agreed with this. Michael asked if this paragraph goes in the document at the end of section 13.3 on page 26. Randy agreed. Michael included this in draft24. Connected Definition: Bob shared his email proposal on connected. He defines connected in three different ways. One type, for rail terminals, is at any one interface and relies on the signal_name being the same. For rail designator interfaces, we can have the *.signal_name for modeling purposes to create a single terminal. At one interface, rail terminals with the same bus_label can also be reduced to one terminal. For I/O terminals, the terminals are brought out by the pin_names at interfaces. If the pin_names share the same signal_name they are regarded as connected, and the connection needs to be described by the IBIS-ISS or Touchstone model. Randy asked where this text should go. Bob noted this contains concepts introduced much later in the BIRD. Michael asked if the text could be split up. Bob noted page 7 introduces connected. Michael suggested it could go after I/O terminals is defined on page 19. It could also be put later in the document after the examples, but this might bury it. The text for rails could go in section 13.6, and the text for I/Os could go in section 13.2. Michael will add Bob's connected definitions in draft24 [AR]. Michael will send out EMD draft24 [AR]. Next Meeting: The next meeting will be September 9. Arpad moved to adjourn. Randy 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