<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Obsolescence in Intel® Collaboration Suite for WebRTC</title>
    <link>https://community.intel.com/t5/Intel-Collaboration-Suite-for/Obsolescence/m-p/1745349#M4825</link>
    <description>&lt;P&gt;Hey, hope you’re doing good &lt;A href="https://doflixindia.com/dooflix-old-version/" target="_self"&gt;&lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I understand this kind of request can get a bit tricky, especially when it’s about obsolescence tracking and compliance for a component like a circuit integrated one. Basically you’re trying to confirm lifecycle status + REACH/ROHS + datasheet in one go, which many suppliers don’t always keep clearly updated in one place.&lt;/P&gt;&lt;P&gt;I faced something similar while checking old electronic parts for a project, and honestly most of the time the issue is internal data is scattered between distributor + manufacturer.&lt;/P&gt;&lt;P&gt;What worked for me:&lt;/P&gt;&lt;P&gt;Always confirm status directly with original manufacturer first (they’re most reliable)&lt;/P&gt;&lt;P&gt;For ROHS/REACH, check latest compliance PDFs, not old listings&lt;/P&gt;&lt;P&gt;If possible, ask for lifecycle bulletin or PCN updates&lt;/P&gt;&lt;P&gt;In my work context (U-Shop reference), I’ve seen teams struggle when they rely only on reseller data.&lt;/P&gt;&lt;P&gt;By the way, do you already have a supplier contact for this 8255-A5 or are you still searching the source?&lt;/P&gt;</description>
    <pubDate>Wed, 22 Apr 2026 11:08:27 GMT</pubDate>
    <dc:creator>nathn34</dc:creator>
    <dc:date>2026-04-22T11:08:27Z</dc:date>
    <item>
      <title>Obsolescence</title>
      <link>https://community.intel.com/t5/Intel-Collaboration-Suite-for/Obsolescence/m-p/1618927#M4761</link>
      <description>&lt;P&gt;Bonjour ,&lt;/P&gt;&lt;P&gt;Je me permets de vous contacter au sujet d’une demande d’information sur votre référence.&lt;BR /&gt;L’activité d’OBSAM est de faire de la veille et du traitement d’obsolescence. Dans ce cadre, CEA nous a missionné afin de récolter des informations.&lt;/P&gt;&lt;P&gt;Référence : 8255-A5 Désignation : CIRCUIT INTÉGRÉ&lt;/P&gt;&lt;P&gt;S’il vous plait, en priorité, pourriez-vous indiquer le statut du produit (Actif/Obsolète/LBO) ainsi que la pérennité de fabrication ?&lt;BR /&gt;Pourriez vous m'indiquer si le REACH et le ROHS sont conformes&lt;BR /&gt;Pour finir, pouvez-vous nous fournir la fiche technique du produit ?&lt;/P&gt;&lt;P&gt;Je vous remercie par avance,&lt;/P&gt;&lt;P&gt;Bien Cordialement,&lt;/P&gt;&lt;P&gt;Nathalie MAHE&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 09:09:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Collaboration-Suite-for/Obsolescence/m-p/1618927#M4761</guid>
      <dc:creator>mahe</dc:creator>
      <dc:date>2024-07-29T09:09:53Z</dc:date>
    </item>
    <item>
      <title>Re: Obsolescence</title>
      <link>https://community.intel.com/t5/Intel-Collaboration-Suite-for/Obsolescence/m-p/1745349#M4825</link>
      <description>&lt;P&gt;Hey, hope you’re doing good &lt;A href="https://doflixindia.com/dooflix-old-version/" target="_self"&gt;&lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I understand this kind of request can get a bit tricky, especially when it’s about obsolescence tracking and compliance for a component like a circuit integrated one. Basically you’re trying to confirm lifecycle status + REACH/ROHS + datasheet in one go, which many suppliers don’t always keep clearly updated in one place.&lt;/P&gt;&lt;P&gt;I faced something similar while checking old electronic parts for a project, and honestly most of the time the issue is internal data is scattered between distributor + manufacturer.&lt;/P&gt;&lt;P&gt;What worked for me:&lt;/P&gt;&lt;P&gt;Always confirm status directly with original manufacturer first (they’re most reliable)&lt;/P&gt;&lt;P&gt;For ROHS/REACH, check latest compliance PDFs, not old listings&lt;/P&gt;&lt;P&gt;If possible, ask for lifecycle bulletin or PCN updates&lt;/P&gt;&lt;P&gt;In my work context (U-Shop reference), I’ve seen teams struggle when they rely only on reseller data.&lt;/P&gt;&lt;P&gt;By the way, do you already have a supplier contact for this 8255-A5 or are you still searching the source?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Apr 2026 11:08:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Collaboration-Suite-for/Obsolescence/m-p/1745349#M4825</guid>
      <dc:creator>nathn34</dc:creator>
      <dc:date>2026-04-22T11:08:27Z</dc:date>
    </item>
  </channel>
</rss>

