GET https://dev.normadoc.fr/_partial/cart/summary?template=%40SyliusShop%2FCart%2F_widget.html.twig

Response
200 OK
IP
216.73.216.19
Profiled on
Token
5e71e4

Components

3 Twig Components
5 Render Count
2 ms Render Time
74.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		2 0.53ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		2 1.63ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.18ms

Render calls

ProductState App\Twig\Components\ProductState 66.0 MiB 0.29 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93066
  +product: App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 68.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93246
  +product: App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 68.0 MiB 0.64 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93321
  +product: App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 74.0 MiB 0.24 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100264
  +product: App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 74.0 MiB 0.98 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100348
  +product: App\Entity\Product\Product {#7310
    #id: 11406
    #code: "IEEE00006069"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039685 {#7274
      date: 2025-06-27 17:54:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 40633
        #name: "IEEE 2030.102.1:2020"
        #slug: "ieee-2030-102-1-2020-ieee00006069-243058"
        #description: """
          New IEEE Standard - Active.<br />\n
          Specific configuration requirements within the relevant Internet Engineering Task Force (IETF) Request for Comments (RFC) for implementation of the Internet Protocol Security (IPsec) protocol suite within a utility control system are identified in this standard. It is not intended to be a comprehensive guide to implementing IPsec. Promoting interoperability between products developed by different vendors is the primary goal in developing this standard. Configuration parameters needed to support the establishment and sustained operation of an IPsec Virtual Private Network (VPN) tunnel between two devices which have implemented IPsec conforming to this standard are the focus of this standard. Minimizing configuration errors involving IPsec implementations within utility control systems is a secondary goal of this standard. Product agnosticism and applicability to any device (e.g., router, substation gateway, intelligent electronic device, etc.) is the intent of this standard, within the utility control system as the end user deems necessary for their unique system architecture.<br />\n
          \t\t\t\t<br />\n
          This standard specifies requirements for interoperability of devices utilized within utility control systems, which implement the Internet Protocol Security (IPsec) protocol suite within an IPv4 environment.<br />\n
          The purpose of this document is to define a specific configuration profile for the Internet Protocol Security (IPSec) protocol suite suitable for use within a utility control system. The primary goal in developing this standard is to promote interoperability between products developed by different vendors. It focuses on those configuration parameters needed to support the establishment and sustained operation of an IPSec Virtual Private Network (VPN) tunnel between two devices that have implemented IPSec conforming to this standard. A secondary goal of this standard is to help minimize configuration errors involving IPSec implementations within utility control systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Interoperability of Internet Protocol Security (IPsec) Utilized within Utility Control Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1619388000 {#7292
      date: 2021-04-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1615503600 {#7318
      date: 2021-03-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2030.102.1"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}